SCIM provisioning
Your directory keeps Varqeni in step: assign people and groups to the Varqeni app there, and they appear here.
AvailabilityFor the person who runs Varqeni for your team. In early access that is usually Fortis, working with you.
Steps
- Make a token: Users and access, Service accounts, Add service account, with the scope scim:write. Copy the token.
- Set up provisioning: in Entra ID (Enterprise applications, your app, Provisioning) or Okta (your app, Provisioning), use the tenant URL shown on the SCIM card in Authentication, and the token as the secret token.
- Assign people and groups: people start as viewers. Give roles in Users and access, or to the teams their groups become.
- Turning someone off in the directory disables them in Varqeni: they can read, and act on nothing.
What you should see: People in the on-call file are matched but never changed by the directory. Every change is in Settings history and the Audit log.
What it can and cannot do
Can
- Let Entra ID or Okta add, change, disable and remove the people and teams in Varqeni.
Cannot
- Give roles from the directory. People start as viewers; roles are given in Users and access or through teams.
Related articles
- Single sign-onLet people sign in to Varqeni with Microsoft Entra ID, Okta, Google, GitLab or any OpenID Connect provider.
- Users and accessAdd people, give them a role everywhere or on chosen systems, group them in teams, and make service accounts for other tools.
Still stuck? Contact support or email info@fortisdatagroup.com.