> For the complete documentation index, see [llms.txt](https://docs.ideogram.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ideogram.ai/plans-and-billing/groups.md).

# Enterprise Groups

Create and manage Enterprise groups, add members, and understand how nested groups control collection access.

Groups let you share collections with part of an Enterprise organization. Owners and admins manage them in **Settings** → **Groups**. The Groups page isn't available in personal, Team-plan or prepaid API workspaces, or to ordinary Enterprise members.

## Create a group

1. Switch to your Enterprise workspace.
2. Open **Settings** → **Groups**.
3. Click **Create group**.
4. Enter a name of up to 100 characters.
5. Choose a **Parent group**, or **None (top level)**.
6. Click **Create**.

Groups can nest up to three levels. The parent picker only offers groups that fit within this limit.

## Add or remove members

1. Select a group from the list.
2. Under **Members**, type a name or email in **Add people by name or email**.
3. Select an organization member from the suggestions.

To remove a direct member, click **Remove** beside their name. This removes their membership of that group; it doesn't remove them from the organization.

### How nested membership works

Members of a subgroup also belong to the groups above it. For example, someone in **Design → Footwear** can access collections shared with **Footwear** and collections shared with **Design**, at the permissions granted to those groups.

The Members section manages people added directly to the selected group. A person may still have access through another group, an ancestor group or a separate collection share after you remove a direct membership.

## Review shared collections

Select a group and look under **Shared collections**. Each row shows the collection and its permission, such as **Can view** or **Can edit**. A **via \[group name]** label identifies access inherited from another group. Click a collection's name to open it, or **Load more** to see more rows.

To grant or change collection access, use that collection's **Share** dialog. See [Share a collection with your team](/organize-and-share/collections.md#share-a-collection-with-your-team).

## Rename or move a group

Open the group's row menu:

* **Rename** changes its name. Enter the new name and click **Save**.
* **Move** changes its parent. Choose **Parent group**, or **None (top level)**, then click **Move**.

Moving a group changes which ancestor groups its members belong to, so it can change the collections they can access. The picker excludes the group itself, its subgroups and destinations that would exceed three levels.

The depth check includes the group's subgroups. For example, a group with a subgroup can't move beneath a group already at level two: the move would put its subgroup at level four. Move the subgroup first or choose a shallower parent.

## Delete a group

1. Move or delete its subgroups first. **Delete** is disabled while the group has subgroups.
2. Open the group's row menu and click **Delete**.
3. Review the warning, then confirm with **Delete group**.

Collections shared with the deleted group stop being shared with its members through that group. The collections and organization members remain; access granted separately through other shares can still apply.

## Why can't I save or load a group?

**Create** or **Save** requires a name containing more than spaces. Leading and trailing spaces are removed. Renaming to the same name or moving to the same parent doesn't enable a new submission. Controls also pause while a change is being saved.

**No members yet** is an empty membership list. **Couldn't load members** is a loading failure; use **Try again** before treating the list as empty. The group list and shared-collection list also offer retry controls when they fail to load.

If creating or changing a group fails, read the error message and try again after correcting the indicated issue. The app may show a specific server message or **Something went wrong. Please try again.** A failed load doesn't establish that a group or its collection shares were deleted.