Provisioning Policy
IdentityNow provisions new accounts based on the way attributes are mapped on the Create Profile page. The information on this page serves as instructions or a template for what information to include in the account, and is often referred to as the provisioning policy.
Important
If the default attribute mapping configuration doesn't meet your specific requirements, you can edit it. SailPoint recommends that you work with Services if you need assistance, to ensure accounts are provisioned as expected.
The following table shows how account attributes are used to create a profile for new Zendesk accounts:
Account Attribute | Type | Generator | Description |
---|---|---|---|
name |
String |
Identity Attribute - SailPoint User Name | The name of the user as taken from the SailPoint User Name |
String |
Identity Attribute - Work Email | The email address of the user as taken from the Work Email | |
verified |
Boolean |
Disable |
To confirm the email address without ownership confirmation from the user, this can be set to
|
details |
String |
Disable |
This is an attribute for details that you want to record about the user. For example, you can add an address. |
notes |
String |
Disable |
This is an attribute for the notes you want to record |
role |
String |
Disable |
The role of the user. Possible values are: end-user, agent, and admin. Default is end-user. |
custom_role_id |
Integer |
Disable |
The ID of the custom agent role. While creating a user with an agent role (without the custom_role_id value), the user gets created as a Legacy Agent. A new role in the admin center of Zendesk support must be assigned to this Legacy Agent. The Legacy Agent is a transitory role that includes all the agents that need roles to be assigned. This role will be null and ineffective after all its members have been assigned other roles. |