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

12/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 is a container for one or more Workspaces. A deployment has these properties;

• ID
• Code Name
• Name
• Description
• One language (eg English)
• One User Account
• One Deployment Class (type of tenancy)

Those properties are inherited by all workspaces.

Workspace

A workspace has these properties;

• ID
• Code Name
• Name
• Description
• One inherited language (eg English)
• One inherited User Account
• One Deployment
• One pre-built Domain Model (eg, Screen Production).
• One Domain Model Template (eg, Feature Film, Documentary, Live Broadcast), These templates can be customised and shared.

Those properties are inherited. This means each Workspace/Domain Model comes with 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).

Domain Model

Here is an example of Domain Model properties;

• Domain Model/Workspace: Website
• Domain Model Function: create CNAME, delete CNAME
• Security Role: Webmaster, Editor, Visitor
• Security Profile: DNS Registry, Website, Design System, CDN