[go: up one dir, main page]

Assign or Deactivate Users

Assign new users to the application to provision them to PagerDuty, or deactivate them to remove them from PagerDuty.

🚧

Deactivation Warning

PagerDuty does not support deactivating and reactivating the same user. If you deactivate a user in the IdP, this action will delete them in PagerDuty. If you reactivate the user, the behavior of the IdP’s SCIM client implementation determines how to reconcile the user. Okta, for example, creates a new user, while OneLogin throws a provisioning error message when the user fails to update.

Supported User Attributes

The PagerDuty SCIM API currently exposes the following user attributes:

AttributeTypeRead / WriteDescription
idStringReadUnique identifier for the user.
userNameStringRead + WriteEmail and username of the user. (Required)
displayNameStringRead + WriteName displayed in PagerDuty. (Required)
externalIdStringRead + WriteUsually the IdP’s ID for the user.
rolesArrayRead + WriteSingle element array containing the user’s role. The accepted role is an object: {“type”: “base”, “value”: “user”} where the value matches the list of roles supported by the public API.
activeBooleanRead + WriteWhen set to false, the user will be deleted.
titleStringRead + WriteJob title of the user.
entitlementsArrayRead + WriteSingle element array containing the user’s license. The accepted entitlement is an object: {“type”: “license”, “value”: “LICENSE_ID”} where LICENSE_ID is a license ID sourced from the public API licenses endpoint.
timezoneStringRead + WriteIANA formatted time zone for the user.