> 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-team.md).
# Your team
See the people who report to you and what you can do for them.
If people report to you, SelfService gives you a view of them and a set of actions you can take on their behalf — without raising a ticket for every small thing.
Open **Access Management → Manage Users**, or use the **My Team** shortcut at the top of the screen. The page is headed **Manage Users**, with **Direct reports of** your name beneath it.
If nobody reports to you, this area doesn't appear.
## Who appears here
The people whose **supervisor** is set to you in OpenIAM. That comes from your organization's HR data, so:
* someone who has just joined your team may not appear until the HR record catches up
* someone who has left your team may still appear for the same reason
* if the list is persistently wrong, the fix is in the HR record, not here — talk to HR or your help desk
The list is split into **Active Users** and **Inactive Users**, so people who have been disabled or have left are separated from your working team rather than cluttering it.
For each person you see at least their **Name** and **Email**, and can open their record for more.
## What you can do
From here you can act for any of your reports:
| Action | When you'd use it | Details |
| ------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **Create request** | They need access | [Requesting for other people](/end-user-guide-for-selfservice/requests/request-for-others.md) |
| **Review access** | Check what they currently hold | [Direct report operations](/end-user-guide-for-selfservice/your-team/direct-report-operations.md) |
| **Reset password** | They're locked out and need to work now | [Direct report operations](/end-user-guide-for-selfservice/your-team/direct-report-operations.md) |
| **Manage identities** | Enable or disable their accounts in specific systems | [Direct report operations](/end-user-guide-for-selfservice/your-team/direct-report-operations.md) |
| **Disable / enable user** | Suspend or restore someone's access | [Direct report operations](/end-user-guide-for-selfservice/your-team/direct-report-operations.md) |
| **Position change** | They're moving role, team, or manager | [Position and role changes](/end-user-guide-for-selfservice/your-team/position-change.md) |
| **Leave or termination** | They're going on leave or leaving | [Leave and termination](/end-user-guide-for-selfservice/your-team/leave-and-termination.md) |
| **Bulk operations** | The same change for several people | [Direct report operations](/end-user-guide-for-selfservice/your-team/direct-report-operations.md) |
## The responsibility that comes with it
These actions take effect on real accounts. Disabling someone stops them working; resetting a password locks them out of a saved session; removing access can interrupt a task mid-flow.
Three habits make this safe:
* **Tell the person.** Almost every problem here is someone being surprised.
* **Check you have the right person** before acting — similar names are common.
* **Prefer the reversible option.** Disabling is recoverable; deleting often isn't.
{% hint style="info" %}
Everything you do here is recorded against your name, with a timestamp. That is protection for you as much as oversight of you — if a question is asked later about why someone's access changed, the record shows what happened and when.
{% endhint %}
---
# 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-team.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.
