Concepts
The tenancy model: an account owns projects, a project has environments (sandbox and production), and each environment holds the organizations, which are your enterprise customers, with their domains, connections and directories.
The tenancy boundary is account → project → environment → organization. An account owns projects. Each project has isolated sandbox and production environments. An organization represents one enterprise customer within an environment.
| Resource | Purpose |
|---|---|
| Account | Your team and its administrative access |
| Project | One product or application |
| Environment | Isolated credentials, configuration and customer data |
| Organization | One enterprise customer |
| Domain | A DNS-verified email domain belonging to an organization |
| Connection | One organization’s SAML or OIDC configuration |
| Directory | One organization’s SCIM provisioning endpoint |
| Profile | A sign-in identity scoped to a connection |
Keep the environment and organization IDs alongside your own tenant ID. Never select a tenant solely from a browser-supplied organization ID or an email address. Resolve it from your application’s trusted tenant context and check the returned profile’s organization.
Secret keys authenticate server requests; publishable keys identify the SSO client. Neither a sandbox key nor an object ID grants access to another environment. Scope server keys to the resources your integration needs.
An SSO connection and a SCIM directory are separate resources. Directory provisioning can begin before SSO is active; it does not prove a successful sign-in. See ordering and setup status.