> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/lifecycle-management/jitpbac/purposes/create-user-purpose-access-request/creating-a-request-through-the-web-application.md).

# Creating a request through the web application

1. To create a new user-purpose access request, navigate to the "Access Requests" page. Click the three-dot menu in the top right corner, and from the dropdown menu, select "New Purpose Access Request".<br>

   <figure><img src="/files/ntO2yyd17yYJHx1MkMmD" alt=""><figcaption></figcaption></figure>
2. Fill all the required fields on the form and click Next button at the bottom of the page to proceed to the next step.\
   \
   Multiple users can be selected to request purposes in bulk. The “Purpose Identical To” field allows for easy lookup of the desired purpose based on the information provided during purpose creation.<br>

   In the screenshot below, “Purpose Identical To” is set to “Team”, and the purposes under “Team 2” are listed for selection for the chosen users. Alternatively, the “Custom” option can be used to manually select the purposes to assign to the selected users.\ <br>

   <figure><img src="/files/wfXdWFEYG60zj5669lvn" alt=""><figcaption></figcaption></figure>

   <figure><img src="/files/O8gTyjx9F1SWPQrqxTaB" alt=""><figcaption></figcaption></figure>

   <figure><img src="/files/8zdPU5FvWCL0yEBbq91k" alt=""><figcaption></figcaption></figure>
3. Review the entered details carefully on the confirmation page. If everything is accurate, click Create to submit the new user-purpose access request(s).<br>

   <figure><img src="/files/IshKooIoQxHXnpfj4WaN" alt=""><figcaption></figcaption></figure>
4. After creation, the new user-purpose access request will be visible on the Access Requests page. The appropriate reviewer assigned to the request will receive a notification via Slack prompting them to review the request.

   <figure><img src="/files/JtUc5Sdf882yjYEjDy1p" alt=""><figcaption></figcaption></figure>
5. The assigned reviewer can review the access request by navigating to the My Tasks page from the side navigation bar. They should click on the Review button to open and evaluate the request.<br>

   <figure><img src="/files/wAzYlZ02Us56rKRVI2KY" alt=""><figcaption></figcaption></figure>

   <figure><img src="/files/PJ2Uh5iLdHCV4hAtSA6j" alt=""><figcaption></figcaption></figure>
6. Once the reviewer approves the user-purpose access request, the status will update on the Access Requests page. The requested purpose will then be assigned to the employee for whom the request was made.<br>

   <figure><img src="/files/eSFgsZicjESOKUm9BQH8" alt=""><figcaption></figcaption></figure>

To use assigned purposes, refer to [Starting & Stopping Assigned Purposes](/lifecycle-management/jitpbac/purposes/starting-and-stopping-assigned-purposes.md).


---

# 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.balkan.id/lifecycle-management/jitpbac/purposes/create-user-purpose-access-request/creating-a-request-through-the-web-application.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.
