Single sign-on
Let your team sign in with Okta, Microsoft Entra, Google Workspace or another identity provider, and make it the only way in.
Updated November 17, 2026
Single sign-on lets people in your company sign in to your siz.la account with the work login they already use. It comes with the Business plan, and only the account owner sets it up. Admins can see how it is set up but cannot change it. It works with any identity provider that supports SAML 2.0 or OpenID Connect, including Okta, Microsoft Entra, Google Workspace, OneLogin and JumpCloud.
Set it up
Open Team in the menu, choose Single sign-on, and work down the page.
- Claim your domain. Type the domain your team's email addresses are at, such as company.com, and choose Add domain. Add the TXT record shown to your domain's DNS, wait a few minutes, and choose Check now. This proves the domain is yours. Only addresses at a verified domain can sign in to your account. Free mail services such as Gmail and Outlook cannot be claimed.
- Give your identity provider our details. Pick SAML 2.0 or OpenID Connect and copy what the page shows into a new application in your identity provider. For SAML that is the entity ID, the ACS URL and, if your provider can read it, the metadata address. For OpenID Connect it is the redirect URI. Set the name ID to the work email address and send the email address as an attribute named email as well. The answer must be signed.
- Give us your identity provider's details. For SAML, paste the metadata address your provider shows, or paste the metadata XML. For OpenID Connect, enter the issuer address, the client ID and the client secret. The secret is stored encrypted and is never shown again.
- Turn it on. Pick the role new people get, then choose Turn on.
Sign-in starts from siz.la, not from your provider's list of apps.
How people sign in
On the sign-in page, people choose Sign in with single sign-on, enter their work email address and are sent to your identity provider. When they come back they are signed in.
The first time someone at your domain signs in, they join your account as a team member with the role you picked, and they take a seat. Check the Team page to see how many seats your plan has. If every seat is taken, they cannot join until you free one.
Someone who already has a siz.la account with the same email address is never joined this way, because nothing proves the account is theirs. The owner invites them from the Team page instead. After they accept, single sign-on works for them.
Each person is tied to the identity your provider gave them the first time they signed in. A later sign-in has to be the same identity. The account owner always signs in the usual way, with a password, and never through single sign-on.
If you change the identity provider, single sign-on turns off until you have tried it again, and everyone is tied to a fresh identity on their next sign-in.
To take someone off the account, remove them on the Team page. Signing in with single sign-on does not bring them back.
Require single sign-on
Once someone in your team has signed in with single sign-on, you can turn on Require single sign-on. People in your team can then sign in only through your identity provider, and not with a password or with Google or Facebook. People who are signed in with a password when you turn it on are signed out. Nobody can make a new account with a password at your domain either.
You, as the owner, keep your own password, so you can still get in if your identity provider is down or set up wrong. Accounts at your domain that are not in your team are not touched.
If your account moves to a plan without single sign-on, the requirement stops and everyone can use a password again.
Good to know
- Every sign-in and every change to the setup is written to the activity log.
- siz.la's own two-step sign-in does not ask for a second code after single sign-on. Your identity provider handles that.
- If you remove single sign-on, the people who joined through it keep their accounts. They can set a password with Forgot your password? on the sign-in page.
Did this help?
More in Domains and teams
Still stuck? Send us a message.