# Groups Groups let you organize users within your organization — for example by team, department, or office location. Instead of adding users to projects one by one, you can assign an entire group to a project and all group members automatically get access. Groups are created and managed in [Organization Settings > Groups](https://app.cogram.com/dashboard/settings/admin/groups). ## What Groups Are For * **Project access**: Assign an entire group to a project so all members get access at once. See [Project Roles > Group Access](/administration/project-roles.md#group-access) for details. * **Team structure**: Reflect your organization's structure — offices, departments, disciplines — so admins can manage users by team rather than individually. * **Settings and insights**: Group Admins can manage notification locks and custom insight preferences at the group level. ## How Groups Work Each group has a name, an optional description, and one or more members. **A user can belong to multiple groups at the same time** — for example, a user can be in both an "Engineering" group and a "London Office" group. Adding a user to a group is additive: their other group memberships are unchanged. One group can be marked as the **default group**. New members added to the organization are automatically placed in the default group. ## Settings Group A user's **settings group** determines which group's settings (notification locks and custom insight preferences) apply to them. A user can belong to many groups, but **only one of those groups may be marked as a settings group** — this avoids ambiguity over which group's settings cascade to the user. In the [Organization Settings → Groups](https://app.cogram.com/dashboard/settings/admin/groups) table, the **Settings Group** column marks which groups are configured as a settings group. A group can be marked as a settings group from its details page. If marking a group as a settings group would put any of its members in two settings groups at once, the change is rejected with a conflict — resolve it by removing the user from one of the conflicting groups first. ## Creating and Managing Groups To create a group, go to [Organization Settings > Groups](https://app.cogram.com/dashboard/settings/admin/groups) and click **Create Group**. From there you can: * Set the group name and description * Add or remove members * Mark the group as default * Assign the group to projects ## Group Admin Role A **Group Admin** is a user who has been granted scoped admin authority over one or more specific groups. It is not an [organization role](/administration/organization-roles.md) — a Group Admin keeps whatever org role they already have (Member by default), and the badge can be assigned to any user in the organization, including Owners and Admins. The same user can administer multiple groups. Within the groups they administer, a Group Admin can: * Add or remove members * Edit the group name, description, and group-level settings (notification locks, custom insight preferences, learned words) A Group Admin **cannot** create or delete groups, and cannot grant or revoke the Group Admin badge for other users — those actions are reserved for Owners and Admins. To assign or remove the Group Admin badge, open a group from [Organization Settings → Groups](https://app.cogram.com/dashboard/settings/admin/groups) and edit its admins list. Granting and revoking the badge is restricted to Owners and Admins. ## Managing Group Membership Anyone who can manage a group's membership can add or remove **any user in the organization**, regardless of that user's organization role. Adding an Owner or Admin to a group does not change their org-wide authority — the membership row is purely about group association. | Action | Owner | Admin | Group Admin | | --------------------------------------------- | :---: | :---: | :---------: | | Create or delete groups | ✓ | ✓ | | | Add or remove users in a group | ✓ | ✓ | ✓ ¹ | | Edit group name, description, and settings | ✓ | ✓ | ✓ ¹ | | Grant or revoke the Group Admin badge | ✓ | ✓ | | | Mark a group as the default or settings group | ✓ | ✓ | | ¹ Group Admins can only act on groups they administer. To manage a group's membership, go to the group's members page in [Organization Settings → Groups](https://app.cogram.com/dashboard/settings/admin/groups) and use the **Add members** button. Adding a user who is already in another group does **not** move them — they will belong to both groups. ## Groups and Project Access When a group is assigned to a project, all members of the group automatically get **Member** access to that project. Group-assigned users appear in a separate **Via groups** section in the project's members list. If a user is both directly added to a project and a member of an assigned group, their effective role is the higher of the two — a direct **Owner** keeps Owner; a direct **Viewer** is elevated to **Member** by the group; a direct **Member** stays at Member. Because a user can belong to multiple groups, project access via groups is a union — a user keeps access as long as they are in **any** assigned group. To revoke a user's group-based access to a project, either remove them from every assigned group that grants that access, or unassign the group from the project in [Organization Settings → Groups](https://app.cogram.com/dashboard/settings/admin/groups). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cogram.com/administration/groups.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.