Skip to content

SSO and SCIM (team provisioning)

Updated:

Set up your own SAML connection, require SSO and map SCIM groups to roles on Team & security.

Open Settings in Fiatto
In this article

Under Settings → Team & security (/dashboard/settings/team), section Security & SSO, admins set up SAML SSO and SCIM. Fiatto supports SAML 2.0 with your own identity provider (Microsoft Entra ID, Okta, Google Workspace, …); there is no OIDC.

Steps

  1. Enter the SSO domain (e.g. company.com). This works once at least one active team member has signed in themselves with a confirmed address on exactly that domain; an account created through SCIM does not count, and neither do subdomains. Then confirm that you manage the domain: click Show DNS record, add the TXT record with the name shown (_fiatto-verificatie.<domain>) and its value to the domain's DNS and click Check; confirm with an extra sign-in check if asked. The domain is only set after a successful check. A sandbox or demo environment cannot get an SSO domain.
  2. Create a SAML application in your IdP with the Entity ID (Identifier) and Reply URL (Assertion Consumer Service) shown under SAML connection, with the email address as NameID. Then enter your IdP's metadata URL (or paste the metadata XML) and click Create connection.
  3. Click Test connection, then sign in in a private window with an address on the domain; Fiatto redirects you to your IdP. If everything works you can Require SSO login — password sign-in is then blocked, including for admins; only Fiatto's platform administrator can switch it off in an emergency.
  4. To manage users automatically from your IdP, create a token under SCIM provisioning (Generate token; you see it once) and enter the SCIM endpoint and token in your IdP. Under Map groups to roles, link an IdP group to a Fiatto role (Map group).

Tips

  • A first SAML connection takes effect immediately. Replacing or removing an existing connection, or changing or clearing the SSO domain, only takes effect after 24 hours; all admins get an email and can stop it until then — see sign-in policy. If new metadata belongs to a different identity provider (different EntityID), it becomes an IdP switch: after 24 hours the SSO domain moves to the new IdP. Everyone who signs in with SSO keeps their account only if the new IdP sends the same email address as NameID; otherwise a new account is created without their current role. Once the switch has started, it can no longer be stopped. You can only clear the domain once the SSO requirement is off. A connection that Fiatto Support set up for you can only be changed by Support.
  • If a colleague already has an account with the same email address (with a password or via SCIM), Fiatto links their SSO sign-in to that account and sends them an email about it; they keep their role and data. If a colleague signs in via SSO without an existing account or invitation, a separate empty trial workspace is created — invite team members first or have them created via SCIM.
  • SCIM: someone in several mapped groups gets the highest role; someone who leaves all their groups becomes a requester again. Mapping a group to the Admin role requires approval from a second admin (unless there is only one), and the last admin never loses their rights via SCIM. Deactivating blocks sign-in; nothing is deleted.
  • Require SSO login only works with a working SSO route: a SAML connection on the SSO domain, or sign-in with Microsoft or Google switched on under Sign-in methods. While the requirement is on, Fiatto also refuses a change that removes the last working route.
  • If your IdP passes an email address at sign-in that is not on the domain of the SSO connection, Fiatto refuses the sign-in and the login page shows a fixed message.
  • Fiatto checks the DNS record every day, so leave it in place. If it is missing for 3 days, the admins get a warning email; at the earliest 14 days after the record was last seen, the verification lapses. After that no new users join via SSO or SCIM until you put the record back and click Check; if someone without an account then signs in via SSO, the sign-in page says the domain is not confirmed. A DNS outage does not count. The weekly security overview counts confirmed, lapsed and restored verifications.
  • SCIM only creates users, and only renames them, with an address on the SSO domain. Without an SSO domain Fiatto rejects new users; existing ones keep syncing. What SCIM creates, updates, deactivates or reactivates appears in the audit log and is sent to a connected SIEM.
  • SSO has no plan gating. Also set a sign-in policy (MFA/passkey) — see passkeys.
Was this article helpful?
View all articles in this topic

Find another answer

A task, feature or short question is enough.