Completing a Request
Work through a request's tasks, confirm actions across your systems, and close it out — with or without a reply.
Completing a request means working through its tasks until every action across your connected systems is done, then closing it out.
The task list
A request's work is organized into groups by status:
- Needs action — tasks waiting on you.
- Needs manual confirmation — actions on systems that require you to confirm they're done (for example, deleting the user's data in a connected app).
- In progress — automated actions currently running.
- Completed — actions that are finished.
Each task shows the data source and, where relevant, how many user records it found.
[📷 Screenshot: request task groups (Needs manual confirmation) — insert here]
Complete tasks
- Automated tasks run through their integration and move to Completed on their own.
- Manual tasks need you to act in that system, then click Mark as completed on the task — or Mark all as completed to clear a whole group at once.
For a completed task, open its details to see the result — for example, the number of records deleted and the deletion job ID.
[📷 Screenshot: task result details (records deleted / job ID) — insert here]
Assign the work
Use Assignee → Choose to assign the request to a group so the right team handles it.
Close the request
When every task is done, click Close request. MineOS opens a reply to the data subject, prefilled with the right's completion template and the data subject's language. From here you can:
- Send & close request — send the reply and close the request, or
- Close ticket without response — close it without sending an email.
[📷 Screenshot: "Reply to user" close dialog — insert here]
You can also let MineOS run this whole process for you — see Autopilot.
Updated about 17 hours ago