Review and fulfill a data request (DSR)

Use the data-request queue to check a request’s deadline and status. An export is meant to run automatically once the member confirms the request from an emailed link, but that confirmation email isn’t sent today, so an export request stays at Pending (its panel shows Not yet verified) and no file is prepared. A deletion needs an authorized admin to complete it.

Who can do this: Admins allowed to view data requests can open the queue and cases. Completing or rejecting a deletion also requires permission to make data-request decisions for that member. The review-policy setting and legal holds have separate permissions. If DSR queue is missing, ask an Org Owner about your access.

Before you start

Three dates apply to a request, and only one of them is the legal deadline. The queue column and its badge show the 45-day response deadline — the legal one. An overdue request stays visible. The request panel also shows a 30-day response target: this is the promise the member is given when they submit (“we will complete or respond within 30 days”). Both dates are counted from the same submission date — the legal one 45 days after it, this target 30 days after it — so the target is not a separate deadline anyone sets or the system tracks on its own, and it always sits inside the 45-day deadline. The 30-day target can pass while the 45-day deadline still has time left. That is normal: the badge stays the colour the legal deadline says, and the request does not become overdue. You cannot change the 30-day target from this screen. Separately, the deletion panel describes a future 30-day grace period after approval; it is informational, and anonymization currently runs as soon as an approval succeeds.
Exports show generation and delivery status only. There is no admin approval or rejection for an export.
On a deletion, the preview lists the records it covers and any open obligations. It describes possible changes, not a complete list of this member’s data; some areas and stored files are not shown. Read How account deletion (anonymize-all) works before approving, especially if you need to explain what may remain.

Steps

Go to DSR queue (the Data requests page, at /admin/admin-security/privacy/dsr).
If needed, use Filter by type or Filter by status. Open requests nearest their deadline appear first. The current queue can still list requests across the organization; it does not yet filter its list to your member assignments.
Select Review on an open request. Select View on a completed, rejected, or expired request to inspect its status and audit.

Export requests

The export panel shows when the member confirmed their email and whether the automatic export was generated and delivered. It does not show the archive contents or offer an admin decision. Use Review while it is open or View after it reaches a final status.

Deletion requests

Deletions always need an admin decision. If up-front review is on, the request waits for your approval before the member re-verifies. If it is off, the member re-verifies first, and an admin still completes the deletion.

Read the What will be anonymized preview and its open-obligations list. Entries marked as blocking must be resolved before approval; other entries are informational.
For each blocking item, follow its billing link.
Resolve the item on the linked billing page.
Return to the deletion request.
Reopen or refresh the preview. Check that no blocking items remain. Approve & anonymize stays unavailable until the preview loads and blocking items are cleared.
Select Approve & anonymize.
If you want an optional audit note, enter it in Add a note for the audit trail on the confirmation.
Select Confirm to submit the decision.

Only if that submission asks you to sign in again, follow these steps. If the request is Fulfilled, stop here.

Complete the sign-in challenge. The earlier submission was refused.
On return, reopen the request and preview to check the latest status and obligations. The trip to sign-in may have cleared the form.
If the deletion is still eligible, re-enter any optional audit note you want to keep.
Select Confirm to submit a new decision. Completing the challenge alone does not anonymize the account.

Turn on admin review for every deletion request (optional)

At the top of the queue, use the Require admin review on deletion switch to change the setting. Turning it on saves automatically and shows Deletion-review policy updated.
If turning it off, select Turn off in the confirmation dialog. Future requests go to member re-verification first; an admin still completes them. In read-only mode, this setting cannot be changed.

Place a legal hold on a member (optional)

If your role permits it, select Place legal hold from the member’s deletion request. The hold blocks future deletion requests; it does not close one already in progress.
If prompted, enter an optional reason for the admin audit.
Submit the hold action.

Only if that submission asks you to re-authenticate, follow these recovery steps. The earlier hold submission was refused.

Complete the sign-in challenge.
On return, check the hold’s current state.
If the hold is still needed, re-enter any lost audit reason.
Submit the hold action anew if it is still needed.

After an accepted hold action, check that the hold was placed. Check the open deletion request’s status separately; placing a hold alone does not reject it. If you intend to deny the open request, follow Deny a deletion request with a reason and choose a currently available reason.

To remove a hold, select Clear legal hold, then check that it cleared. These hold controls are unavailable while the organization is read-only.

Verify

You’ll know an approved deletion is complete when its status changes to Fulfilled. For a legal hold, check both the hold’s current state and the deletion request’s status; they change separately. Export requests would reach Fulfilled through the automatic worker after the member confirms; because the confirmation email isn’t sent, they stay at Pending today. The admin queue shows their status without an approve action.

If something goes wrong

“This request was already resolved — refresh to see the latest status” — refresh before making another decision.
“Close {N} obligation(s) before anonymization can run” — follow each blocking item’s billing link, resolve it there, then return and reopen or refresh the preview before trying approval. Other listed items are informational.
“This member is under a legal hold, so the deletion can’t run.” — this appears after you confirm, even when the preview looked clear: the hold is checked again at the moment you approve, so one placed after the request arrived still stops it. Nothing was deleted or changed. Reopen the request to see its current state. The message does not say why the hold is there, and the queue will not tell you. Clear the hold first if that is the right call, then decide again — do not keep pressing Confirm.
“Close this member’s open obligations before the deletion can run.” — this also appears after you confirm, even when the preview showed nothing blocking: the preview and the approval are two separate checks at two different moments. Nothing was deleted or changed. Settle, refund, or cancel the open item on the billing page the message links to, then reopen or refresh the preview before deciding again.
The preview cannot load — select Try again. Approval remains unavailable until it loads.
You need to reject a deletion — see Deny a deletion request with a reason.
“Could not load data requests.” — select Try again.
A direct link gives 403 or 404 — a 403 may mean that case or action is outside your member access; a 404 means the request was not found or belongs to another organization. Ask an Org Owner about your access if needed. Access to your own member request does not grant access to the admin queue.