RBAC causes a change to the Deployment Engine

Mike's Notes

Building out RBAC is leading to other changes in Pipi.

Resources

• https://www.blog.ajabbi.com/2025/09/role-based-access-control-rbac.html

References

• Reference

Repository

• Home > Ajabbi Research > Library >
• Home > Handbook > 

Last Updated

09/09/2025

RBAC causes a change to the Deployment Engine

By: Mike Peters

On a Sandy Beach: 09/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Using RBAC to redesign the Pipi security model has led to some changes in other Engines. 

User Account

A User Account has one or more Deployments.

Deployment

A deployment has these properties;

• ID
• Code Name
• Name
• Description
• One language (eg English)
• One User Account
• One Deployment Class (type of tenancy)
• One Domain Model (eg, health).

Those properties are inherited. This means each Deployment/Domain Model has its own set of prebuilt Security Roles, Security Profiles

Security Role

A security role has these properties;

• ID
• Code Name
• Name
• Description
• One User Account Class ( eg, Pipi, Enterprise, DevOps, SME, User)
• One language (eg, English, French, Hebrew)
• One Domain Model (eg, health, website, sewerage, public transport, art gallery).

Example

• Domain Model: Website
• Domain Model Function: create CNAME, delete CNAME
• Security Role: Webmaster, Editor, Visitor
• Security Profile: DNS Registry, Website