> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/approval-workflow/what-are-access-requests/initiate-an-access-request.md).

# Initiate an Access Request

To initiate an access request, you will need to click on the `Request Access` button on any asset that has a "lock" icon view in the Catalog.

<figure><img src="/files/O4yi3UjkSGoboOxSIGC6" alt=""><figcaption><p>Catalog with assets that are "locked".</p></figcaption></figure>

When requesting access to an asset, the owner of the asset will automatically be selected as the reviewer. If there is no designated asset owner in the Catalog, then the request will be sent to the designated owner of the parent asset (eg. Schema) or the source owner.

User can specify how long the access is required and the purpose of the request in the access request form which will be submitted to the reviewer.

<figure><img src="/files/5bBAd2tEeWNZokn6kEMH" alt=""><figcaption><p>Fill in the access type requested and reason for requesting access.</p></figcaption></figure>

When the access request is sent, the reviewer will then receive an email. Clicking on the link in the email will bring them to the request approval form.

<figure><img src="/files/eR93cLb8qRy9JCPYPi15" alt=""><figcaption><p>Approving an access request</p></figcaption></figure>

The reviewer can then review the access request and select the permissions that can be granted to the specific asset for the user. They can also change the access type (either permanent to temporary or temporary to permanent).

Once the reviewer completes the form and submits the permissions, the requestor can then access the asset with the appropriate access controls granted.


---

# 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.decube.io/approval-workflow/what-are-access-requests/initiate-an-access-request.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.
