Skip to main content
About the Resource Center

Restricted fields value list

This article lists the supported restricted fields value list. These fields are configured in the Access Policy JSON as a preset attributes list to restrict a user from updating certain User Profile fields or sections. For a detailed information, see Attribute based access control.

Restriction based on User Profile fields

To restrict a specific User Profile field from being updated, use the field values from the following table. 

    Showentries
    FieldDescription

    images

    User profile image.

    agent.name

    Agent name.

    agent.profileImage

    Agent image that can be found next to the Informal Photos tab.

    general

    User general fields include Name, Title, and Department.

    general.name

    User name found below the profile picture.

    general.title

    User title found in the first column under user name.

    general.department

    User department found in the second column under the user name.

    hr

    HR section

    hr.officialName

    HR section: Official Name field.

    hr.empId

    HR section: Employee ID field

    Restriction based on User Profile section names

    To restrict a group of fields from a User Profile section, you can list the User Profile section names in the preset attributes list. Use the following section names as restricted.fields.value preset attributes list:

    • Images
    • name
    • profileImage
    • name
    • title
    • department
    • hr
    • relationships
    • email_main
    • email_work
    • phone_work
    • primaryContactInfo
    • location

    Example restrictions

    • The inclusion of contactInfo.phone_work in the policy template enables you to prevent users from updating their work phone number. If you want to also prevent users from updating work phone 2, you must explicitly add contactInfo.phone_work_2 to the policy. 
    • Alternatively, if you want to prevent users from updating any of the fields in the Contact Information section, you can add contactInfo as a preset attribute to the policy and remove the other contactInfo fields. Using contactInfo as a preset attribute is similar to contactInfo.*, covering all of the contact-specific fields.