Set up SSO (SAML)

Connect Okta, Google Workspace or Microsoft Entra ID so your team signs in to Higgsfield with their company accounts.

Single sign-on (SSO) lets your team sign in to Higgsfield with their company accounts. Once SSO is on, anyone with an email on your company's domains signs in through your identity provider: Okta, Google Workspace or Microsoft Entra ID.

SAML SSO with Okta, Google Workspace or Microsoft Entra ID is part of the Enterprise plan. Setup takes about 20 minutes, plus the time your DNS change takes to appear.

Before you start

You'll need:

  • Owner access to your main Enterprise workspace. Only the workspace Owner can set up SSO. Sub-workspaces don't have their own SSO settings: the setup in your main workspace covers them.
  • Admin access to your identity provider: an Okta or Microsoft Entra ID admin, or a Google Workspace super administrator.
  • Access to your domain's DNS settings, or someone on your IT team who can add a TXT record.
  • Your company email domains, for example company.com. Public email domains such as gmail.com can't be used.

Setup has five steps:

  1. Verify your company email domains.
  2. Choose your identity provider.
  3. Create a SAML app in your identity provider.
  4. Bring your identity provider's metadata back to Higgsfield.
  5. Test sign-in.

Step 1. Verify your company email domains

Verifying a domain proves that it belongs to your company.

  1. Open Manage account → Organization. In the Security section, select Set-up SSO.
  2. Under Company email domains, enter your domain (for example, company.com) and select Add.
  3. The domain appears as Pending verification, with a DNS record to add:
    • Type: TXT
    • Name: _higgsfield-verification
    • Value: The value shown in Higgsfield. It starts with hf-verify=
    • Use Copy next to Name and Value. If your DNS provider asks for the full record name, use the full name Higgsfield shows under Name, for example _higgsfield-verification.company.com.
  4. Add the TXT record in your DNS provider's settings.
  5. Back in Higgsfield, select Check. Once the record is visible, the domain shows Verified.

DNS changes can take up to an hour to appear. If Higgsfield says The TXT record is not visible yet, wait a few minutes and select Check again.

Repeat these steps for every email domain your team uses, for example company.co.uk. Verify all of them before you continue: once SSO is on, adding or removing a domain goes through Higgsfield support. Keep the TXT records in place after verification.

Step 2. Choose your identity provider

  1. Under Identity provider, select Okta, Google (Google Workspace) or Microsoft (Microsoft Entra ID).
  2. Select Continue.

Higgsfield now shows two values to copy into your identity provider. Keep this window open:

  • ACS URL: the Assertion Consumer Service URL.
  • SP Entity ID: the Service Provider ID, also called the Audience URI.

Step 3. Create the SAML app in your identity provider

Follow the steps for your provider. The first hint in the Higgsfield setup window describes Okta's menus; for Google Workspace and Microsoft Entra ID, use the steps below instead.

Okta

  1. In the Okta Admin Console, go to Applications and Resources → Applications (Applications → Applications in older consoles) and select Create App Integration. If Okta offers a choice, pick Classic experience.
  2. Choose SAML 2.0 as the sign-in method and select Next.
  3. Enter an app name, for example Higgsfield, and select Next.
  4. Paste the values from Higgsfield:
    • Single sign-on URL: the ACS URL.
    • Audience URI (SP Entity ID): the SP Entity ID.
  5. Set Name ID format to EmailAddress and Application username to Email.
  6. Select Next. On the feedback page, choose I'm an Okta customer adding an internal app and This is an internal app that we have created, then select Finish.
  7. On the app's Sign On tab, under Attribute Statements (SAML), select Add expression and add:
    • mail: user.profile.email — Required
    • firstName: user.profile.firstName — Optional
    • lastName: user.profile.lastName — Optional
    • In older Okta consoles, the creation wizard has an Attribute Statements section instead. Add the same names there, with the values user.email, user.firstName and user.lastName.
  8. On the Assignments tab, assign the people or groups who will sign in to Higgsfield.
  9. On the Sign On tab, copy the Metadata URL. You'll paste it into Higgsfield in step 4.

Google Workspace

  1. In the Google Admin console, go to Apps → Web and mobile apps and select Add app → Add custom SAML app.
  2. Enter an app name, for example Higgsfield, and select Continue.
  3. Under Option 1: Download IdP metadata, download the metadata file and keep it. You'll upload it to Higgsfield in step 4. Select Continue.
  4. Paste the values from Higgsfield:
    • ACS URL: the ACS URL.
    • Entity ID: the SP Entity ID.
  5. Set Name ID format to EMAIL and Name ID to Basic Information → Primary email, then select Continue.
  6. Under Attribute mapping, add:
    • Primary email: email — Required
    • First name: firstName — Optional
    • Last name: lastName — Optional
  7. Select Finish.
  8. Open the app's User access settings and turn the app on: ON for everyone, or only for the organizational units or groups that use Higgsfield. Select Save. Google can take up to 24 hours to apply this change, though it's usually much faster.

