> 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/direct-report-operations.md).

# Acting for your team

Reset passwords, review access, manage accounts, and disable users on your team.

These actions are reached from **Manage Users** — select a person, then choose what you need to do. **Bulk Operations** and **Bulk Request** at the top right apply an action to several people at once.

## Reviewing someone's access

Opens the same view as [Your access](/end-user-guide-for-selfservice/your-access.md), for them: their roles, groups, resources, and the accounts they hold in managed systems.

Use it before approving a request for them, before a role change, and whenever you're asked "what can this person actually get to?"

## Raising a request for them

See [Requesting for other people](/end-user-guide-for-selfservice/requests/request-for-others.md).

## Resetting a password

For when someone is locked out and can't wait.

{% stepper %}
{% step %}
**Select the person and choose to reset their password.**
{% endstep %}

{% step %}
**Select the managed system.**

You are asked to **Select Managed System** — the managed system the reset applies to. Someone may have accounts in several, so choose the one they actually can't get into. Some organizations let you reset across all of them at once.
{% endstep %}

{% step %}
**Complete the reset and tell them how to get the new password.**

Depending on your setup, a temporary password is generated or sent to them directly.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Encourage people to set their [security questions](/end-user-guide-for-selfservice/signing-in/security-questions.md) so they can reset their own password next time. It's faster for them and removes the work from you.
{% endhint %}

## Managing identities

An **identity** is one person's account in one managed system. This action lets you enable or disable those accounts individually — useful when someone should lose access to one system but keep the rest.

Before it acts, you are shown exactly what will happen:

> *"You are about to … the following identities for user …"*

and, if you selected everything:

> *"You are about to … all identities for user …"*

Read that line before confirming. It names the person and the accounts, and it is the last point at which a mistake is cheap to correct.

## Disabling and enabling a user

**Disable user** suspends someone's access without deleting anything. **Enable user** restores it.

Use disable when someone:

* goes on extended leave
* is under investigation
* has left, but their accounts must be retained for a period

Disabling is the right tool precisely because it is reversible. Deleting an account destroys history that may be needed later.

## Converting a user

**User conversion** changes someone's type — contractor to employee, for example. It is not a cosmetic change, and the portal warns you plainly:

> *"Converting user … from … to … may affect their identities, attributes, and entitlements. Please confirm that you understand the implications."*

Because access is often granted by user type, converting can add and remove access automatically. Check afterwards that the person still has what they need, and no longer has what they shouldn't.

## Bulk and contract operations

Where the same change applies to several people, bulk operations let you do it once. Contract operations handle contractor-specific arrangements such as extending or ending an engagement.

{% hint style="warning" %}
Bulk actions multiply mistakes as efficiently as they multiply work. Check the list of selected people before you confirm — an action applied to the wrong twenty people takes far longer to undo than it took to do.
{% endhint %}

## Before you act, tell the person

Every one of these actions is visible to the person it affects — usually as something suddenly not working. A short message beforehand prevents a support ticket and a bad afternoon.


---

# 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/direct-report-operations.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.