Company SSO
Connect a verified company domain to a SAML identity provider
Company SSO lets allowed employees join/sign in through the workspace's SAML provider. It supports a configured company domain, proof of DNS ownership, provider metadata, a test sign-in and explicit activation. Password, Google and Microsoft sign-in remain available where enabled; this flow does not enforce SSO-only authentication.
Company SSO setup is self-service: workspace owners can configure, test and activate it in Settings → Company SSO using this guide.
Need help with setup? Contact us and tell us which identity provider you use and where you’re stuck
Requirements
Before configuring SSO, create a Semogram account using email and password, Google or Microsoft where available. Create your company workspace, or open an existing workspace where you are the Owner, then go to Settings → Company SSO and follow the setup steps below.
Keep your original sign-in method available while configuring and testing SSO. You don’t need an existing SSO connection to create your account or workspace.
If you’re an employee trying to sign in, your workspace owner must configure and activate SSO, allow your email and arrange access in your company’s identity provider. If SSO isn’t ready or sign-in is denied, contact your workspace owner.
You need a Semogram account as workspace Owner, access to the company domain's DNS and administration access to its SAML identity provider. The deployment must support the configured SSO provider integration. Administrator role alone does not manage Company SSO.
The sign-in page shows Continue with SSO, and Settings → Company SSO offers setup, only when the installation has SAML sign-in enabled. Otherwise both say that Company SSO is not enabled on this installation. Google and Microsoft sign-in buttons likewise appear only when those providers are enabled; email and password sign-in is always available.
Have your own testing identity assigned to the SAML application. The owner test can grant the verified company identity your existing workspace ownership/permissions while the original account retains access for recovery.
Example company setup
For a company using example.com, open Settings → Company SSO and follow the numbered steps:
- Enter example.com as Company domain and save it.
- Add the displayed TXT record
_semogram-sso.example.comwith the exact displayedsemogram-sso=<verification token>value. Select Verify DNS record after propagation. Do not substitute the illustrative token. - In the identity provider create a custom SAML application using the ACS URL and Entity ID / Audience displayed by Semogram. Configure Name ID as primary email with
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress. - Assign your test account in the provider and download its metadata XML.
- Upload the fresh metadata XML (maximum 256 KB) and save the connection.
- Select Test sign-in and retain ownership. Complete provider sign-in and verify the test-passed state on return.
- Select Activate Company SSO after the successful test.
- Add each allowed Employee email in Member access. An employee must also be assigned in the provider and use the supported Company SSO sign-in flow.
Copy the deployment's displayed provider endpoints; do not construct them from an example host. Cloudflare-assisted DNS setup is available only when the deployment/provider template supports it; manual TXT verification remains the explicit path.
Access and membership
New permitted employees join as Member. A company-domain email alone is not an authorization grant. Review their custom read and write-policy permissions after joining.
Removing an email from Allowed employees prevents future joins but keeps existing workspace membership.
Disabling new SSO sign-ins is a pause. Nobody can sign in through the provider, but members who already signed in keep their access and sessions. Activating again restores sign-in without other setup.
Removing the connection ends SSO access. Every member who signed in through the provider, including an SSO owner account created by the test sign-in, is signed out everywhere and removed from the workspace. Then the provider, verification, tests and allowlist are deleted and the domain is released. The confirmation shows how many members will lose access. Removal is refused if it would leave the workspace without a non-SSO owner. Their accounts are not banned; without the provider they cannot sign in. To restore SSO, verify the domain, upload metadata, test, activate and allow members again. Removal does not delete service keys or earlier data.
Domain ownership
Several workspaces can claim the same domain, but only one can hold it verified, so an unverified claim never blocks the company that owns the domain. Verification checks the DNS record every time: when you verify, start a test sign-in and activate SSO. If another workspace holds the domain verified, verifying moves the domain to your workspace once that workspace's own record is no longer published. Whoever controls the domain's DNS decides. Losing a domain is not a pause:
- Taken over: the previous workspace's identity provider is deleted, and the members who signed in through it are signed out and removed from that workspace. If removing them would leave it without an owner who signs in another way, they stay members, but their SSO sessions still end.
- Record removed: if company sign-in finds the record gone while nobody else claims the domain, the domain becomes unverified and Company SSO is turned off. Members who signed in through the provider are signed out on their next request; their memberships stay, so verifying and activating again lets them sign back in.
The workspace that lost the domain sees the date and reason on its Company SSO settings page.
Company sign-in is limited to 20 attempts per minute from one network address.
Maintenance and troubleshooting
| Problem | Check |
|---|---|
| Owner access denied | Current workspace and owner identity |
| Record not found | Exact TXT name and DNS propagation |
| Value mismatch | Complete token value, not just the domain |
| Test fails | ACS/Audience, Name ID format, assignment and current metadata |
| Employee cannot join | Active connection, exact allowed email and provider assignment |
| Certificate rotates | Disable as required by the settings workflow, upload fresh metadata, test and reactivate |
The configured domain is read-only once saved. Review the UI's connection removal/reconfiguration flow for a domain change. Retain an owner recovery identity before changing the provider.
SSO setup is a signed-in owner workflow; no public API-key or MCP connection-creation action is exposed. An assistant can help review settings and DNS instructions, but must not invent an SSO mutation tool.
To sign in, select Continue with SSO, enter your work email, then select Sign in. Your company identity provider completes authentication.
Troubleshooting sign-in
If Company SSO reports that sign-in is unavailable, contact your workspace owner. Platform operators can inspect JSON server trace logs for server_failure to distinguish connection lookup, DNS verification, and sign-in provider failures. Use the displayed reference ID to find the log with context company_sso_sign_in. These logs exclude employee emails and authentication secrets.