> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/privacy-requests/user-requests/create-user-request-note.md).
# Create user request note
{% hint style="success" %}
**Access Type**: User Requests - Editor
**Premium Feature**: DSAR
{% endhint %}
User requests notes enable your organization to include additional information to a specific user request. In this article, we will cover how to add a new note to a user request.
{% hint style="info" %}
There is only one note per user request. Any subsequent edits to the note is stored in a single note instead of as separate notes for the ticket.
{% endhint %}
Click **Privacy Requests** on the left-hand panel and ensure the **User Requests** tab is selected on the subsequent page.
Navigate to a user request on the list and click the **Details** button in the user request card.
Navigate to the **Ticket note** panel and click **Edit**.
Use the provided space to input your note and click **Save** when finished.
The new note will be added to the **Request History** for the ticket and can be viewed from the list view of your user requests.
---
# 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.didomi.io/privacy-requests/user-requests/create-user-request-note.md?ask=&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.
