Skip to content

Vault

The vault holds the credentials that a workspace uses to bind connector requirements to authenticated accounts. A persona declares logical requirements and references. The workspace supplies the specific account and its grants.

A personal connection is resolved for the person a run acts for. A shared app destination requires its own approved binding and permitted operations. The runtime resolves and uses credentials on the service side. A persona definition and install preview can show the logical requirement and the operations it needs. Secret values belong in the workspace’s account store.

Item Where it belongs
calendar requirement and upcoming operation Portable playbook
Calendar account and its grant Workspace binding and Vault
Token or provider credential Protected credential storage
Account used for a real dispatch Restricted run evidence as a reference
Requirement: calendar (personal)
Operation: upcoming
Selected connection: member-authorized Google Calendar
Effective grant: read upcoming events within the playbook’s declared operation

When an account is revoked, expired, or replaced, recheck it before the next operation. An approval for an old acting account does not transfer to a materially different proposal. If an effect may already have been sent, reconcile it against its receipt before repeating it with a new binding.

See connectors, bindings, and execution receipts.