# User request overview {% hint style="success" %} **Access Type**: User Requests - Editor or Viewer **Premium Feature**: DSAR {% endhint %} When an end-user submits a DSAR to your organization, a ticket is created for the request in the **User Requests** tab of Privacy Requests. In this article, we will cover the following: * [Filter user requests](#filter-user-requests) * [User request details](#user-request-details) Click **Privacy Requests** on the left-hand panel and ensure the **User Requests** tab is selected on the subsequent page.

*** ### Filter user requests From the **User Requests** tab, your organization can view all new, current, and past user requests submitted to your organization. Use the provided dropdown menu to filter the list by:

Filter	Description
Type	Filters list to one of the three user request types: Access data request Delete data request Opt-out of sales request
Status	Filters list to tickets with a particular status. Click here to learn more about user request statuses.
Create date or due date	Sort the list by: Newest -creation date, descending order Oldest - creation date, ascending order Least urgent - Sorted by due date, ascending order Most urgent - Sorted by due date, descending order

Filter

Description

Type

Filters list to one of the three user request types:

Access data request
Delete data request
Opt-out of sales request

Status

Filters list to tickets with a particular status. Click here to learn more about user request statuses.

Create date or due date

Sort the list by:

Newest -creation date, descending order
Oldest - creation date, ascending order
Least urgent - Sorted by due date, ascending order
Most urgent - Sorted by due date, descending order

### User request details View the details of any user request by clicking the **Details** button within the user request card.

From the details page of a user request, your organization can view the following information:

Field	Description
Request type	Whether the ticket is one of three request types: Access data request Delete data request Opt-out of sales request
Ticket ID	Didomi assigned ID to the user request.
Status	Identifies the progress of the user request in your organization's workflow. Click here to learn more about user request statuses.
Due in	Once a request is submitted, your organization needs to process the request within the statutorily defined deadline. The deadline varies depending on the request type and the applicable data privacy regulation. To assist you in responding to requests on time, Didomi calculates and displays the number of days until the deadline for each request.
Date of completion	Date the user request was fulfilled by your organization. Only available for tickets with Fulfilled status.
Date of rejection	Date the user request was refused by your organization. Only available for tickets with Refused status.
Date of archive	Date the user request was archived by your organization. Only available for tickets with Archived status.
Date of request	Date the end-user made the DSAR request.
User ID	Unique user identifier for the end-user. If the request is submitted through the privacy request widget, the User ID will be the email address that was used to create the request. If the request is submitted through the API, the User ID can be something other than the email address. For further info on how to use different User IDs, please check our developers documentation.
Email address	Email address provided when the request was created.
Request history	Tracks changes and internal notes added to the request.
Ticket note	Internal notes created by your organization for the request. Click here for more information on user request notes.

--- # Agent Instructions: 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: ``` GET https://docs.didomi.io/privacy-requests/user-requests/user-request-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.