Pipi 9 RBAC

Mike's Notes

This is a summary of the RBAC (Role-based access control) now used globally within Pipi 9.

Resources

• https://www.blog.ajabbi.com/2025/09/namespace-engine-key-to-rbac.html
• https://www.blog.ajabbi.com/2025/09/rbac-policies.html
• https://www.blog.ajabbi.com/2025/09/rbac-causes-change-to-deployment-engine.html
• https://www.blog.ajabbi.com/2025/09/role-based-access-control-rbac.html

References

• Reference

Repository

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

Last Updated

18/09/2025

Pipi 9 RBAC

By: Mike Peters

On a Sandy Beach: 18/09/2025

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

Summary

Pipi 9 uses automated RBAC (Role-based access control) to control user access to everything that has a namespace.

Pipi 10 will have additional authorisation frameworks available to be chosen by enterprise accounts.

User Account Properties

• ID
• Code Name
• Namespace
• Name
• Default Language
• Global authorisation framework (RBAC)
• Account type
• ...

Deployment Properties

• ID
• Code Name
• Namespace
• Name
• Description
• Language (eg English)
• Inherited User Account
• Deployment Class (type of tenancy)
• ...

Workspace Properties

• ID
• Code Name
• Namespace
• Name
• Description
• Inherited language (eg English)
• Inherited User Account
• Inherited Deployment
• Domain Model
• Domain Model Template
• ...

Autonomous Agent Properties

• ID
• Code Name
• Namespace
• Name
• Description
• Agent Type (Pipi System, Engine, Domain, Algorithm, CAS, Digital Twin, etc.
• ...
• Many Roles
• Many Policies
• ...