Verified Domains
SSO works only for email addresses at a domain you’ve proved you own. Use the domain of the email address your identity provider sends, such asacme.com rather than acme.onmicrosoft.com.
- Under Verified domains, enter one or more domains in Add a domain. Separate several with commas or spaces, then select Add.
- Each domain appears with a Host and a TXT value. Add that TXT record at your DNS provider. DNS changes can take a few hours to show up.
- Select Verify on the domain.
A verified domain is checked again every day. If its record can’t be found, the domain shows a warning with the date SSO from that domain stops, 7 days after the first missed check. Restore the record and select Re-check before then.
A domain can be verified by only one account at a time. To take a domain off SSO, select the bin icon on its row and confirm Remove domain. SSO stops for that domain, and existing users keep their access.
Anyone your identity provider lets in, at one of your verified domains, joins your account the first time they sign in with SSO. Control who can sign in by choosing who is assigned to the app in your identity provider.
Connect Your Identity Provider
Under SSO provider, you connect one provider. Verify a domain first: until you do, the section says “Verify a domain above before adding a provider.”- Under Choose your identity provider, select Okta, Microsoft Entra ID or Google Workspace.
- Choose the protocol. SAML is recommended, because it connects from one metadata URL. Use OIDC if your IT team prefers it. Google Workspace connects with SAML only.
- Under Add Squawk Studio in your provider, follow the setup instructions shown for it, and copy the values Studio gives you into a new app in your identity provider. For SAML these are the SP Entity Id and the Redirect URL, labelled the way your provider names them. For OIDC it is the redirect URL. Assign the people who need access to that app.
- Bring the connection details back to Studio.
- SAML: paste your provider’s metadata URL and select Connect. Google Workspace has no metadata URL, so paste the contents of the
GoogleIDPMetadata.xmlfile you download from the Google Admin console. To type the details instead, select Enter values manually instead and fill in IdP Entity Id (Issuer), IdP Sign-In URL and X.509 certificate. - OIDC: enter the Client Id and Client secret from your provider, and the Issuer URL. For Microsoft Entra ID, enter the Directory (tenant) ID, Application (client) ID and Client secret, using the secret’s Value. Then select Save provider.
- SAML: paste your provider’s metadata URL and select Connect. Google Workspace has no metadata URL, so paste the contents of the
- You see “SSO provider saved”, or “Connected. SSO provider saved.” after Connect, and the section shows Connected.
Require SSO
Until you require it, SSO is an extra way to sign in: password and Google sign-in keep working. Under Sign-in rules, turn on Require SSO to make SSO the only way in.- Switch on Require SSO. The Require SSO? window says “This account’s users at its verified domains will only be able to sign in with SSO. Password and Google sign-in stop working for them, and anyone signed in that way is signed out.”
- Select Require SSO to confirm. You see “SSO is now required”.
Signing In With SSO
On the Studio sign-in page, select Sign in with SSO below the sign-in form. If you’ve already typed your email address, it’s carried over.- On Continue with SSO, enter your Work email and select Continue. If the domain isn’t set up for SSO, you see “Single sign-on is not set up for this email domain. Check the address, or sign in another way.” Select Go back to return to the usual sign-in.
- Select Sign in with your company account. Your identity provider opens in a window. Sign in there, and you’re taken into Studio. If the window is blocked, allow pop-ups for the site and try again.
Troubleshooting
I see 'Single sign-on is available on the Enterprise plan.'
I see 'Single sign-on is available on the Enterprise plan.'
- SSO is part of the Enterprise plan. Contact support@squawkvoice.ai to ask about it
A domain stays on Waiting for DNS or Record not found
A domain stays on Waiting for DNS or Record not found
- Check that the Host and TXT value at your DNS provider match what Studio shows, with nothing added or cut off
- DNS changes can take a few hours to show up. Select Verify again later
A domain won't verify and the record is correct
A domain won't verify and the record is correct
- A domain can be verified by only one account at a time. If another account has already verified it, contact support@squawkvoice.ai
Someone can't sign in with SSO
Someone can't sign in with SSO
- Check that they’re assigned to the app in your identity provider
- Check that their email address is at one of your verified domains and that the domain shows Verified
- If the provider’s secret or certificate has expired, enter the new one under Change provider details
Next Steps
Users
Invite teammates, and how people sign in.
Okta SSO
Set up SSO with the SquawkVoice app in the Okta Integration Network.
Microsoft Entra ID SSO
Set up SSO with Microsoft Entra ID.
Google Workspace SSO
Set up SSO with a custom SAML app in Google Admin.
Security
How SquawkVoice protects your data.