Suite | Team, Growth, Professional, Enterprise, or Enterprise Plus |
Support | Team, Professional, or Enterprise |
Admins and agents in custom roles with permissions can create, edit, and manage any custom user fields. Custom user fields are visible to all agents, but only agents with access to all tickets can edit custom user fields for themselves (not other agents) and end users. End users cannot see or edit custom user fields.
Editing custom user fields
Everything about a custom field is editable except the field type and key, which can't be changed after the custom field is created.
To edit a custom user field
- In Admin Center, click
People in the sidebar, then select Configuration > User fields.
- Hover over the row of the field you want to edit, then click the option menu
icon (
) and select Edit.
- Edit settings as needed and click Save.
Deactivating and reactivating custom user fields
The User fields page has two tabs: Active and Inactive. New custom user fields are active by default. Activating an inactive custom user fields adds it to the user profile view.
- In Admin Center, click
People in the sidebar, then select Configuration > User fields.
- Find the custom user field on the Active tab, click the option menu
icon (
), and select Deactivate.
Deactivating a custom user field removes it from the user profile view, but the field can be reactivated at any time.
- Click Deactivate to confirm you want to deactivate the custom
field.
The custom user field moves to the Inactive tab.
To reactivate a custom user field
- In Admin Center, click
People in the sidebar, then select Configuration > User fields.
- Find the custom user field on the Inactive tab, click the option menu
icon (
), and select Activate.
The custom user field moves to the Active tab.
Deleting custom user fields
You can delete custom user fields on the edit page. Deleting a custom user field is permanent. The field and data stored in that field can't be recovered.
- In Admin Center, click
People in the sidebar, then select Configuration > User fields.
- Hover over the row of the field you want to edit, then click the option menu
icon (
) and select Edit.
- Click the option menu icon (
) at the top of the page, then select Delete.
When you delete a custom user field, that field and any associated data is removed from all users. The data is preserved only if the custom field also adds a tag to a user. The two custom fields that add tags are the drop-down list and the checkbox. If you delete one of these custom fields, then the data in users persist as tags.
- Click Delete to confirm that you want to delete the custom user field.
27 comments
Christopher Kennedy
Setting the user field value will require a separate API request to update the user once you've created the ticket.
Best,
0
Luciano Zambito
Hi everyone, I'm trying to SET (while creating a ticket for a new user) and to UPDATE some custom user fields (dropdown type) for a SPECIFIC user already created, via API.
User fields are already there: I just need to set their value.
I can't find out how to do that: may someone give me the right direction?
0
Paul Strauss
Can we make user fields required somehow?
1
Anil Zendesk TI
Can we create conditions on User fields? On Ticket fields we have an option.
1
Binh Du
Hi Dave,
We originally thought we could set it up for Assignees as an Out of Office trigger. The conditions would be if the User Field (set as a checkbox) was checked for the Assignee, then for any incoming tickets assigned to that Assignee (all of our tickets are automatically assigned to specific Agents), a specified backup Agent would be added as a follower and emailed so that they could be able to take care of the tickets until the Assignee is no longer out of office. At first testing I thought it worked, but I did the test myself as both the Requester and Assigner and only later found out that it did not work as I intended. Could this feature be added or modified to include Assignees as well, or is there a different way to achieve what we are wanting to do?
0
Dave Dyson
Unfortunately, only requester user fields are accessible via Triggers. Can you talk a little more about your use case? What are you trying to achieve?
0
Binh Du
Currently when creating a custom user field and adding it as a condition in a trigger, it only applies to the Requester. Is it possible that the user field condition can be applied to the Assignee instead, or just make it neutral and applies any time the user field is in use?
1
Sign in to leave a comment.