Skip to content
SkyKeephelp

Vault administration

The per-vault admin console is where an engagement's administrator

manages compartments, user accounts and their grants, reviews

quarantined uploads, and adjusts the vault's configurable settings.

The console holds no power of its own: every act travels the same

verified, audited data access layer as any other request, the vault's

engine re-checks admin authority on every write, and the set of

configurable settings is a closed list — the console can never be

talked into storing a setting the vault does not know. The vault is

also local-first: it refuses to start at all if its model endpoint

points outside the deployment, unless the operator has explicitly

accepted that egress — and then every model call is put on the record.

The console refuses a visitor who is not an administrator

A setting outside the vault's vocabulary is refused

The vault refuses to start when its model lives outside the deployment

An explicit operator override puts model calls on the record

Disabling an account blocks new sessions immediatelystack

A member cannot administer the vaultstack