Skip to content
API reference Go to app

Create Custom Roles

2 min read

Create a custom role when system roles do not match your team’s exact access needs.

Custom roles can be created for the workspace or for a project.


Workspace roles control workspace-level access.

To create a workspace custom role:

  1. Open the workspace Roles page
  2. Click Create Workspace Role
  3. Enter a Role Name
  4. Add an optional Role Description
  5. Select permissions
  6. Click Create Role

The role name is required and must not duplicate an existing role name.


Workspace custom roles use these permission groups:

  • Visibility Permissions: browse projects, view users, view roles, view custom fields, view parameters, view integrations, view access tokens, view workspace settings, and view audit logs when available
  • Project Coordination Permissions: view project membership, add users to projects, remove users from projects, and assign project roles
  • Group Management Permissions: view groups, create groups, edit groups, and delete groups

Each permission can be selected individually. Use Select All or Deselect All within a category when you want to change the full category at once.


Project roles control access inside a project.

To create a project custom role:

  1. Open the project Roles page
  2. Click Create Project Role
  3. Enter a Role Name
  4. Add an optional Role Description
  5. Select project permissions
  6. Click Create Role

The role name is required and must not duplicate an existing role name.


Project custom roles include permission categories for:

  • Requirements
  • Test cases
  • Test suites
  • Shared steps
  • Parameters
  • Executions
  • Releases
  • Defects
  • Custom fields
  • Labels
  • Roles

Most categories include View, Create, and Update permissions. Labels also include Delete. Executions include permissions for creating and updating executions and executing tests.

When a project custom role is created, Hawzu includes the required project browse access so the role can open the project.


  • Start with the smallest permission set that supports the user’s work
  • Create roles around responsibilities, not individual people
  • Use groups to assign the same custom role to several users
  • Review custom roles regularly to avoid overlapping access