Multi-Account Operations
Running APIANT for many customer accounts — account-level isolation, linked accounts for multi-location, shared credentials, and admin keyvault.
Customers run as accounts inside your APIANT tenant. Each customer's data is isolated at the account level, multi-location customers use linked accounts to share state across locations, and credentials are scoped per-account or admin-shared via the keyvault.
- Tenancy and Linked Accounts — how accounts isolate customer data, and how linked accounts let multi-location customers share state.
- Shared App Connections — sharing OAuth apps and API keys across customer accounts when safe.
- Credentials — keyvault storage, admin scope, per-user connection credentials.
In this section
Tenancy and Linked Accounts
How APIANT isolates customers via tenants and supports multi-location customer deployments.
Shared App Connections
Sharing one connection from a parent account across all of a multi-location customer's linked child accounts — keeps config simple and applies one rate-limit budget across every location.
Credentials
How APIANT stores and resolves credentials at user, connector, and tenant scopes.