At a glance
- Record the request as "A team member" in Admin, Privacy, Requests; the same legal deadlines apply.
- Their work stays with the workspace. Erasing a team member removes the person, not the business's records.
- A copy for a team member holds their own records in full, and only the fields about them from the workspace's records.
- Only the workspace owner handles a request about an admin, and the owner is never erased while they are the owner.
Before you start
- Who can do it
- Anyone given "Handle privacy requests" can record the request. An admin searches, copies, corrects, restricts and erases.
- Where it is
- Admin, Privacy, Requests, New request, then choose "A team member".
- Before erasing
- Remove the person from the team first: Admin, People, their name, Remove. Their records are handed to someone else and their sign-in is turned off.
Why team members are different
A team member's data is mixed with the business's records: they created the deal, logged the call, issued the invoice. Leading business systems such as Salesforce and Microsoft 365 take the same approach Moirova does: the work stays, the person goes.
Record the request
- Start a request. In Admin, Privacy, Requests, choose New request, then "A team member", and pick the person - current or former.
- Say what they asked for. See their data, correct it, stop using it for now, or delete it. The deadline is set from where they live, as for a contact.
- Check who is asking. Record how you confirmed it is them. The copy, the correction, the restriction and the erasure all wait for this step.
- Answer and close. Use the tool for the request, then close it as answered. Every step is kept in the request's log.
What each tool does for a team member
| Tool | What it does |
|---|---|
| Find | Every place that holds their data: their person record, sign-in history, AI analysis of their work, briefings and notifications, and every workspace record that names them. Never another workspace's records. |
| Copy | Two files: their own records in full, and from the workspace's records only the fields about them, such as who made it and their name. Never your clients' details or amounts, never a saved password. Only after the identity check. |
| Restrict | They are left out of AI analysis of the team, and their stored analysis is deleted, until an admin lifts it with a reason. |
| Correct | Their name on their person record, their sign-in and the copies other records keep. The audit trail, the privacy register, the activity history and issued invoices keep the name they were made with. |
| Erase | See below. |
Erasing a team member
- Deleted: their sign-in history, AI analysis of their work, briefings, notifications, their sign-in account (email, password, two-step) and their saved mailbox passwords.
- Kept, without their name: deals, invoices, activities, files, payments and the audit trail. Records show "Former team member" where their name was.
- Their person record stays only as an empty stub - role, who took over their work, the terms they accepted - so the workspace's history still adds up.
- Never changed: another workspace's records, other people's records and the email messages themselves.
As with a contact, a second admin approves the check when the workspace has two or more admins, the admin who erases types the request's reference, and the erasure finishes even if the page closes. An erased person can never be turned back on, given a role or brought back by a restore.
Requests about admins and the owner
Every workspace has one owner, an admin with the final say. A request about an admin is searched, copied, restricted, corrected or erased only by the owner; another admin can be the second admin who approves an erasure. The owner is never erased while they are the owner - they hand the workspace to another admin first.
Nobody changes or erases their own data through these tools. Anyone can download their own copy, the owner included.
Tip
When another team member has the same name, records that show only the name are not changed. The check says so, so you can review them by hand.
Limits to know
Notes and emails that other people wrote and that mention the person by name are not searched. Usage counters expire on their own, and system logs, kept for 30 days, hold no names.

