Governance is designed into the application
Roles, policies, granular permissions, server-side rules and workflow controls are built in, not added before launch. They decide who can act, on what, and how changes happen.
Security and Governance
How access is decided
- Roles, policies and permissions
- Field and record level rules
- Enforced on the server
Enforced on every request
Enforced in more than one layer.
BuildPad DaaS uses defence in depth. Hiding a button is not authorization, so the rules sit lower down too.
Application
Sessions and input
JWTs are validated, sessions managed and input checked, so a request is identified before it reaches anything else.
API
Permission rules on the route
Each route checks the operation against the caller's policies, not the screen it came from.
Database
Row-Level Security in PostgreSQL
PostgreSQL Row-Level Security policies enforce access record by record, closest to the data.
Roles, policies and permissions.
Three parts, managed in one place instead of across screens.
Roles
Roles describe who a user is
- A named group, such as Editor, Viewer or Approver
- Each has an icon, a parent role and assigned users
- One user can hold several roles
- Policies attach to the role, not each screen
Users can hold several roles at once, so responsibilities combine.
Policies
Policies decide what access those roles get
- They hold the access flags and permission rules
- They attach to a role, or to one user
- A user's access is the union of everything attached
- Flags cover admin, DaaS Studio and delegate access
A user's effective access is the union of everything attached to them.
Permissions
Rules down to the action, field and record
- One rule covers one action on one collection
- Create, read, update, delete and share
- Rules set which fields and records a user reaches
- They can set valid values and defaults on create
Two kinds of access, kept apart.
Managing a project and approving a record in the app are separate systems, for separate people.
Dev Platform
BuildPad Dev Platform roles
What a person can do to the project itself and its platform resources.
- Organization and project access
- Microapps, workers and builds
- For the team building the app
Runtime
DaaS roles and policies
What users can do with the app's data while it runs.
- Collections, fields and records
- Workflow transitions
- For the people using the app
Across every application
Governance is the promise. xAppHub is the product that keeps it.
This page covers one app. At thirty apps, you need one place to see who can access what. xAppHub is that place: one portal, one access model, one reporting layer.
See xAppHubWant to see this in a real app?
We show you this part working end to end, in an app we have built.
