How to Assign Roles - Users & Groups Guide

Roles can be assigned to:

  • Users: Individual users can be assigned roles directly
  • Groups: Groups can be assigned roles, and all members inherit those permissions

Assigning Roles to Users

To assign a role to a user:

  1. Navigate to the Users page.

  2. Click on a user to open their details.

  3. Click “Edit” to enter edit mode.

  4. Change the user’s workspace role or project roles as needed.

  5. Click “Save” to apply the changes.

Assigning Roles to Groups

To assign a role to a group:

  1. Navigate to the Users page.

  2. Click on a group to open its details.

  3. Click “Edit” to enter edit mode.

  4. Assign projects and roles to the group.

  5. Click “Save” to apply the changes.

Best Practices

When managing roles:

  1. Principle of Least Privilege: Grant only the minimum permissions necessary for users to perform their tasks
  2. Use Groups: Assign roles to groups rather than individual users for easier management
  3. Clear Naming: Use descriptive role names that indicate their purpose (e.g., “QA Lead”, “Project Viewer”)
  4. Document Roles: Add descriptions to roles explaining their purpose and when to use them
  5. Regular Audits: Periodically review role permissions and assignments
  6. Test Roles: Create test users with new roles to verify permissions before assigning to team members
  7. Project-Specific Roles: Use project roles for project-specific permissions rather than workspace roles

Use Cases

Creating a QA Lead Role:

  • Create a workspace role with permissions to manage test cases, test runs, and defects
  • Assign it to QA team leads
  • Allows them to oversee testing activities without full administrative access

Creating a Viewer Role:

  • Create a workspace role with only View permissions
  • Assign it to stakeholders who need to see progress but not make changes
  • Provides read-only access to all workspace resources

Creating a Project-Specific Tester Role:

  • Create a project role with permissions to create and update test cases and test runs
  • Assign it to specific projects only
  • Allows testers to work on assigned projects without access to others

Restricting Project Access:

  • Create project roles with “Selected Projects” scope
  • Assign different roles to different projects
  • Ensures users only have access to projects they’re working on

Next Steps

Was this page helpful?