Appearance
Data privacy
ComplianceData privacyPermission:
compliance.privacy.vieworcompliance.dsr.viewOpen in Roari ERP (new tab)Also known as
- PII inventory
- personal data inventory
- ROPA
- record of processing activities
- data map
- data protection
- GDPR
- PDPL
- lawful basis
- sensitive data
The PII inventory records which fields of which records hold personal data, why you process them, on what lawful basis, how long you keep them and whether they can be erased on request. Data protection officers maintain it; it also drives what a data subject access request returns. The Consents and Data subject requests tabs of the same area are described on their own pages.
Read the inventory
- Go to ComplianceData privacy. The PII inventory tab opens.
- The tiles at the top show, per record type, the number of personal-data fields, how many are high or special sensitivity and how many are erasable.
- Filter the list by Record type, Sensitivity, Category, Lawful basis or Erasable.
Add a personal-data field
Permission:compliance.privacy.manage- Select Add field.
- Fill in the dialog (see the table) and select Save field.
To change a field, select the pencil icon on its row; Record type and Field cannot be changed. To remove one, select the bin icon and Remove field: the field leaves the inventory, no data is deleted.
| Field | What to enter | Required / default |
|---|---|---|
| Record type | The record that holds the data, such as customers or employees. | Yes |
| Field | The field name, such as email or bank_account. | Yes |
| Label | A readable name shown in the list. | No |
| Owning module | The module that owns the record, such as finance or hr. | Default core |
| Category | Identifier, Contact, Financial, Government id, Employment, Health, Biometric, Location, Online or Other. | Yes, default Identifier |
| Sensitivity | Low, Medium, High or Special (special category data such as health or biometrics). | Yes, default Medium |
| Lawful basis | Consent, Contract, Legal obligation, Vital interests, Public task or Legitimate interests. | Yes, default Contract |
| Retention policy | The retention policy that limits how long the data is kept. | No |
| Erasable on request | On when the data can be erased for an erasure request. | Default on |
| Anonymisation | How the value is erased: Mask, Hash, Fixed (a fixed value) or Null (emptied). | Yes, default Mask |
| Purpose | Why the data is processed, such as "Salary payments". | No |
| Notes | Anything else, such as the processor or the transfer country. | No |
Data privacy tabs
| Tab | Page |
|---|---|
| PII inventory | This page. |
| Consents | Consents |
| Data subject requests | Data subject requests |
Differences by role
- Permission:
compliance.privacy.viewshows the inventory and consents;Permission:compliance.privacy.manageadds, edits and removes fields and records consents. - Users with only Permission:
compliance.dsr.viewsee the area for its Data subject requests tab.
Related
- Data subject requests
- Consents
- Retention policies
- Data retention: the platform's own retention settings
- Incidents: report a personal data breach
- Custom fields
