> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/governance/elevated-access.md).

# Elevated access requests

Sometimes a person needs elevated Salesforce permissions in a production org for a short time — to investigate an incident or apply a manual fix. Rather than granting standing access, codev lets you **request temporary elevated access**: you name the user, the access level, and how long they need it. The request is approved like any other gated action, codev grants the access on approval, and **removes it automatically** when the time is up.

## Requesting elevated access

<figure><img src="/files/uh1GHwd1mxVc9Uf4q3IZ" alt="The Request Elevated Privileges dialog"><figcaption><p>Requesting temporary elevated access from Ops.</p></figcaption></figure>

Open **Ops > Operations** and choose **Request elevated privilege in production**. In the dialog:

| Field               | What to enter                                                                           |
| ------------------- | --------------------------------------------------------------------------------------- |
| **Project**         | The project the org belongs to.                                                         |
| **Username**        | The Salesforce user who needs the access, e.g. `user@company.com`.                      |
| **Target Org**      | The production org to grant access in.                                                  |
| **Dev Config File** | The access configuration file that defines the available access levels for the project. |
| **Access Level**    | The level to grant, chosen from the levels the access configuration defines.            |
| **Duration**        | How long the access lasts, in minutes — up to 24 hours (1440 minutes).                  |

Submitting the request creates a tracked request titled **Request — Elevated Privileges** and sends it for approval.

{% hint style="info" %}
The **access levels** you can choose are defined in the project's access configuration, not in codev. See [sfp: Access management](https://docs.flxbl.io/flxbl/sfp) for how those levels are defined for a project.
{% endhint %}

Two things to know before you request:

* The user must **already have access** in the production org — elevation raises an existing user's level, it does not create access from nothing.
* **Closing** an active elevation downgrades the user back to the default level.

## Approval and restore

An elevated-access request pauses at an [approval gate](/flxbl/codev/governance/approvals.md) — nothing is granted until it is approved. By default the project's **owners** are the approvers, and the request appears in the [Pending Approvals](/flxbl/codev/governance/approvals.md#where-approvals-appear) list alongside releases. An approver can resolve it there, or from the source thread with `/codev approve`.

* **On approval**, codev grants the chosen access level to the user on the target org and starts the clock.
* **When the duration ends**, codev restores the user's previous access automatically — you do not have to remember to revoke it.
* **On rejection**, nothing is granted.

Because it is approval-gated, the request also honors [separation of duties](/flxbl/codev/governance/approval-gates.md#separation-of-duties): with that setting on, the person who requested the elevation cannot approve their own request.

Every request and decision is recorded in the [audit trail](/flxbl/codev/settings/audit.md) — who asked for access, who approved it, for whom, at what level, and for how long.

## Related

* [Approvals](/flxbl/codev/governance/approvals.md) — how the approval gate works and where requests appear
* [Configuring approval gates](/flxbl/codev/governance/approval-gates.md#approvers-for-operational-requests) — who approves operational requests
* [Audit trail](/flxbl/codev/settings/audit.md) — the record of every request and decision


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flxbl.io/flxbl/codev/governance/elevated-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.