> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/team-and-account/user-groups.md).

# User groups

Split a large team into groups so each group shares requests, contacts and templates only among its own members.

{% hint style="info" %}
Available on the **Enterprise** plan.
{% endhint %}

Groups divide a team into smaller units, such as offices or departments. Members of a group share access to templates, requests and other assets with the rest of their group, not with the whole team.

## Who sees what

| Person                       | Sees work from                              |
| ---------------------------- | ------------------------------------------- |
| Member of one or more groups | The other members of their groups           |
| Member in no group           | Other team members who are also in no group |
| Team admin in no group       | Everyone on the team, across all groups     |

The team's **Shared inbox** setting still applies inside each group: with it off, members see only their own requests and the ones assigned to them. See [Team members and admins](/team-and-account/team-members-and-admins.md#team-wide-settings).

A template shared into a group is visible to that group's members. See [Share, lock, reorder and duplicate templates](/templates/share-lock-reorder-and-duplicate.md).

## Create a group

{% stepper %}
{% step %}

### Open Groups

Go to [Team → Groups](https://pipefile.com/dashboard/settings/team#groups) and click **Manage**.
{% endstep %}

{% step %}

### Name the group

Click **Create group**, enter a **Group Name** and click **Save**.
{% endstep %}

{% step %}

### Add members

Open the group, click **Add members**, choose people under **Select Team Members**, and click **Add to Group**.
{% endstep %}
{% endstepper %}

You can also put new people straight into groups when you invite them: use **Assign to Groups (Optional)** in the invite window.

## Change or delete a group

On a group's page:

* Remove a member with the remove icon next to their name, then confirm with **Remove From Group**.
* Use the **...** menu for **Edit Group** (rename) or **Delete Group**.

Members marked **Admin** inside a group are group admins. To make someone a group admin, contact <support@pipefile.com>.

{% hint style="info" %}
If you use single sign-on with directory sync, groups and their members can be kept in step with your identity provider. See [Single sign-on](/team-and-account/single-sign-on.md).
{% endhint %}

## Related

* [Team members and admins](/team-and-account/team-members-and-admins.md)
* [Assign requests to teammates](/requests/assign-requests.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.pipefile.com/team-and-account/user-groups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.