Roles and access rights in Yandex Tracker
Yandex Tracker is one of the services that can be connected to the Yandex 360 organization. The organization administrator who connected Tracker also becomes the Tracker administrator.
Access rights to individual elements and features of the service can be configured for users and user groups in Tracker.
- Global Tracker Access Level
- Access Rights to Individual Tracker Structure Elements
- Group Visibility Settings
Global Tracker Access Level
A user's access level applies to the entire Tracker structure. This access level determines which actions the user can perform, such as creating and editing tasks and changing Tracker settings.
Tracker administrators and Yandex 360 for Business organizations can configure access for users or user groups. For more information, see the How to configure access to Yandex Tracker section.
Administrator
The administrator has access to all elements of the Tracker structure. By default, the Yandex 360 organization administrator has administrator permissions.
To assign other employees as administrators, grant them the "Tracker Administrator" role in the Yandex 360 organization admin console. For information on how to grant administrator roles, see the Yandex 360 for Business Help.
Actions available to the administrator:
- Managing Tracker users and access rights.
- Managing Tracker settings: creating new statuses, resolutions, and task types, configuring global fields for tasks, connecting repositories.
- Managing queue settings.
Full-Access User
Users can use all Yandex Tracker features:
- Creating and editing tasks.
- Searching for tasks using the filter designer and query language.
- Adding comments.
- Creating and configuring queues.
Including creating auto actions, triggers, and macros in the queue. - Working with task boards and dashboards.
- Configuring the interface and notifications.
User with Read
access
Read
access is the default setting for organization employees who do not have access to Tracker. If an administrator has TrackerRead access in
, they can still change the access settings for their own account.
In Read
mode, users cannot perform actions related to creating, updating, and deleting objects, e.g.:
-
Create issues using the Tracker interface.
-
Change parameters, statuses, and resolutions in issues.
-
Comment on issues.
-
Subscribe to changes in issues.
However, you can still perform all actions related to viewing Tracker issues:
-
View issues, dashboards, and issue boards.
-
Search for issues using the filter builder and query language.
-
View queue pages.
-
Customize the service interface and configure notifications.
Access rights to individual Tracker structure elements
-
Queue tasks. Permissions to create, view, and edit tasks can be configured by the queue owner or another user who has been granted permission by the owner to change queue settings.
Access to queue tasks can be configured for individual users, groups, and roles:
- Access — users listed in the Access field for the task;
- Observer — users subscribed to the task;
- Author — the task author;
- Executor — the task assignee;
- Queue Owner;
- Queue Team Member — users added to the queue team.
To restrict user access to specific tasks within the queue, you can use components.
For information on configuring queue access, see How to configure access rights in a queue.
-
Access rights to Tracker entities and elements can be configured by their owner or another user granted permissions by the owner. To configure access, see the following sections:
Access to Tracker API
Access to Yandex Tracker API requires authorization using the OAuth 2.0 protocol or an IAM token. How to get access to the API
When working with Yandex Tracker API, application requests are executed on behalf of the Tracker user. To perform certain actions through the API, the user executing the request must have the appropriate rights in the Tracker.
Group Visibility Settings
The Administrator can allow or restrict Tracker users' access to data belonging to members of a specific user group, such as login, email, and job title. For more information, see Configuring visibility for user groups.