Microsoft Entra ID

  1. In the Microsoft Entra admin center, go to Entra ID → Enterprise apps → All applications (Enterprise applications in the Azure portal) and select New application → Create your own application.
  2. Enter an app name, for example Higgsfield, choose Integrate any other application you don't find in the gallery (Non-gallery), and create the app.
  3. Open Users and groups, select Add user/group, choose the people or groups who will sign in to Higgsfield, and select Assign.
  4. Open Single sign-on, choose SAML, and edit Basic SAML Configuration:
    • Identifier (Entity ID): the SP Entity ID.
    • Reply URL (Assertion Consumer Service URL): the ACS URL.
    • Select Save.
  5. Under Attributes & Claims, check that these claims are in place. They're usually there by default:
    • http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress: user.mail — Required
    • http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname: user.givenname — Optional
    • http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname: user.surname — Optional
  6. Under SAML Certificates, copy the App Federation Metadata Url. You'll paste it into Higgsfield in step 4.

Step 4. Bring the metadata back and turn on SSO

Pick a quiet time. From the moment you save, everyone with an email on your verified domains must sign in through your identity provider. If something is wrong, they can't sign in until you fix it or select Disable. Before you save, make sure you're assigned to the app in your identity provider, so you can test sign-in right away.

  1. Back in Higgsfield, find the last step in the setup window, Bring Okta's metadata back (or Google's, or Microsoft's), and add your identity provider's metadata:
    • Okta or Microsoft Entra ID: paste the metadata URL into the field, or copy it and select Paste.
    • Google Workspace: under or upload XML Metadata, drag in the XML file you downloaded, or click the upload area to choose it.
  2. Select Save configuration.

SSO turns on right away. The Security section shows SSO is enabled. Members can sign in with your company account.

Step 5. Test sign-in with SSO

Keep your current Higgsfield window signed in, and test in a private (incognito) browser window:

  1. Open the Higgsfield sign-in page and select Continue with SSO.
  2. Enter your Work email and select Continue with SSO. Higgsfield redirects you to your identity provider.
  3. Complete your company’s sign-in process. After you return to Higgsfield, open the profile menu and select your Enterprise workspace.

If the new setup blocks sign-in, go back to the window where you’re still signed in and select Disable in Security. Fix the SAML app settings with your IT team, then select Enable and test again.

After SSO is on

  • Invite people by default. SSO controls how people sign in. People still need an invitation unless automatic joining through SSO is enabled for your workspace or your identity provider has added them through Directory Sync. Send invitations to your team’s work emails from Manage account → Members. To add and remove people automatically from your identity provider, set up Directory Sync (SCIM).
  • Only assigned people can sign in. Someone on your domain who isn't assigned to the Higgsfield app in your identity provider can't sign in with SSO.
  • Start sign-in from Higgsfield. Signing in from your identity provider's app dashboard isn't turned on by default. If your team needs sign-in from an app tile, such as the Okta dashboard, ask your Higgsfield account manager to enable it.
  • Turn SSO off or on. In the Security section, select Disable. Your configuration is saved, and you can select Enable at any time. Disabling SSO doesn't turn off Directory Sync (SCIM); turn that off separately.
  • Finish setup later. If you close the setup window before you select Continue, your domains are saved: select Set-up SSO again to pick up. If you close it after Continue, the Security section shows Setup in progress. Select Continue setup.
  • Change your setup. To add or remove domains, switch identity providers or update the metadata after SSO is on, contact your Higgsfield account manager or enterprise@higgsfield.ai.

Troubleshooting

Troubleshooting

What you see

What to do

The TXT record is not visible yet. DNS can take up to an hour to update

Check that the record's Name and Value match Higgsfield exactly. Wait a few minutes, then select Check again.

Could not read DNS for this domain right now. Try again in a minute

Wait a minute, then select Check again.

A message about too many verification attempts

Wait a while before you select Check again.

A shared email provider cannot be used for SSO

Use your company's own email domain.

This domain is already used by another SSO connection.

The domain is already connected to SSO for another Higgsfield workspace. Contact enterprise@higgsfield.ai.

No Set-up SSO in Manage account → Organization

Only the Owner of your main Enterprise workspace sees the SSO settings. Ask your workspace Owner.

We couldn't find an SSO setup for this email. Try another email or use regular login

SSO isn't on for this email's domain. Check the email, or ask your workspace Owner whether SSO is enabled.

An error page from your identity provider

Check that the person is assigned to the app, and that the ACS URL, SP Entity ID and email attribute match the steps above.

Signed in, but the workspace isn't there

Check that you used your work email. Ask your workspace Owner whether you have an invitation, were added through Directory Sync (SCIM), or can join automatically through SSO.

If sign-in opens your personal workspace, select the Enterprise workspace from the profile menu. Check that the email in Manage account → Personal profile matches the work email on your invitation.

Your IT team manages sign-in and account recovery for company SSO. If you still need help, contact your IT team, your Higgsfield account manager, or enterprise@higgsfield.ai. Include the error message and the approximate time of the attempt, with your time zone.

FAQ

Got any questions left?