User provisioning

Jenz supports SCIM 2.0 (RFC 7643, RFC 7644) for provisioning users from your identity provider. Once it is connected, your directory is the source of truth for who has a Jenz account.

What it keeps in sync

In your directory	In Jenz
A person is assigned to the Jenz app	Their Jenz account is created
First name, last name, job title	Updated on their profile
Department	Updated; a department that does not exist in Jenz yet is created
Mobile phone number	Updated, when it is a valid number not used by another Jenz account
E-mail address	Updated, when no other Jenz account uses it
A person is unassigned, disabled or deleted	Their account is deactivated: they can no longer sign in
A deactivated person is assigned again	The same account is reactivated

Deactivating does not erase anyone's posts or history in Jenz, and reactivating brings back the same account rather than creating a new one.

Choose your setup

• Microsoft Entra ID

  ---

  The most common setup. Uses Entra's built-in provisioning service, no code needed.

  Entra ID guide

• Another provider, or your own client

  ---

  Any SCIM 2.0 client that provisions users can connect. The reference lists exactly what Jenz supports.

  SCIM API reference

Good to know

• Users only. Jenz provisions users. Groups are not provisioned over SCIM; manage them in the Jenz admin panel.
• SCIM and single sign-on are independent. You can provision users with SCIM whether or not they sign in to Jenz with SSO.
• Matching existing users. When your provider creates a user whose e-mail address already belongs to a deactivated Jenz account, that account is reactivated and updated. When it belongs to an active account, Jenz answers 409 Conflict and leaves it alone, and your provider can match the two by e-mail instead.