Security

Access in a bolt is policy-based: reusable grants assigned to teams, evaluated inside the runtime on every read and mutation, with approval gates on top.

The model

Users belong to team s, and a team holds a policy that grants operations on collections — with row conditions, field redaction, and approval config per grant.

Building blocks

• Teams — the unit of assignment; a user belongs to one team, or none before somebody places them
• Policies — reusable grants that say who can do what to which collections
• Redaction — attribute-level hiding that applies at read and write time
• Approval gates — write-then-lock for high-value changes that need review
• Audit — every mutation recorded, so what happened and who did it is answerable

Policies

See Policies — grants, row conditions, redaction, mutation outcomes, and recommended authoring order.

Approval workflows

See Approval workflows — write-then-lock gates, step statuses, reroutes, and versioned rollback.