> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/end-user-guide-for-selfservice/your-access/my-groups.md).
# My groups
Work with the groups you are responsible for managing.
A **group** is a collection of people who share the same access. Rather than granting a folder, mailbox, or application to fifty people one at a time, your organization grants it once to a group and puts the fifty people in it.
**My Groups** lists the groups **you are responsible for managing** — not the groups you personally belong to. If you own or administer a group, it appears here.
Open it from **Access Management → My Groups**. The page is headed **My Groups**, with *Groups available to you to manage* beneath it.
{% hint style="info" %}
Looking for the groups **you are a member of**? Those are part of your own access — see [Your access](/end-user-guide-for-selfservice/your-access.md), where they appear under the application they belong to.
{% endhint %}
## What the list shows
| Column | What it tells you |
| ------------------ | -------------------------------------------------------------------------------------------------------------- |
| **Name** | The group's name, with its description underneath |
| **Status** | Whether the group is **Active** |
| **Managed System** | The managed system the group lives in — for example a directory. A dash means the group exists only in OpenIAM |
| **Actions** | An edit action for opening the group |
Use **Search by name** to find one in a long list, and **View** to change how the list is displayed.
## Why the managed system matters
A group with a managed system named against it exists in that system — adding someone to it changes their access there, not just in OpenIAM. A group with a dash is internal to OpenIAM, and is typically used to bundle other entitlements together.
It is worth knowing which you are looking at before you change membership: one reaches into a live system, the other does not.
## Adding and removing people
Opening a group lets you work with its membership, within whatever permission you have been given.
Two habits worth keeping:
* **Add through a request where you can.** A membership that arrives through [a request](/end-user-guide-for-selfservice/requests/request-access.md) carries a reason and an approval with it. One added directly does not, and a reviewer later has no way to tell why the person is there.
* **Take people out when they move on.** Group membership is one of the most common places stale access hides, precisely because nobody is prompted to remove it.
## If a group looks wrong
* **You're managing a group you don't recognise.** Ownership can be inherited when someone leaves. If it isn't yours, say so rather than quietly keeping it.
* **A group has no members.** An empty group that still carries access is worth retiring — see [Group management](/end-user-guide-for-selfservice/for-managers/group-management.md).
* **You expected a group and it isn't here.** You may not be its owner. Your help desk can tell you who is.
---
# 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://docs.openiam.com/end-user-guide-for-selfservice/your-access/my-groups.md?ask=&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.
