Security · Policies, approvals, and audit history
Security
Control access, route sensitive decisions, and preserve the evidence behind every change.
Read the technical documentation
Policies
Policies decide which records, fields, actions, and apps each team can use. Row-level conditions and field redaction make access specific enough for real operations, and the same rules apply in every interface and server action.
Approvals
Approval gates commit sensitive changes provisionally under a hold until the right reviewer decides. Every row the change creates or updates is stamped with the request and keeps a restore point; only participants of the request may write it in the meantime. Approval seals the change and clears the stamps, while rejection restores every touched row to its snapshot and records the decision.
Audit history
Every mutation leaves a durable trail of who changed what and when. Operational records stay easy to use while audit events and record revisions preserve the evidence behind them.
- Reusable grants for collection actions, fields, and app visibility
- One governing policy per team, evaluated on every request
- Versioned records that make approval and rollback defensible
Continue through the product
Logic
Keep business rules and connected actions inside the governed runtime.