A named set of people you grant things to once, instead of inviting the same five names to every room.
Open GroupsA group is a named set of people you grant things to once, instead of inviting the same five names to every data room. It lives at /groups.
A group is a sharing primitive, not a data surface: it holds no data of its own — it holds people, and other objects point at it.
New group asks for a name in English and Arabic, and nothing else. It belongs to you, or to an organization you manage.
You are the owner, and ownership is not a member row: you will not see yourself in the members table, and you cannot leave your own group. Deleting it is the exit.
Invite by email address or username. A username is resolved on the server, so nobody's email address is ever handed back to your browser.
What happens next depends on whether that address already has an account:
Until then the table shows them as Invited rather than Joined. The row is what grants access, so an invitation whose email failed to send still works the moment they sign in.
Re-inviting an address already in the table is how you change its role. Groups have a member cap — see Plans & limits.
| Role | Can |
|---|---|
member |
See the group and what it reaches |
manager |
Invite and remove members |
owner |
Everything, plus role changes, rename and deletion |
Only the owner may make a manager. A manager who could appoint managers could escalate the whole group, so a manager can neither create a manager row nor modify one, and every role change is owner-only.
Inviting the owner is refused: a member row would shadow their ownership with a lower role.
The grant is created on the resource, not on the group. There is no "add a data room" button inside a group — this is the part people look for in the wrong place.
Open the data room, the dashboard or the project, share it with the group, and choose the role that grant carries:
| Resource | Roles a group may hold |
|---|---|
| Data room | viewer (open and download clean items) · collaborator (also curate the bundle) |
| Dashboard | viewer (open and query) · editor (also save pages and widgets) |
| Project | viewer (read the index) · collaborator (also add and remove items) |
Neither grant role can change sharing, manage grants, archive or delete — that stays with the resource's manager. Someone in two groups that both reach a room gets the better role.
The group's page then lists what it Reaches — the rooms and dashboards its members can open — and the groups list shows the same as a count. It is read from the resources' grants, so it answers "what does this group open".
Leave group removes your own row and nothing else; the owner has no row to remove.
An owner or manager can remove any member — except that removing a manager, like making one, is the owner's call.
Deleting the group removes it and prunes the grants that pointed at it, so no room carries a grant to a group that no longer exists. The rooms, dashboards and projects themselves are untouched.