---
metadata:
- name: generator
content: Diplodoc Platform v5.47.3
alternate:
- https://yandex.com.tr/support/tracker/en/manager/queue-access.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt
# How to configure access rights in a queue
{% note info "" %}
A queue can be set up by its [owner](https://yandex.com.tr/support/tracker/en/manager/queue-team.md) and Yandex Tracker administrators, as well as by users with the [**Queue settings** permission](https://yandex.com.tr/support/tracker/en/manager/queue-access.md#permissions).
{% endnote %}
Access to queue issues is granted to:
* Users and groups added to the [**Main participants** section](#main). If the user isn't on the list of the queue's main participants, they're added to the **Access** field when summoned in an issue comment. After the first comment, the user is automatically added to the **Followers** list.
* Users specified in the **Author**, **Assignee**, **Followers**, and **Access** issue fields.
* Users whose access can't be restricted:
* [Organization administrators](https://yandex.com.tr/support/tracker/en/role-model.md#admin).
* Tracker robot.
* [Queue owner](https://yandex.com.tr/support/tracker/en/manager/queue-team.md).
## Managing access in queues {#manage-access}
To give queue access to Yandex Tracker users:
1.
In the left-hand panel, click **Queues** and select a queue. {#queue}
1.
In the top right corner of the queue page, click **Queue settings**. {#settings}
1. Click the **Access bindings** tab.
* To view all access permissions for a user or group, use the search at the top of the screen or click the user or group.
* To restrict access for queue participants, select a user or group from the list and click **Revoke access**.
1. Assign access [levels](#permissions) and [types](#scheme) to the queue users. You can combine different access types.
{% note info "" %}
The queue access settings will be applied within an hour.
{% endnote %}
Configure queue permissions carefully to avoid unintentionally revoking your own permissions. This may happen if you delete the settings that allow you to [manage the queue](#permissions). To avoid this, contact [admins](https://yandex.com.tr/support/tracker/en/manager/queue-team.md#implicit-access).
## Levels of access {#permissions}
You can set up user permissions to perform certain actions in the queue:
* `Queue settings`: View and edit queue settings. This level doesn't include access to issues within the queue.
* `Edit issues`: View all issues in the queue, leave comments, and edit the issue description and any issue fields.
* `Create issues`: Create issues in the queue. When creating a new issue, the user is assigned the author role with permissions to view and edit the issue.
* `Create issues with components`: Create issues with [components](https://yandex.com.tr/support/tracker/en/manager/components.md) in the queue. Only available when editing a component.
* `View issues`: View queue issues, change issue statuses, and add or delete comments.
## Access types {#scheme}
The **Access rights** tab contains sections where you can differentiate user permissions by access type:
* [**Main participants**](#main): Use this section to grant access rights to issues in the queue for specific users, user groups, or robots.
* [**Roles in issues**](#task-role): This section adds to the access settings you've set up under **Main participants**. Use it to edit user permissions based on their role in a specific issue: author, assignee, follower, or individual added to the **Access** field.
* [**Issues with component**](#access-component): Use this section to set special rules for user access to issues with a particular component.
* [**Access disabled**](#prohibit): Use this section to deny access to queue issues to a user or group of users. This access type takes priority over any other access settings for the user or group.
User permissions combine all the rights applied, both personal and group ones. If different access rights are assigned to the user or their group in the access type sections, the user gets the most access allowed.
### Main participants {#main}
Under **Main participants**, you can select users who will have specific permissions for the queue.
> You can assign the following [access levels](#permissions) to the queue's main participants: `Queue settings`, `Edit issues`, `Create issues`, and `View issues`.
To add the queue's main participants:
1. Under **Main participants**, click **Add** and search for a user or user group.
1. Select the permissions you want to grant to a user or user group. If a user already has group rights, you will see which groups they belong to in the same window.
1. Click **Add**.
### Roles in issues {#task-role}
Under **Roles in issues**, you can modify the rights of issue participants. These permissions are granted in addition to the permissions configured under **Main participants**.
> You can assign the following [access levels](#permissions) to issue participants: `Edit issues` and `View issues`.
To modify the access level for an issue role:
1. Under **Roles in issues**, select the role from the list to adjust its access.
1. Click **Change access**.
1. In the access editing window, you can select the required permissions from the list or revoke extended access for this role. In this case, only the rights from the **Main participants** section will apply for an issue participant with this role.
1. Click **Save**.
### Issues with components {#access-component}
You can set up access to different [components](https://yandex.com.tr/support/tracker/en/manager/components.md) of the queue. This way, you can set different settings for the queue issues without components or issues with components.
> You can set the following [access levels](#permissions) for participants of issues with components: `Edit issues`, `Create issues with the component`, `View issues`. Components do not allow reconfiguring the rights to edit queue settings.
To add a component to an existing issue, component access of the `Create issues with the component` level is required.
{% note warning "" %}
Access rules for a component take priority over queue-level access rules, but don't override those set in [Access disabled](#prohibit).
{% endnote %}
If permissions are not configured in the component, the **Access** field for that component displays `Does not affect access`.
If multiple components are added to an issue, their permissions get combined. In this case, all the users who have access to at least one of the components will be granted access to the issue.
To configure access to a component:
1. Under **Issues with component**, select a component.
If there are no components yet, click **Create** and [fill out the component creation form](https://yandex.com.tr/support/tracker/en/manager/components.md#create-component).
1. Set up the access permissions on the component page:
* **Add participants**: Click this if no one has access to the component yet.
* **Main participants**: [Create a list of users](#main) who will be granted the selected permissions for the queue issues with the component.
* **Roles in issues**: [Set up permissions for issue participants](#task-role).
{% note info "" %}
We recommend that you review and set up permissions for user roles so that issues can be accessed by their assignees and other participants. For example, if the assignee doesn't have the `View issues` permission and isn't listed among the main participants, they won't be able to see the issue.
{% endnote %}
### Access denied {#prohibit}
You can't set deny access for the queue owner or any groups they're in. If you have the [Queue settings permission](#permissions), you can't deny access for yourself or the groups you're in.
{% note warning "" %}
Denied access has priority over other access types.
Let's say a user is denied access to the queue, and [roles in issues](#task-role) allow followers to edit the issue. Even if we make this user a follower, they won't be able to view and edit the issue.
{% endnote %}
To deny any access to queue issues:
1. Under **Access denied**, click **Add** and search for a user or user group.
1. Click **Deny access**.
#### Learn more {#see-also}
* [Queue owner and team](https://yandex.com.tr/support/tracker/en/manager/queue-team.md)
* [Bulk settings for queue access](https://yandex.com.tr/support/tracker/en/manager/queue-access-bulk.md)
* [Permission setup examples](https://yandex.com.tr/support/tracker/en/manager/queue-access-examples.md)