Groups help you manage project access for teams. Instead of assigning the same project role to each person one by one, you can add users to a group and assign that group to projects.
When a group has a project role, users in that group inherit that access.
A group can include:
Groups do not replace direct project roles. A user can have direct project access, inherited group access, or both.
Direct access is assigned to a user for a project.
Inherited access comes from group membership. If a group is assigned to a project, every eligible user in that group receives the group’s project role.
Removing a direct project role does not remove inherited access. To remove inherited access, update the group membership or the group’s project access.
Workspace users with the Viewer role cannot be added to groups.
If a user’s workspace role is changed to Viewer, Hawzu warns that their group memberships and project assignments will be removed before the update is applied.
Groups are managed from the workspace Groups page. You can also review and update one user’s group membership from the workspace Users page.
Project user views show inherited roles so you can see when access comes from a group.
QA Team or Release Managers