Appearance
Groups and permissions
A group is a role in your organization, such as "Sales managers" or "Office". Everyone has exactly one group here.
Create a group
Groups & RBAC → New group: Group name and Description. Then give it permissions and menus. Groups can't be deleted, so name them for the job, not the person.
Permissions
Select the group, then Next permissions: permissions grouped by area, each with its key and what it allows. Tick and Save permissions. Taking permissions away asks first: "Revoke N permission(s)? Members of … lose: …".
Permissions that make someone an admin:
| Permission | Lets them |
|---|---|
tenant.admin | manage your organization: users, groups, modules, access, documents, Tool Shed, audit trail |
users.read, users.write, users.delete | see, add and change, remove users |
groups.read, groups.write | see, change groups and their permissions |
menus.read, menus.write | see, change the organization's menus |
audit.read | read the audit trail |
documents.admin | document settings and types |
toolshed.admin | Tool Shed for your organization |
Modules add their own permissions when they're installed (named <module>.<action>).
Default group for new members
Above the group list, Default group for new members picks the group people get when they join without one: someone added without a group, and people who sign up through Google or your directory (when your organization allows that). Choose None to have no default; then every new user needs a group. Only your organization's own groups can be the default, never a built-in admin group. You need the organization admin permission (tenant.admin) to change it.
Menus
Menu access lists the apps in your organization; tick those this group should see and Save menu roles. It's easier for all groups at once in Modules & Access.
Changes apply when members refresh or sign in again.