Platform
Access to a box Beta
Being in an organisation does not put you on a box. Access is granted per box, per person, with one role, and the box learns about it from a signed list rather than from a request it has to trust.
Custodian roles
| Role | For | On the box |
|---|---|---|
| box admin | Whoever owns the deployment | Projects and environments, keys and rotation, settings, and everything below. |
| developer | Engineers integrating an application | Connect details, and full key management: issue, disable, enable and revoke. Plus the live view and the trail. |
| box auditor | Internal audit, compliance, an external reviewer | Read the trail, the live view, and verify. Never sees keys, and changes nothing. |
The auditor role exists so you can hand someone the evidence without handing them the controls. It is the role to give a reviewer who asks to see your audit trail during a security review.
Granting
- An admin adds a person as a custodian of a named box, with one role.
- The platform publishes a new signed access list for that box.
- The box picks it up within about a minute and records the change.
The person can now sign in to that box. Nothing was pushed to it and no inbound connection was made; the box asked, verified a signature, and acted on what it verified.
Revoking, and how fast it takes effect
Removing a custodian publishes a new signed list the same way. Be precise about the timing, because it matters in an incident:
- New sign-ins to that box stop as soon as the platform knows, because the ticket is refused at the platform before it is ever issued.
- An existing box session ends once the box sees the new list, about a minute later.
- A box that cannot reach the platform keeps honouring the last list it verified. This is the trade for a box that keeps working when we are down. Showing that list's age on screen is still to come.
There is no customer-facing way to revoke on the box itself today, so an offline box honours its last list until it can reach the platform again. Tell us if that gap matters to you before it does.
Leaving the organisation
Do both, in this order:
- Revoke their custodianships, so every box drops them.
- Disable their account, which ends platform sessions at once.
Then rotate any project key they held, since a key is a credential for a machine rather than for a person. See key lifecycle.
Every change is on the record
Grants, changes and revocations are config events on the platform's own hash-chained trail, and the box records its own copy when it acts on a new list. The platform side can also be sealed onto a box you choose. Sealing the box's own copy of custodian changes is still to come, so today the honest word for that half is recorded.