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 an approval flow per grant. Holders are people through a team, but also envoys, automations, and integrations, each acting under its own declared policies; only a person can approve.

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 — prepare-and-gate review for high-value changes
• Audit and telemetry — every mutation appends a history revision, the most recent 256 per record, so recent changes and the actor behind them are answerable; the runtime also keeps its own telemetry records for the host window, readable by administrators only

Policies

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

Approval workflows

See Approval workflows — prepare-and-gate lifecycle, step statuses, reroutes, and resume-on-approval.