> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-user-guides/crs-guide/how-to.../managing-submitted-requests-screen.md).

# Managing Submitted Requests Screen

Audience

Applicable to users responsible for managing content requests. See also: [SIRS to CRS Status Map](https://github.com/SNOMED-Documents/snomed-crs-guide/blob/main/SIRS-to-CRS-Status-Map_31985160.html) for task status meaning

## Accept Request

From **CRS Dashboard** , in **Submitted Requests (1)** , select a request which has status is **New (2)** to go to request details page.|

<figure><img src="https://1680366874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT7gOK7qF5jKUT64ZHaBu%2Fuploads%2Fgit-blob-2f6f207ccdb5cd7ba0c4d745a2c4ba93acb1b828%2F29953319.png?alt=media" alt=""><figcaption></figcaption></figure>

*Figure 1: The Submitted Requests screen* select **Accept Request** (1) button to accept a request, then you will be redirected to **CRS Dashboard**

<figure><img src="https://1680366874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT7gOK7qF5jKUT64ZHaBu%2Fuploads%2Fgit-blob-9ee302d0206a0be24833c38365946151e17d497d%2F28743000.png?alt=media" alt=""><figcaption></figcaption></figure>

## Reject Request

From **CRS Dashboard** , in **Submitted Requests** (Figure 1), select a request which has status is **New** to go to request details page.select **Reject Request** (1) button and provide a reason and select Confirm button **in Reject Request dialog (2)** to reject a request, you will be redirected to **CRS Dashboard.**|

## Clarification Requested

From **CRS Dashboard** , in **Submitted Requests** (Figure 1), select a request which has status is **New** to go to request details page.Select **Pending Clarification** (1), to launch the , **Pending Clarification dialog** (2). Enter a **Reason** (what clarification is desired on) and select **Confirm** , you will be redirected to **CRS Dashboard.**|

## Appeal Rejected Request

From **CRS Dashboard** , in **My Requests** , select a **rejected** request to go to request details page.select **Appeal Rejection** (1) button to appeal a request, then provide a reason and select Confirm button in **the Appeal Request Rejection** (2) you will be redirected to **CRS Dashboard.**|

## Withdraw Request

From **CRS Dashboard** , in **My Requests** , select a **Accepted** request to go to request details pageSelect **Withdraw Request** (1), to launch the **Withdraw Request** dialog (2). Provide a reason and select **Confirm** , then you will be redirected to **CRS Dashboard.**|

<figure><img src="https://1680366874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT7gOK7qF5jKUT64ZHaBu%2Fuploads%2Fgit-blob-818eb3c1a69e2a7c16fe0eb7c63f09a3657b6593%2F29953323.png?alt=media" alt=""><figcaption></figcaption></figure>

\\

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Content+Request+Guide&#x26;entry.670899847=Managing%20Submitted%20Requests%20Screen" class="button primary">Provide Feedback</a>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snomed.org/snomed-ct-user-guides/crs-guide/how-to.../managing-submitted-requests-screen.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
