Zendesk Support accounts on the Enterprise plan or above can provide more granular access to their agents by defining custom agent roles. For more information, see Creating custom roles and assigning agents in the Support Help Center.
JSON format
Custom Agent Roles are represented as JSON objects with the following properties:
Name
Type
Read-only
Mandatory
Description
configuration
object
false
false
Configuration settings for the role. See Configuration
created_at
string
true
false
The time the record was created
description
string
false
false
A description of the role
id
integer
true
false
Automatically assigned on creation
name
string
false
true
Name of the custom role
role_type
integer
true
true
The user's role. 0 stands for a custom agent, 1 for a light agent, 2 for a chat agent, 3 for a contributor, 4 for an admin and 5 for a billing admin. See Understanding standard agent roles in Zendesk Support in Zendesk help
team_member_count
integer
true
false
The number of team members assigned to this role
updated_at
string
true
false
The time the record was last updated
Configuration
The configuration object has the following properties, which are all optional.
Name
Type
Read-only
Comment
assign_tickets_to_any_brand
boolean
no
Whether or not the agent can assign tickets to any brand and list all brands associated with an account sorted by name
assign_tickets_to_any_group
boolean
no
Whether or not the agent can assign tickets to any group
chat_access
boolean
yes
Whether or not the agent has access to Chat
custom_objects
object
no
A list of custom object keys mapped to JSON objects that define the agent's permissions (scopes) for each object. Allowed values: "read", "update", "delete", "create". The "read" permission is required if any other scopes are specified. Example: { "shipment": { "scopes": ["read", "update"] } }
end_user_list_access
string
no
Whether or not the agent can view lists of user profiles. Allowed values: "full", "none"
end_user_profile_access
string
no
What the agent can do with end-user profiles. Allowed values: "edit", "edit-within-org", "full", "readonly"
The kind of access the agent has to Guide. Allowed values: "edit-topics", "full", "readonly"
forum_access_restricted_content
boolean
no
group_access
boolean
yes
Whether or not the agent can add or modify groups
light_agent
boolean
yes
macro_access
string
no
What the agent can do with macros. Allowed values: "full", "manage-group", "manage-personal", "readonly"
manage_automations
boolean
no
Whether or not the agent can create and manage automations
manage_business_rules
boolean
no
Whether or not the agent can create and manage schedules and view rules analysis
manage_contextual_workspaces
boolean
no
Whether or not the agent can view, add, and edit contextual workspaces
manage_dynamic_content
boolean
no
Whether or not the agent can access dynamic content
manage_extensions_and_channels
boolean
no
Whether or not the agent can manage channels and extensions
manage_facebook
boolean
no
Whether or not the agent can manage facebook pages
manage_group_memberships
boolean
no
Whether or not the agent can create and manage group memberships
manage_groups
boolean
no
Whether or not the agent can create and modify groups
manage_organization_fields
boolean
no
Whether or not the agent can create and manage organization fields
manage_organizations
boolean
no
Whether or not the agent can create and modify organizations
manage_roles
string
no
Whether or not the agent can create and manage custom roles with the exception of the role they're currently assigned. Doesn't allow agents to update role assignments for other agents. Allowed values: "all-except-self", "none"
manage_skills
boolean
no
Whether or not the agent can create and manage skills
manage_slas
boolean
no
Whether or not the agent can create and manage SLAs
manage_suspended_tickets
boolean
no
Whether or not the agent can manage suspended tickets
manage_team_members
string
no
Whether or not the agent can manage team members. Allows agents to update role assignments for other agents. Allowed values: "all-with-self-restriction", "readonly", "none"
manage_ticket_fields
boolean
no
Whether or not the agent can create and manage ticket fields
manage_ticket_forms
boolean
no
Whether or not the agent can create and manage ticket forms
manage_triggers
boolean
no
Whether or not the agent can create and manage triggers
manage_user_fields
boolean
no
Whether or not the agent can create and manage user fields
moderate_forums
boolean
yes
organization_editing
boolean
no
Whether or not the agent can add or modify organizations
organization_notes_editing
boolean
yes
Whether or not the agent can add or modify organization notes
report_access
string
no
What the agent can do with reports. Allowed values: "full", "none", "readonly"
side_conversation_create
boolean
no
Whether or not the agent can contribute to side conversations
ticket_access
string
no
What kind of tickets the agent can access. Allowed values: "all", "assigned-only", "within-groups", "within-groups-and-public-groups", "within-organization". Agents must have "all" access to create or edit end users from the Agent Workspace. However, the ability to create or edit end users through the API is determined by the user's role, not by ticket_access.
ticket_comment_access
string
no
What type of comments the agent can make. Allowed values: "public", "none"
ticket_deletion
boolean
no
Whether or not the agent can delete tickets
ticket_editing
boolean
no
Whether or not the agent can edit ticket properties
ticket_merge
boolean
no
Whether or not the agent can merge tickets
ticket_redaction
boolean
no
Whether or not the agent can redact content from tickets. Only applicable to tickets permitted by ticket_access
ticket_tag_editing
boolean
no
Whether or not the agent can edit ticket tags
twitter_search_access
boolean
no
user_view_access
string
no
What the agent can do with customer lists. Allowed values: "full", "manage-group", "manage-personal", "none", "readonly"
view_access
string
no
What the agent can do with views. Allowed values: "full", "manage-group", "manage-personal", "playonly", "readonly"
view_deleted_tickets
boolean
no
Whether or not the agent can view deleted tickets
voice_access
boolean
no
Whether or not the agent can answer and place calls to end users
voice_dashboard_access
boolean
no
Whether or not the agent can view details about calls on the Talk dashboard
Example
{"id":35436,"name":"Partner","description":"Can only make private comments on assigned tickets","created_at":"2012-02-20T22:55:29Z","updated_at":"2012-02-20T22:55:29Z","configuration":{"assign_tickets_to_any_brand":false,"assign_tickets_to_any_group":false,"chat_access":true,"custom_objects":{"shipment":{"scopes":["read","update","delete","create"]},"product":{"scopes":["read"]}},"end_user_profile_access":"readonly","explore_access":"edit","forum_access":"readonly","forum_access_restricted_content":false,"light_agent":false,"macro_access":"full","manage_automations":true,"manage_business_rules":true,"manage_contextual_workspaces":false,"manage_dynamic_content":false,"manage_extensions_and_channels":true,"manage_facebook":false,"manage_group_memberships":false,"manage_groups":false,"manage_organization_fields":false,"manage_organizations":false,"manage_roles":"none","manage_skills":false,"manage_slas":false,"manage_suspended_tickets":false,"manage_team_members":"none","manage_ticket_fields":false,"manage_ticket_forms":false,"manage_triggers":true,"manage_user_fields":false,"organization_editing":false,"organization_notes_editing":false,"report_access":"none","side_conversation_create":true,"ticket_access":"within-groups","ticket_comment_access":"none","ticket_deletion":false,"ticket_redaction":true,"view_deleted_tickets":false,"ticket_editing":true,"ticket_merge":false,"ticket_tag_editing":true,"twitter_search_access":true,"view_access":"full","voice_access":true,"voice_dashboard_access":false}}
// Status 200 OK{"custom_roles":[{"configuration":{"assign_tickets_to_any_group":false,"chat_access":true,"end_user_list_access":"full","end_user_profile_access":"readonly","explore_access":"edit","forum_access":"readonly","forum_access_restricted_content":false,"group_access":true,"light_agent":false,"macro_access":"full","manage_business_rules":true,"manage_contextual_workspaces":false,"manage_dynamic_content":false,"manage_extensions_and_channels":true,"manage_facebook":false,"manage_organization_fields":false,"manage_ticket_fields":false,"manage_ticket_forms":false,"manage_user_fields":false,"moderate_forums":false,"organization_editing":false,"organization_notes_editing":false,"report_access":"none","side_conversation_create":true,"ticket_access":"within-groups","ticket_comment_access":"none","ticket_deletion":false,"ticket_editing":true,"ticket_merge":false,"ticket_tag_editing":true,"twitter_search_access":true,"user_view_access":"readonly","view_access":"full","view_deleted_tickets":false,"voice_access":true,"voice_dashboard_access":false},"created_at":"2012-03-12T16:32:22Z","description":"Advisors manage the workflow and configure the help desk. They create or manage automations, macros, triggers, views, and SLA targets. They also set up channels and extensions. Advisors don't solve tickets, they can only make private comments.","id":16,"name":"Advisor","role_type":0,"team_member_count":10,"updated_at":"2012-03-12T16:32:22Z"},{"configuration":{"assign_tickets_to_any_group":false,"chat_access":true,"end_user_list_access":"full","end_user_profile_access":"readonly","explore_access":"edit","forum_access":"readonly","forum_access_restricted_content":false,"group_access":true,"light_agent":false,"macro_access":"full","manage_business_rules":true,"manage_contextual_workspaces":false,"manage_dynamic_content":false,"manage_extensions_and_channels":true,"manage_facebook":false,"manage_organization_fields":false,"manage_ticket_fields":false,"manage_ticket_forms":false,"manage_user_fields":false,"moderate_forums":false,"organization_editing":false,"organization_notes_editing":false,"report_access":"none","side_conversation_create":true,"ticket_access":"within-groups","ticket_comment_access":"none","ticket_deletion":false,"ticket_editing":true,"ticket_merge":false,"ticket_tag_editing":true,"twitter_search_access":true,"user_view_access":"readonly","view_access":"full","view_deleted_tickets":false,"voice_access":true,"voice_dashboard_access":false},"created_at":"2011-07-20T04:31:29Z","description":"A Staff agent's primary role is to solve tickets. They can edit tickets within their groups, view reports, and add or edit personal views and macros.","id":6,"name":"Staff","role_type":0,"team_member_count":10,"updated_at":"2012-02-02T10:32:59Z"}]}