> For the complete documentation index, see [llms.txt](https://authdocs.skill-mine.com/licentio-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://authdocs.skill-mine.com/licentio-documentation/workflow/manage-request.md).
# Manage Request
The page consists of three tabs for request filtering:
1. **Pending**: Displays all requests currently awaiting action.
2. **Approved**: Shows requests that have been approved.
3. **Rejected**: Lists requests that have been rejected.
***WORKFLOW NAME*** : The name of the workflow associated with the request.
***STEP(S)*** : The current step of the workflow where the request is located.
***APPLICANT NAME*** : Name of the user who submitted the request.
***APPLICANT EMAIL*** : Email ID of the applicant.
***REQUESTED TIME*** : The time elapsed since the request was submitted. Displayed in months and days.
#### **Action Buttons**
1. **View History** (Blue Button):\
Opens a detailed history of the request, showing previous steps, actions taken, and timestamps.
2. **Approve** (Green Button):\
Approves the request.
3. **Reject** (Red Button):\
Rejects the request.
---
# 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://authdocs.skill-mine.com/licentio-documentation/workflow/manage-request.md?ask=&goal=
```
`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.