> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oncanary.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Requests

> Capture maintenance needs, route them for review, and connect approved work to a work order.

A Request is an intake record for maintenance work that still needs review. It gives requesters a simple way to report an issue while maintenance teams retain control over the work order that will be planned and assigned.

Requests can come from a requester account, a public [Request Portal](/help/requests/request-portals), or the API.

## What a Request can contain

* Required Request Title
* Description and contact information
* Priority
* Location and asset
* Pictures, files, and configured custom fields
* Approval destination or assigned team
* Source and Request Portal provenance
* Review or cancellation reason
* One linked work order after approval

The exact fields shown to signed-in requesters follow the organization's **Request preferences**. A Request Portal has its own field configuration.

## Request lifecycle

| Status    | Meaning                                                               |
| --------- | --------------------------------------------------------------------- |
| Pending   | The request is waiting for maintenance review.                        |
| Approved  | A reviewer approved it and created the linked work order.             |
| Declined  | A reviewer declined it, optionally with a visible reason.             |
| Completed | The linked work order is Done.                                        |
| Canceled  | The requester canceled their own pending request with an explanation. |

Approval creates and links one work order in the same operation. Completing that work order moves the Request from Approved to Completed. Reopening the work order returns the Request to Approved.

## Access by role

* **Admins** see and review every Request and manage Request Portals.
* **Members** see and review Requests routed to teams they belong to.
* **Requesters** create and view their own Requests. They can edit or cancel a Pending Request and delete their own Pending or Declined Requests.

Requesters follow maintenance progress through the Request status. Work-order access remains governed separately.

Deleting a Request removes it from the Request workspace. Any work order already created from it remains part of maintenance history.

## Common tasks

* [Submit and review a Request](/help/requests/create-and-review)
* [Create and share a Request Portal](/help/requests/request-portals)
* [Understand the linked work order](/help/work-orders/overview)