Groups

Introduction

A group is a named set of users. Its purpose : grant a permission to a whole group at once, rather than to each person. When the team changes, you simply add or remove a group member and their access follows.

A typical example : an Artistes group with write permission on Content/, and a Programmeurs group on Source/.

Access and roles

• Super admin : full management (create, rename, delete, add / remove members).
• project_admin : can view the list of groups and their member counts, which is enough to target a group in the Permissions tab. They cannot create or modify a group, nor manage its members.

Why this restriction : because a group is global, modifying it would silently move access across every project that uses it, including those a project_admin does not administer. Group management therefore stays with the super admin.

Create a group

1. Groups tab → + button (Create).
2. Name (required, 1 to 100 characters) and Description (optional).
3. Confirm. A name already taken is rejected.

Manage members

Select a group in the left-hand list : its members appear on the right.

• Add : choose a user from the drop-down menu (it lists only active accounts that are not yet members), then Add.
• Remove : the removal button on the member's row.

Adding a member who is already present does nothing (the operation is idempotent). The account must exist and be active.

Delete a group

Common pitfalls

Editing a shared group changes access everywhere

Because a group is global, adding a folder to its permission in one project may look local but is still carried by the same group if it is reused elsewhere. For genuinely different needs between two projects, prefer two separate groups.

Does a removed member keep access ?

No : as soon as they leave the group, they lose the permissions the group carried. If they still have access, it means they hold a direct permission (granted to their account, not to the group) : check the Permissions tab and its test result.