Roles Overview

Roles define what users can see and do in Hawzu. They are used for workspace membership, project access, and group-based access.

---

Workspace and Project Roles

Hawzu uses two role scopes:

• Workspace roles control access across the workspace
• Project roles control access inside a project

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.

---

System and Custom Roles

Roles are also grouped by category:

• System roles are built-in roles provided by Hawzu
• Custom roles are roles your team creates for specific needs

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.

---

Direct and Inherited Access

Users can receive project access in two ways:

• Direct assignment: a role assigned directly to the user for a project
• Group inheritance: a role inherited from a group assigned to a project

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.

---

Role Pages

Use the role guides based on what you need:

• System Roles
• Create Custom Roles
• Managing Custom Roles
• Deleting Custom Roles

---

Best Practices

• Start with system roles when they match the responsibility
• Create custom roles only when built-in roles are too broad or too narrow
• Use groups for team-based access
• Use direct project roles for exceptions
• Review custom roles regularly as responsibilities change

---

Next Steps

• Review System Roles
• Create roles with Create Custom Roles
• Learn about Groups