Data Subject Requests

Work the DSR queue.

Review, act on, and close the requests that need a human.

This is where every request lands that you haven't fully automated, plus anything that needs a human eye. Requests are collected automatically from your privacy inbox and your webform, so by the time a request reaches this page Superset has already classified it and pulled out the structured data.

The queue

Each row shows a request's Status, its Origin (Email or Webform), the requester's Email, the request Type, and when it was Received and Completed. Search the list from the box at the top, switch between list and detail layouts, and use the Showing Needs Review filter to narrow down to the requests that actually need you rather than the whole history.

The DSR Requests queue: a table with Status, Origin, Email, Type, Received and Completed columns, and a Showing Needs Review filter. — The DSR Manager queue. Use the "Showing Needs Review" filter to focus on requests that need you.

Filter and sort the DSR Manager

Beyond the Needs Review / All Requests toggle, the column headers double as filters and sorts, so you can slice the queue however you need:

Filter by Status, Origin, or Type. Click the Status header to filter by state (Submitted, Processing, Unverified, Error, Completed), the Origin header to filter by where the request came from (Webform or Email), or the Type header to filter by right (Access, Erasure, Rectification, Restriction, Portability, Automated, Optout, Sensitive). Tick the values you want to keep in view and the rest drop out.
Sort by Email, Received At, or Completed At. Click the Email, Received At, or Completed At header to sort by that column, and click again to reverse the order.

The DSR Manager queue with the Status header clicked, showing a Filter by Status menu with Submitted, Processing, Unverified, Error, and Completed checkboxes. — Click **Status**, **Origin**, or **Type** to filter the queue; click **Email**, **Received At**, or **Completed At** to sort it.

Open a request

Click any row to expand it. You'll see two blocks of detail and the actions you can take:

Metadata The request's own record: Origin, Sender's Email, Received At, Request Type, Completed At, Applicable Law, Authorized Agent Name (when it came through an agent), and Processed At.
Subject's Data The identity and address fields Superset extracted for the data subject: name, email and business email, phone, the address fields, date of birth, mobile advertising IDs, and LinkedIn, along with a Confidence rating on the extraction. Alongside each primary value, the plural email, phone, and address rows show the complete list Superset holds for the request, with the primary first. These are the same fields you can reference as variables in an automation.

An expanded DSR request showing the Metadata and Subject's Data blocks, with Mark Completed and Execute buttons. — Expanding a request shows its Metadata and the Subject's Data Superset extracted, with Mark Completed and Execute at the bottom.

Act on a request

Two buttons sit on each expanded request:

Mark Completed. Close the request by hand once you've actioned it on your side. Superset stamps the Completed At time and the request drops out of your "needs review" view.
Execute. Run the automation you configured for this right (the API call and confirmation email from Step 3) for this one request, right now. It's the manual trigger for the same flow automation runs on its own, which is handy for one-offs and for requests you wanted to eyeball before letting Superset finish them.

Tip If this queue is filling up faster than your team can work it, that's usually the signal to turn on automation for your highest-volume right and to enable Auto-Reply on the inbox. See Decide what to automate.

For the bigger picture of what's flowing through the queue over time, head to your Dashboard.