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

# Submit, track, and revise requests

> Requester and approver steps from category cards to completion.

## Submit a request

Open Request Forms/the requester dashboard and select an authorized category/form card. Check versions, complete required fields and dynamic tables, upload attachments, and review before Submit. A saved draft is not an accepted submission.

PDFs, PPTX files, and images are reviewed within the platform according to supported formats/converter availability. Do not upload unnecessary data. Enable signing per document when needed, configure signer/input layout, and confirm the workflow supports it.

## Read status

Open **My Requests**, use filters/pagination, then open request details. History shows visited nodes, decisions, actors, datetimes, and available SLA information. Active requests show approval-layer information. History is not a list of every possible branch as though all were executed.

## Approver actions

Open **My Approvals**, choose a task, and review form data, attachments, and notes. Use the document reviewer for annotations/notes. Confirm the reviewed version is current. Approve, Reject, and Need revision are different decisions; a comment alone does not decide a task.

## When revision is needed

1. Open the notification or the same request's details.
2. Read the revision reason, approver notes, and document annotations.
3. Correct allowed fields/attachments. Replacing a document may require a new signing layout.
4. Save if needed, review the updated data, then **Resubmit**.
5. The process follows the configured Revision/Loop route; it does not automatically restart every node.

Exhausted revision limits do not make a request Approved. Final actions follow valid policy and decisions. A final Rejected request requires a new submission if the organization wants to restart.

## After approval

Finish Approved records the approval outcome. Track any configured signing obligations separately. Approved does not mean vendor payment, every recipient Signed, or completion in an external system.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.