Roles define what users can see and do in Hawzu. They are used for workspace membership, project access, and group-based access.
Hawzu uses two role scopes:
Workspace roles manage broad access such as user visibility, groups, project membership, workspace settings, and workspace resources.
Project roles manage product work such as requirements, test cases, executions, releases, defects, labels, project roles, and project configuration.
Roles are also grouped by category:
System roles are read-only reference roles. They can be assigned, but they are not edited or deleted from the role details view.
Custom roles can be created, edited, and deleted when your role allows it.
Users can receive project access in two ways:
Hawzu uses additive access. If a user has both direct and inherited roles, the user keeps access from each source until that source is removed.
Use the role guides based on what you need: