Postman collections

Use the collection that matches your invited organization role. Both collections use the same API as the dashboard and enforce your live organization scope on every request.

Set up

1. Download and import the collection for your role into Postman.
2. Set base_url to the dashboard origin, without a trailing slash.
3. Set identity_email and identity_password to your individual account, and set branch_organization_id to the top-level organization UUID for the context you want to use.
4. Run Authentication → Identity Login. The test script saves the returned session token as identity_jwt.
5. Run Organization & Tenants → List Tenants, then set tenant_id to a tenant returned in your scope.

Do not use Platform Admin credentials or copy an admin_jwt into these collections. A successful login does not expand permissions: deactivated identities, removed memberships, out-of-scope tenant IDs, and capabilities your role does not hold are rejected when each request runs.

Role boundaries

Organization Admin requests only include delegated actions. Platform-only billing, deployment, data-plane, branding, phone-number provisioning, portal cutover, permanent deletion, and hierarchy-migration operations are not in the collection.

Organization Operators can operate tenants already in scope. They cannot create or rename organizations, create or deactivate tenants, or invite and revoke identities. If one of those actions is required, ask an Organization Admin with the appropriate live scope.

To rename an in-scope tenant, open Tenants, select Rename on its row, enter a name between 2 and 100 characters, and save. The tenant slug and portal address do not change. The same action is available in the role-specific collection as Organization & Tenants → Rename Tenant.

API-key reveal and copy actions are audited and return no-store responses. Never save those responses as Postman examples or paste tenant API keys into URLs, logs, tickets, screenshots, or shared environments.