Single sign-on
Single sign-on (SSO) lets members sign in to Standard Compute with their existing work accounts. Your company’s identity provider handles sign-in, and Standard Compute determines which company resources each member can access.
Standard Compute supports compatible SAML 2.0 identity providers. The setup walkthrough below uses Microsoft Entra ID as an example; Microsoft is not required to use SSO.
Before you start
You’ll need:
- A Standard Compute company administrator account with the Single sign-on feature available.
- Permission to configure a SAML application in your identity provider, and access to your company’s DNS records.
- A test work account, and a recovery administrator who can sign in to Standard Compute without SSO.
Example: set up Microsoft Entra ID
1. Verify your domain
In Standard Compute, select your company and open Compliance → Single sign-on (SAML). Add your work-email domain and create the DNS TXT record shown in the dashboard. Then return to check verification.
Copy the record’s name and value exactly. Your email MX records stay unchanged.
2. Configure the Microsoft application
In Microsoft Entra admin center, open Enterprise applications and create a non-gallery application for Standard Compute. Choose Single sign-on → SAML.
Copy these values from Standard Compute’s SSO settings into Basic SAML Configuration:
| Microsoft field | Value |
|---|---|
| Identifier (Entity ID) | Entity ID from Standard Compute |
| Reply URL (ACS URL) | ACS URL from Standard Compute |
Under Attributes & Claims, use user.objectid for Name ID with the persistent format, and map the email claim to the member’s actual work email on your verified domain.
Assign your test member to the application. Set Assignment required? to Yes to restrict Microsoft sign-in to assigned users.
3. Save and test the connection
Copy Microsoft’s App Federation Metadata URL into Standard Compute’s SSO settings and save. Choose Test sign-in and sign in with the assigned test member’s Microsoft account.
The test checks the connection while keeping your administrator session signed in. It does not enroll the test member. Confirm that the test passes and your recovery administrator can still sign in.
4. Enable SSO
Choose Enable SSO in Standard Compute. Share standardcompute.com/signin with your members: choose Continue with SSO, enter a work email, and sign in through your identity provider.
Already a company member? Use Connect your existing membership to SSO in the company’s SSO settings. Follow the prompts to verify your existing Standard Compute account and your work identity.
What happens after setup
Members use their work accounts to reach the website. Your identity provider handles authentication; Standard Compute company roles and permissions determine access. SSO does not grant administrator rights. Personal access and other company memberships remain separate.
Website SSO does not assign paid plans, configure Claude Desktop, or automatically synchronize member removal. Remove members and revoke relevant credentials in Standard Compute when they leave; disabling their work account alone does not guarantee that existing Standard Compute sessions or API keys stop working.
Pause new SSO enrollment stops new members joining through SSO. It does not disable access for existing members.
If sign-in fails
Check the Entity ID and ACS URL, the member’s application assignment, and the email claim’s verified domain. If the test succeeds but members cannot sign in, confirm that SSO is enabled. Keep your recovery administrator available when changing the connection.
For the Microsoft-side screens, see Microsoft’s SAML setup guide.