> 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.../navigating-crs-from-the-sidebar.md).

# Navigating CRS from the Sidebar

## What are **My Requests**?

These are the requests that the current user has submitted. From this dashboard as user may view their own requests and track their progress through evaluation and, if accepted, eventual inclusion into SNOMED CT.|

<figure><img src="/files/ASUrRHX9Ke5lIMCgaenP" alt=""><figcaption></figcaption></figure>

## What are **My Assigned Requests**?

These are the requests that the current user has been assigned. From this dashboard as user can view their assigned requests and update request in to CRS and SNOMED CT.|

<figure><img src="/files/pKGPf9P9LrMpJSFlkpWu" alt=""><figcaption></figcaption></figure>

## What are **Submitted Requests** ?

Users may search requests from other users to identify similar or identical requests.|

<figure><img src="/files/4U1t0371DHYcLuut1XIr" alt=""><figcaption></figcaption></figure>

## What are **Accepted Requests**? :

Following initial review, each request is assigned a manager who is a member of the IHTSDO Content Team. A change to a status of “Accepted in scope” does not mean that the request will be approved for inclusion in SNOMED CT.|

<figure><img src="/files/woppNUlqFihs1dqyoh71" alt=""><figcaption></figcaption></figure>

## What are **My Batch Requests**?

Refers to Content Requests for a large scale addition of new content/ and or large scale modifications to existing content.|

<figure><img src="/files/p2quy1FhBfDwOPKDFO3o" alt=""><figcaption></figcaption></figure>

## What is **Create New Request**?

Allows a user to create a Content Request in simple or direct mode|

<figure><img src="/files/sXlQEHJgqqQ7FDrBaSVn" alt=""><figcaption></figcaption></figure>

## What is **New Batch Import**?

Allows a user to create a request for large numbers of new content adaptations or modifications by uploading content.|

<figure><img src="/files/px9ZQ1O0IvgrpWmFPa5z" alt=""><figcaption><p>_</p></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=Navigating%20CRS%20from%20the%20Sidebar" 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 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://docs.snomed.org/snomed-ct-user-guides/crs-guide/how-to.../navigating-crs-from-the-sidebar.md?ask=<question>&goal=<endgoal>
```

`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.