> 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/requests/request-for-others.md).

# Requesting for other people

Raise requests on behalf of colleagues, individually or for several people at once.

If you manage people, or have been given a delegated-administration role, you can raise requests for other people as well as yourself. A new joiner rarely knows what to ask for — their manager does.

This page needs the right permission. If you don't have it, the option to choose another person simply isn't there.

## Requesting for one person

{% stepper %}
{% step %}
**Start the request.**

Open **Requests → Create Request**.
{% endstep %}

{% step %}
**Choose the person.**

Search for them by name. You can select only people you are allowed to act for — usually your direct reports, or a group you administer.
{% endstep %}

{% step %}
**Select what they need.**

Exactly as for yourself. For a new joiner, look for an [access profile](/end-user-guide-for-selfservice/your-access/access-profiles.md) matching their job — one request instead of a dozen, and nothing forgotten.
{% endstep %}

{% step %}
**Explain why.**

Say who they are and what they will do — "new starter in Finance, starts Monday" tells the approver everything.
{% endstep %}

{% step %}
**Submit.**

You are recorded as the requestor, and they as the person it is for. Both of you can follow it in [Request history](/end-user-guide-for-selfservice/requests/request-history.md).
{% endstep %}
{% endstepper %}

## Requesting for several people at once

For a whole team — a new intake, a department reorganisation, a group that all need the same tool — use the bulk option: **Create Request → Bulk Access Request**.

{% stepper %}
{% step %}
**Select the people.**

Search and pick everyone the request covers.
{% endstep %}

{% step %}
**Select the access.**

Everything you choose is requested for everyone you selected.
{% endstep %}

{% step %}
**Review carefully before submitting.**

Bulk requests multiply mistakes. Check both lists — the wrong item across twenty people is twenty things to unpick.
{% endstep %}

{% step %}
**Submit.**

This may create one request covering everyone, or one per person, depending on your organization's configuration. Either way you can track it in [Request history](/end-user-guide-for-selfservice/requests/request-history.md).
{% endstep %}
{% endstepper %}

There is a matching bulk option for removal — see [Giving up access](/end-user-guide-for-selfservice/requests/revoke-access.md) — which is the efficient way to strip access from a whole team at the end of a project.

## Things to keep in mind

* **You are accountable for what you request.** Your name is on it. Request what people need for their job, not everything they might conceivably touch.
* **It still needs approval.** Requesting for someone doesn't skip the approval chain, and you may not be the approver.
* **The person is notified.** They can see what was asked for on their behalf.
* **Prefer access profiles for joiners.** They are designed for exactly this and are far less error-prone than assembling a list by hand.

{% hint style="info" %}
For someone changing role rather than joining, don't just add the new access — arrange for the old to be removed too. Access that accumulates across role changes is the most common finding in access reviews. See [Position and role changes](/end-user-guide-for-selfservice/your-team/position-change.md).
{% 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/requests/request-for-others.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.