> For the complete documentation index, see [llms.txt](https://atd-dts.gitbook.io/admin-shared-mobility-portal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atd-dts.gitbook.io/admin-shared-mobility-portal/application-statuses.md).
# Application Statuses
| Status | Description | Notes |
| ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
Not Submitted
| The provider has not submitted their application yet | *This does not appear on the Reviewer Dashboard unless you filter for "All".* |
|
Needs Review
| The provider has submitted their application and requires review by staff | *This will be when an email is generated to the resource account* |
|
In Progress - Pending Action
| When a reviewer has completed a review and needs a customer action to take place (ex. re-upload documents) |
The reviewer will need to mark the:
Attachment Status,
Attachment Comment (optional)
Change Status
Add Reviewer Comment (where you can add custom text for provider) or
Send "Pending Action" Email (default response)
|
|
In Progress - Completed Action
| The provider has re-uploaded their documents and re-submitted their application and requires review by staff | *This will be when an email is generated to the resource account to require an initial review by staff* |
|
Pending Approval - Pending Action
|
When a reviewer has completed a review and needs a customer action to take place (ex. upload final submission documents)
|
The reviewer will need to mark the:
Attachment Status,
Attachment Comment (optional)
Change Status
Add Reviewer Comment (where you can add custom text for provider) or
Send "Pending Action" Email (default response)
|
|
Pending Approval - Completed Action
| The provider has re-uploaded their surety bond and insurance documents and re-submitted their application and requires review by staff | *This will be when an email is generated to the resource account to require a final review by staff* |
|
Pending Approval - Pending Payment
| When a reviewer has completed the final review and needs a customer to make payment | |
|
Pending Approval - Permit Team
| The provider has submitted their payment and requires review by permit team staff | *You will want to keep the application in this status until you have added the permits to on the Provider page so that their Approval letter will populate* |
|
Approved
| The reviewer has added the permits on the Provider page and would like the provider to view their Approval Letter | |
|
Expired
| This status is when the application has not been submitted and reached an Approval state | |
|
Cancelled
| The status when a provider has decided not to continue to purse a license application. | |
---
# 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://atd-dts.gitbook.io/admin-shared-mobility-portal/application-statuses.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.
