Platform capability · Enterprise SSO & Directory
SAML, LDAP and OIDC: users sign in with their company’s own directory
Direct connectors for the identity systems enterprise customers use. SAML 2.0 with exchange of service-provider metadata, for Okta, Microsoft Entra ID and Google Workspace. LDAP and Active Directory sign-in, with directory groups mapped to roles. A general OIDC connector for any provider that follows the standard. Connections are set for one organization or for the whole platform, so each enterprise customer signs in through its own directory and its IT team controls the accounts.
Enterprise buyers expect your product to work with the directory they already use, and do not want a new set of logins. Some use Okta or Microsoft Entra ID over SAML. Some still sign in against Active Directory on their own servers. Some run their own OIDC provider. The platform connects to all three directly, so the customer’s IT team decides who has an account.
A directory group maps to a role in the platform. When IT adds someone to a group, that person gets the matching role at the next sign-in. When IT removes them, the role is taken away. Together with SCIM provisioning, the customer’s identity team handles people who join, change role and leave, and your support team does not create accounts by hand.
Connectors are configured with SAML 2.0, LDAP or OIDC settings. Users start on your product’s branded sign-in page, which sends enterprise sign-in to the configured directory or identity provider.
Every sign-in screen carries your brand
User provisioning through your customers’ own identity providers
Roles, attribute rules and resource hierarchies in one permission system
One record of every customer, app, plan and setting, with overrides for each customer
A solution architect will demo the live service against your domain model.