User provisioning (SCIM)
Let your identity provider manage who is in your Vaizy workspace. When you add someone to the Vaizy app in Okta, Microsoft Entra ID, OneLogin or any other SCIM 2.0 identity provider, they get access. When you deactivate them there, they lose it and are signed out everywhere. Groups can set workspace roles.
SCIM provisioning is available on the Enterprise plan. Owners and admins set it up in Settings → Provisioning (SCIM). It works with or without single sign-on.
Before you start
SCIM can only provision people on your verified email domains. Verify at least one domain in Settings → Domains first.
1. Connect your identity provider
Copy the SCIM base URL.
Enter a token name (for example "Okta") and select Generate token. Copy the token: it is shown only once.
Paste both into the provisioning settings of your identity provider.
You can have 2 active tokens at a time, so you can switch to a new token without downtime: generate the new one, update your identity provider, then revoke the old one.
Okta
In your Okta app for Vaizy, open General and enable SCIM provisioning.
Under Provisioning, set the SCIM connector base URL to the SCIM base URL and the unique identifier field to
userName.Choose HTTP Header authentication and paste the SCIM token.
Enable Create Users, Update User Attributes and Deactivate Users under To App.
Assign people to the app, and use Push Groups for groups you want to map to roles.
Microsoft Entra ID
In your enterprise application for Vaizy, open Provisioning and set the mode to Automatic.
Paste the SCIM base URL as the Tenant URL and the SCIM token as the Secret Token, then test the connection.
Under Mappings, keep
userPrincipalNameormailmapped touserName, and mapmailtoemails[type eq "work"].value.Assign users and groups to the application and start provisioning.
OneLogin
Add the SCIM Provisioner with SCIM Bulk Operations (SCIM v2 Core) app, or enable provisioning on your Vaizy app.
Set the SCIM Base URL to the SCIM base URL and the SCIM Bearer Token to the SCIM token.
Set the
userNamein the SCIM JSON template to the email address, then enable provisioning.Use rules to push roles as groups if you want to map them to Vaizy roles.
What happens in Vaizy
Vaizy never deletes the person's account, and their history in the workspace is kept. The workspace owner is never changed through SCIM.
People created through SCIM sign in with single sign-on. Without single sign-on, they set a password with Forgot password on the login page.
Changing someone's email address isn't supported. Deactivate the old address and provision the new one.
Provisioning counts toward your seats. If you pay by invoice and all seats are taken, new people aren't provisioned until your account manager adds seats.
2. Map groups to roles
Groups appear in Settings → Provisioning (SCIM) after your identity provider pushes them. Choose a role for each group: Member, Manager or Admin, or leave it Not mapped.
A person gets the highest role of the mapped groups they are in.
People in no mapped group become Members.
Until you map at least one group, roles stay manual and SCIM never changes them.
People who have project access need at least the Manager role, so Vaizy keeps them at Manager instead of Member.
You can still change someone's role in Settings → Users. The next group change that affects them sets it back to the group's role.
3. Map attributes
Select Map attributes to fill Vaizy fields from your identity provider:
Department/Team
Job title
Country: an ISO code or English country name. Public holidays follow the country.
Custom attribute: any other attribute, such as cost center, shown read-only on the team member under "From your identity provider".
Attributes your identity provider already sent are listed under Sent by your identity provider. Mapped fields are locked in Vaizy and update on every sync. A newly mapped attribute fills in the next time your identity provider syncs each person.
Custom attributes are visible to everyone who can see the member in Vaizy. Only map what your team may see.
Recent activity
Recent activity shows what your identity provider changed in the last 90 days, and any failures. Common failures:
"The email address is not on a verified domain of this workspace": in Entra ID this is often a
@yourtenant.onmicrosoft.comaddress. MapmailtouserNameand emails instead."The workspace has no free seats left": ask your account manager to add seats, then let your identity provider retry.
"Changing a user's email address isn't supported": deactivate the old address and provision the new one.
"A user or group with this name is already provisioned": your identity provider lost track of the person. It usually finds them again on the next retry.
Revoke a token
Select the trash icon next to the token. Your identity provider stops provisioning with it right away. People already provisioned keep their access.
Was this helpful?
More in Settings & Preferences
NotificationsSecurity and privacyLanguages and currencyVerified domainsStill need help? Ask the team