Feature · Revoke / Sever
ShippedOne revocation. Everything under it stops.
Pull a grant at the source and each wire issued under it, plus everything descended from it, stops working immediately. No hunting through individual integrations to clean up access by hand.
What it does
Revocation is a single act, not a checklist.
Grants form a chain: a capability granted to an agent, delegated onward to a sub-task, wired into a specific tool call. Revoking at any point in that chain severs everything downstream of it in one operation.
The same grant, delegated, and revoked mechanism also covers sharing outward: giving a contractor, a partner, or an outside agent access to something you hold, with the same signed receipt and the same one-action revocation if you need it back. Delegating to an external party is newer than internal delegation chains and has seen less production use, so treat it as early rather than as hardened as the core grant path.
How it works
Descendants are tracked, so severing one severs all of them.
Because each delegation is recorded at grant time, SynOI knows what depends on what. Revoking a grant does not just stop new requests under it; it invalidates everything already issued that traces back to it, across whichever tools or providers it touched.
This is what offboarding an integration, a compromised agent, or a departing employee actually needs: one action with a complete, provable blast radius, rather than a per-provider cleanup task you hope you did not miss a step on.
Status
Shipped.
Revocation and offboarding both run on this same mechanism today, as part of the core grant engine.
Cut access once, not once per integration.
Set up a grant chain and see what a single revocation actually reaches.