Data-subject rights across many systems
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
handle access, correction, and erasure requests across platform, ERP, and CRM.
Planned topics
- Rights include access, correction, and erasure (the exact set and deadlines depend on the law; verify with legal).
- You need a data map: where one person's data lives and which system is the master.
- Design one request workflow that fans out to every system and collects confirmations.
- Some data must stay (tax records); erasure becomes restriction or anonymization with a recorded reason.
Draft outline details
Demonstration
a flow: request → identity check → lookup by customer ID across systems → fan-out tasks → confirmation → response and audit record.
Check your understanding
A customer asks for erasure but an invoice must be kept for tax. What happens?
Show answer
Keep the legally required record, minimize and restrict it, erase the rest, and tell the customer.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.