Permission setup examples

For HR teams

Configure the queue so that all employees can create new issues, but only the author and assignee can see them. For example, an employee reaches out to the department with a private request that only HR specialists should see.

Solution: Under Main participants, configure access for all organization users to only create issues, and for the HR team, to edit issues. Under Roles in issues, grant view and edit permissions to the author and assignee.

For information security

Configure access restrictions for issues using the component. For example, you need to restrict access for all users with different roles in the issue, except for the Information security group.

Solution: Create a component in the queue, e.g., private. For the private component, under Main participants, grant permissions to create and edit issues to the Information security group. Leave the Roles in issues section as it is, with the Doesn't affect access labels.