# Queue permissions · Queues And Permissions · Tickets · Admin Portal

Manage users' access to tickets in queues and subqueues through agent or company roles. Assign Read, Update and Create permissions for each queue.

Canonical: https://docs.mintsd.com/docs/mint-service-desk/admin-portal-queue-permissions
Language: en-GB
Revision: 2a2d39f1e31deba465d9905cd685a5a3416966a588eb6151bba19ba5bc3c7cc9

<a id="element-01a1452d-fca8-7218-94bc-0624c5208cec"></a>

Use Queue permissions to control access to tickets in each queue and subqueue.

<a id="element-01a1452d-fca8-7f96-94e7-9ae5cf303731"></a>

![Queue permissions: Use Queue permissions to control access to tickets in each queue and subqueue.](https://docs.mintsd.com/api/reader/assets/assets/images/image275.png?v=e7f8ee9d9e1f178c461811342cca5d06aacefe59b1a1dff86759c72ed68f7a3e)

<a id="element-01a1452d-fca9-7047-ab38-4ecad257fc09"></a>

If you want to change rights, first you need to select one position from
the list of available General types of roles. They can be e.g. ‘Agent
Roles’ (if you have more than one created in the Agent Roles section) or
‘Company Roles’ (located in Companies > Company users section,
separately for each company in ‘Role management’ > Company users tab.

<a id="element-01a1452d-fca9-78b9-b3ba-fcca476b2e0b"></a>

After you do that, from the second list you need to select a particular
type of Role for which you want to change the right.

<a id="element-01a1452d-fcaa-70bc-a1e7-8692a21dc7fb"></a>

The screen below shows the situation when we’ve decided to select ‘Agent
roles’ and then one particular role: ‘Service Desk Agent’, which means
that we will be able to change the rights for this particular role.

<a id="element-01a1452d-fcaa-7d59-bd26-fd1c32016940"></a>

![The screen below shows the situation when we’ve decided to select ‘Agent roles’ and then one particular role: ‘Service Desk Agent’, which means that we will be able to change the rights for this particular role.](https://docs.mintsd.com/api/reader/assets/assets/images/image276.png?v=523b107d0724aeaaa4af2445e162e58fc45515c4e6967d318fa6028f7d432860)

<a id="element-01a1452d-fcab-7f95-a199-bca6447e630f"></a>

Now we can change the rights by selecting some check-boxes located on
the right side of each queue.

<a id="element-01a1452d-fcab-7cb3-bfc7-a4d5a07258a0"></a>

![Now we can change the rights by selecting some check-boxes located on the right side of each queue.](https://docs.mintsd.com/api/reader/assets/assets/images/image277.png?v=4592be796b57eee0fbeaa02f770ffec08325b76a65e9a4a1d99d643bd6fd18cf)

<a id="element-01a1452d-fcab-7749-b2a5-d41096726e12"></a>

Available permissions:

<a id="element-01a1452d-fcad-7368-9be9-983beba06500"></a>

- **Read** – allows the user only to view the content of the Tickets on
  a queue
- **Update** – allows the user to make changes in the content of a
  Ticket on a queue. For example, Agent will be allowed to answer the
  client (to create a message in the communication section, change the ticket parameters).
- **Create** – allows the user to create tickets. The user can have Create but not Update and Read rights.

<a id="element-01a1452d-fcad-7677-bed9-f34228833e38"></a>

Selecting ‘Read’ does not select ‘Update’.

<a id="element-01a1452d-fcad-7d4a-a618-4a452073c7d9"></a>

Selecting ‘Update’ also selects ‘Read’, allowing the user to view and change ticket content.

<a id="element-01a1452d-fcae-74ad-bbb5-b73454857c8b"></a>

<a id="element-01a1452d-fcae-7127-a6b4-bddc131724f7"></a>

Once you finish making the changes, you need to click ![Save](https://docs.mintsd.com/api/reader/assets/assets/images/image8.png?v=c6dfcae62b1da5a56376cb98f40e0a593d8d731e458977d27180f6380454b49d#element-01a1452d-fcae-74ad-bbb5-b73454857c8b) button,
otherwise, when you try to leave this part of the system it will inform
you that you have some unsaved changes.

<a id="element-01a1452d-fcae-7544-a17f-0ca1d1466abd"></a>

In this section, you can configure the whole structure for Tickets. Step
by step you can create, edit or delete: ‘Ticket types’, ‘Groups’ (of
attributes), as well as single ‘Attributes’ along with their values. You
will also set custom Statuses for your Ticket Types and unique Ticket
number pattern.

