Skip to main content
Settings & Preferences

Single sign-on (SAML 2.0)

Let people on your company's email domains sign in to Vaizy through your identity provider, such as Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud or any other SAML 2.0 identity provider. You can also require it, so nobody on those domains reaches workspace data with just a password.

Single sign-on is available on the Enterprise plan. Owners and admins set it up in Settings → Single sign-on.

Before you start

Single sign-on works for your verified email domains. Verify at least one domain in Settings → Domains first (see the Verified domains article).

You also need two-factor authentication on your own account to change security settings.

1. Add Vaizy to your identity provider

Create a SAML 2.0 application in your identity provider. Copy these values from Settings → Single sign-on into it:

  • Entity ID / Audience URI

  • ACS / Reply URL

  • Service provider metadata URL, if your identity provider can read the settings from it

  • NameID format

Send the person's email address as the NameID or as an email attribute. Make sure it is their address on your verified domain: Microsoft Entra ID sometimes sends a @yourtenant.onmicrosoft.com address instead, which Vaizy refuses.

2. Connect your identity provider

  1. Paste the Metadata URL your identity provider gives you, or upload its Metadata XML.

  2. Under Domains, choose which verified domains sign in through this identity provider.

  3. Select Connect.

The connection is saved, but nobody can use it yet.

3. Test and turn on

  1. Select Test sign-in and sign in through your identity provider with your own account. Your email address must be on one of the selected domains.

  2. After a successful test, select Turn on.

People on the selected domains now see Sign in with SSO on the Vaizy login page.

If you replace the metadata later, the last test is cleared. Test again before people rely on it.

Sign-in policy

Create accounts automatically (on by default): people your identity provider lets in join the workspace as Members on their first sign-in. When it's off, only people who already have access can sign in.

Require single sign-on: everyone on the selected domains, owners and admins included, only sees workspace data after signing in through your identity provider. Password sessions stop showing workspace data straight away. People on other domains, such as external collaborators, aren't affected.

To avoid locking yourself out, you can only require single sign-on after a successful test, and while you are signed in through single sign-on yourself.

How accounts work

Single sign-on signs people in to their existing Vaizy account with the same email address, so their projects and history stay with them. It doesn't create a second account.

Two-factor authentication still applies. If someone has an authenticator app set up, or your workspace requires it, they enter their code after signing in through your identity provider.

Removing someone in your identity provider stops new sign-ins, but a session they already have keeps running until it ends. To cut access at once, disable them in Settings → Users, sign them out in the Security center, or use SCIM provisioning, which does this automatically.

Turn off or remove

  • Turn off: people sign in with a password again. Accounts created through single sign-on can set a password with Forgot password.

  • Remove single sign-on: deletes the connection. People can no longer sign in through your identity provider, and single sign-on stops being required.

If your identity provider is down while single sign-on is required, contact Vaizy support. After checking who you are, we can switch the requirement off so an owner can sign in with a password and fix the connection.

Troubleshooting

  • "...an email address this workspace's single sign-on does not cover": your identity provider sent an address on a domain that isn't selected on the connection or isn't verified. Change the email it sends, or add and verify that domain.

  • "Your identity provider did not send an email address": map your identity provider's email attribute, or send the email address as the NameID.

  • "You don't have access to this workspace yet": the person has no access to the workspace and Create accounts automatically is off. Invite them, turn it on, or provision them with SCIM.

  • "Your access to this workspace has been disabled": an admin disabled the person in Settings → Users. Restore their access there.