Single sign-on and SCIM
Updated October 10, 2026
Enterprise security lets your company sign in through its own identity provider (IdP) and manage members from it. It is labelled Beta.
It depends on your plan and must be turned on by InfluenceBot support. When it is on, Settings → Enterprise security appears. Only the workspace owner can change these settings.
Note: The page shows the IdP and DNS modes. In MOCK mode, sign-in uses a built-in test identity provider and only reserved test domains (.test, .example) can be verified. Connecting a real identity provider needs live mode.
1. Verify your domain
- Under Domains, enter your company email domain and select Add domain.
- Publish the DNS TXT record shown (Name and Value) at your DNS provider.
- Select Verify. The status becomes Verified.
Public email domains like gmail.com can't be claimed.
2. Add an SSO connection
- Under SSO connections, select New OIDC connection or New SAML connection.
- For OIDC, enter the Issuer URL, Client ID and Client secret. For SAML, paste the IdP metadata XML.
- Choose the Default role for new members. Tick Create members on first sign-in (just in time) if new colleagues should be added automatically.
- Select Create connection. Register the Redirect URI (OIDC) or the ACS URL and SP entity ID (SAML) at your IdP.
- Select Test connection, then Activate.
People then sign in with Sign in with SSO on the sign-in page: they enter their Work email and select Continue with SSO.
3. Enforce SSO (optional)
Select Enforce SSO on a verified domain. Password and magic-link sign-in are refused for that domain. The owner keeps an audited emergency sign-in.
4. Provision members with SCIM
- Under SCIM provisioning, enter a Token name and an expiry, and select Create token.
- Copy the token right away ("This is the only time the token is shown"). Paste it and the SCIM base URL into your IdP.
- Under Group → role mapping, give each group pushed by your IdP a role. Members get the highest role of their groups. A group never grants the owner role.
Deprovisioning in your IdP suspends the membership and signs the person out everywhere. Each new member needs a free seat.
Messages you may see
- "Verify a domain before adding a connection."
- "Run “Test connection” successfully before activating it."
- "Activate an SSO connection for this domain before enforcing SSO, so people can still sign in."
- "Your plan does not include enterprise SSO. Nothing was changed."
- "The organization has no free seat for a new member. Ask an administrator."
