Integrations
Connect applications for single sign-on, provision accounts downstream, protect APIs, define roles, and federate sign-in.
The Integrations area is where you connect the platform to the rest of your application landscape. It covers everything from giving users single sign-on into an application, to automatically creating their accounts in that application, to protecting your own APIs, to letting users sign in with an external identity provider.
What you manage here
| Page | Purpose |
|---|---|
| Applications | Register the applications your users sign in to — over OpenID Connect, SAML 2.0, or WS-Federation — from a pre-built catalog or as a custom app. |
| Application provisioning | Automatically create, update, and deactivate accounts in downstream applications using outbound SCIM. |
| APIs | Define the APIs and resources you protect, the scopes they expose, and which applications may call them — including machine-to-machine access. |
| Roles | Group API permissions into roles and assign them to users and groups, so applications can make role-based authorization decisions. |
| Connections | Delegate sign-in to external identity providers (generic OIDC/SAML, Microsoft Entra, or a social provider such as Google, Apple or GitHub), with account linking and just-in-time user creation. |
| Integration catalog | Browse the pre-built integrations by name, vendor, protocol and category before you add one. |
| Dynamic client registration | Let OpenID Connect clients register and manage themselves, authorized by initial access tokens you issue. |
How the pieces fit together
A typical onboarding looks like this:
- Register the application so users can sign in to it. Most catalog applications and all custom applications start on the Applications page.
- Decide who can use it by assigning the application to users, groups, directories, or organizations.
- Set its sign-in requirements — for example, always require multi-factor authentication, or apply a conditional-access policy.
- Provision accounts so users do not have to be created by hand in the downstream system. See Application provisioning.
- If the application calls one of your APIs, define and protect that API under APIs, and optionally model fine-grained access with Roles.
Federated sign-in is the mirror image of the first step: instead of an application trusting the platform, the platform trusts an external identity provider so your users can "sign in with" it. That is configured under Connections.
Note: Several capabilities on these pages are gated by your subscription tier or add-ons. Each gated page or section opens with a callout. See Plans & add-ons for the full matrix.