Set access rights for queues

Set access rights for queues

By default, users have unrestricted access to issues in a queue.

If you restrict access to your queue, only the users specified in the following fields will have access to its issues by default: Author, Assignee, Followers, Access.

You can change access settings for individual users, groups, or roles:

  1. Open the queue page.

  2. To the left of the queue name, select  → Configure.

  3. Go to the Access → All issues tab.

  4. Configure permissions by category:

    • Users and robots — Individual settings for individual users. To add a user to this category, enter the login or the user's name in the search bar at the top of the table.

    • Groups — Settings for departments and teams. To add a new department, enter its name in the search bar at the top of the table.

      Tip. To add all of your company's employees at once, select the All employees group.
    • Roles — Settings for users who have specific roles in queue issues:

      • Access — Users listed in the Access field of an issue.

      • Follower — Users who subscribed to the issue.

      • Reporter — The person who created the issue.

      • Assignee — The person assigned to the issue.

      • Queue owner.

      • Queue team members are users added to the queue team. This role isn't on the list by default, but you can add it via the search bar at the top of the table.

  5. Click Save.

If a user has multiple roles, they gain all access rights associated with each role.

Example

If a user is both the reporter and the assignee, they are able to Create issues, View issues, and Edit issues.

Add a message for users who can't access issues

When a user is trying to open an issue from a queue they doesn't have access to, a message pops out that says “Contact the queue owner” with the owner's name.

This message can be changed, however. For instance, you can specify another user with queue admin rights who can give access to issues. You can also specify the reason for restricting access to the queue.

To edit the message displayed to users with no access to the queue, do the following:

  1. Open the queue page.

  2. To the left of the queue name, select  → Configure.

  3. Go to the Access → All issues tab.

  4. Go to the Message for users without queue access block and click Edit.
  5. Write your message and click Save.

    If you want to add a link to a user profile in your message, specify their username followed by the @ symbol, such as login@.

Set access rights to issues with components

You can configure access to various components of the queue. This lets you create separate setups for issues that have components and those that do not. The rules for component access take priority over the rules for queue access.

To configure access to issues by component:

  1. Open the queue page.

  2. To the left of the queue name, select  → Configure.

  3. Go to Access → Issues with component.

  4. Configure permissions by category:

    • Users and robots — Individual settings for individual users. To add a user to this category, enter the login or the user's name in the search bar at the top of the table.

    • Groups — Settings for departments and teams. To add a new department, enter its name in the search bar at the top of the table.

      Tip. To add all of your company's employees at once, select the All employees group.
    • Roles — Settings for users who have specific roles in queue issues:

      • Access — Users listed in the Access field of an issue.

      • Follower — Users who subscribed to the issue.

      • Reporter — The person who created the issue.

      • Assignee — The person assigned to the issue.

      • Queue owner.

      • Queue team members are users added to the queue team. This role isn't on the list by default, but you can add it via the search bar at the top of the table.

  5. Click Save.

If an issue has several associated components, all users with access to at least one of them will be able to access the issue.

Example

If an issue has the Hardware and Software components, it can be accessed by users from both the “Product development” and “Application development” groups.