> 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/user-request-status-glossary.md).

# User request status glossary

{% hint style="success" %}
**Access Type**: User Requests - Editor or Viewer

**Premium Feature**: DSAR
{% endhint %}

Tickets associated with user requests are assigned statuses to help your organization monitor and manage the requests throughout the ticket lifecycle as it moves through your processing workflow. Refer to the table below for more information on each status and whether an email is automatically generated to the end-user when the ticket is changed to the status .

{% hint style="info" %}
[Click here](/privacy-requests/user-requests/update-user-request-status.md) for more information on how to update the status of a ticket associated with a user request. 
{% endhint %}

<table><thead><tr><th width="159.166748046875">Status</th><th width="415.9166259765625">Description</th><th data-type="checkbox">Email to end-user</th></tr></thead><tbody><tr><td>Unverified</td><td>The default status for a ticket when an end-user submits a DSAR through your organization's privacy request widget.<br><br>An email is delivered to the end-user's provided email address to verify the request.</td><td>true</td></tr><tr><td>Verified</td><td>The request was verified by the end-user via the email link or manually moved into the status by a member of your organization.</td><td>false</td></tr><tr><td>Work in progress</td><td>The request is currently being processed by your organization. <br><br>An email is delivered to the end-user's provided email to inform them of the status change.</td><td>true</td></tr><tr><td>Fulfilled</td><td>The request has been completed and closed. <br><br>An email is delivered to the end-user's provided email to inform them of the status change. <br><br><mark style="background-color:$warning;"><strong>Note</strong>: For access data requests, an optional field is available to let the end-user download their data.</mark></td><td>true</td></tr><tr><td>Archived</td><td>A request that no longer needs to be addressed because it has been fulfilled or refused.</td><td>false</td></tr><tr><td>Refused</td><td>The request was refused by your organization.<br><br>An email is delivered to the end-user's provided email to inform them of the status change.</td><td>true</td></tr></tbody></table>


---

# 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.didomi.io/privacy-requests/user-requests/user-request-status-glossary.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.