PingOne Advanced Identity Cloud

Manage provisioner properties

Configure properties on a provisioner when you need to work with attributes on the external system that aren’t already exposed by the connector schema. For example, you might add properties so that advanced sync mappings can read or write fields such as costCenter, managerId, or a custom entitlement flag on the remote system.

Provisioner properties define or extend the schema for a provisioner’s object types. These properties represent real attributes on the external system and are available as source and target fields in advanced sync mappings.

To avoid schema overlap and conflicts, only add or edit provisioner properties when you need to expose additional attributes that the connector does not already show. Any property you define here must match a real attribute on the target system (name, type, and usage), or synchronization might fail at runtime.

Before deleting or changing a property, update any advanced sync mappings that reference it to avoid sync errors.

To add, edit, or delete a provisioner property:

  1. In the Advanced Identity Cloud admin console, go to power Integrations > Provisioners.

  2. In the object type list in the upper-left corner, select the object type you want to configure properties for.

  3. Click the Properties tab.

  4. Do one of the following:

    • To add a property, click add Add a Property, complete the property details, and click Save.

    • To edit a property, click the property name, update the property details, and click Save.

    • To delete a property, click the Ellipsis icon (more_horiz) next to it, select Delete and confirm the deletion.

Property settings reference

Use the following settings on the Add or Edit a Property modal to define how the property connects to the external system and how it can be used in advanced sync mappings:

Field Description

Name

The name of the attribute on the external system. This must match the real attribute name on the external system for synchronization to work. For most provisioners it’s case sensitive, so make sure you enter the name exactly as it appears on the external system.

Type

The data type of the attribute on the external system. Must be one of String, Integer, Boolean, or Object. This must match the real attribute type on the external system for synchronization to work.

Multi-valued

Allow multiple values for the property.

Select this checkbox only if the corresponding attribute on the external system is defined as multivalued (for example, groups, roles, email addresses). The property is treated as an array in mappings.

Required

Mark the property as mandatory on the external system.

Select this checkbox if the target system requires a value when creating or updating an object. If a required property is missing, provisioning operations for that object fail.

Advanced settings:

Field Description

Creatable

Select if the property can be set when creating a new object in the connected system.

Clear this checkbox if the external system does not allow the field to be written on create.

Readable

Select if the property is returned from the connected system when objects are read.

Clear this checkbox if the external system never returns the field or if you don’t need it in reads.

Updatable

Select if the property can be changed on existing objects in the connected system.

Clear this checkbox if the field is read-only after creation.

Returned by default

Controls whether the property is included in standard read operations without being explicitly requested.

Clear this checkbox for large, sensitive, or rarely used fields that you only want when specifically asked for in queries.