'Group permissions' allow all org members (present and future) to be invited to masters and projects.
'Group permissions' is available with 'Premium'.
Sending individual invitations and managing roles can be time-consuming. To streamline this, assigning a role to the 'All org users' or 'All org admins' group grants all members quick access to projects and masters. This makes the process easier for admins and new users, as they immediately gain access to everything they need.
Related article: Inviting someone to collaborate on a project
Members of the organization are automatically included in the 'All org members' group. Whether they are also part of the 'All org admins' group depends on their admin status. This is managed through 'User management' in the Org settings.
A screen capture of the 'User management' interface.
Adding group permissions:
The 'Invite users' page has been updated so that you can invite individual users and add groups to a project or master:
A screen capture of the 'Invite users and groups' functionality.
Permissions are set in the fields below those, but if they need to be edited, you can go to the team members tab, then the three-dot menu, and then to the manage roles.
A screen capture of the 'Manage project roles' functionality and how to assign a project role or define the role at a specification level.
Removing group permissions:
You can also remove individuals and groups from a project or master by going to the team members tab, then the three-dot menu.
Individual permissions vs group permissions:
If a group is assigned a role on a project or master, then all members of that group will receive that role. Their permissions will match the permission level defined for the group.
When multiple group roles apply, the platform merges them, prioritizing the highest permission level. If a user has both a group role on a project or master and an individual role, the individual role's permissions override the group role, including the 'Excluded' permission.
Let’s consider an example: you have a master folder and need to manage access permissions for all staff members and the person responsible for maintaining it.
| Org User | Individual role on the master folder | The 'Org user' group role on the master folder is set to 'Reader' | The final permission is: |
| Ash is accountable for the master folder. | Administrator | Reader | Administrator |
| James is responsible for maintaining the content | Contributor | Reader | Contributor |
| Morgan copies from the masters for use in their project specifications | Not set | Reader | Reader |
For a more in-depth look at the permissions between Org Admin group roles and Org User group roles, please refer to the table below:
| Org Admin Group Role | |||||||
| Org User Group Role | Excluded | Limited | Reader | Designer | Contributor | Admin | |
| Excluded | Excluded | Limited | Reader | Designer | Contributor | Admin | |
| Limited | Limited | Limited | Reader | Designer | Contributor | Admin | |
| Reader | Reader | Reader | Reader | Designer | Contributor | Admin | |
| Designer | Designer | Designer | Designer | Designer | Contributor | Admin | |
| Contributor | Contributor | Contributor | Contributor | Contributor | Contributor | Admin | |
| Admin | Admin | Admin | Admin | Admin | Admin | Admin | |