Use cases → Multi-tenant and agencies
Keep a registry of which tenant granted which scope
The single document that turns a multi-tenant delegation outage into a ten-minute fix.
| Who it is for | Anyone operating delegation across more than one domain. |
|---|---|
| APIs | Sheets API |
| Typical scopes | spreadsheets |
The problem
When something breaks, the question is always 'what is authorized where' — and the answer lives in three admin consoles and one person's memory.
How it works
- Record every scope, the tenants it is granted in, and what depends on it.
- Update it as part of any grant change, not afterwards.
- Have the health check read from it so drift is detected automatically.
What changes
Drift between intention and reality becomes visible instead of theoretical.
Questions people ask
Cannot this be read from the API?
Not directly — there is no endpoint listing your delegation grants. Keeping the registry is the only reliable answer.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Produce per-client reporting from a shared estate
Generate and deliver each client's own report from data that lives across several tenants.
Run one automation estate across several brands
Share the machinery while keeping each brand's identity, sender and data cleanly separate.
Operate several Workspace tenants from one service account
Authorize the same client ID in each domain and switch tenants simply by changing who you impersonate.