#5667 - Document / inform of new catalogue field setting "May contain personal information"
| Identifier | #5667 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Document / inform of new catalogue field setting "May contain personal information" |
| Status | Open |
| Tags |
Roadmap: v11 final phase (custom) Type: Legal compliance / Privacy (custom) |
| Handling member | Deleted |
| Addon | General / Uncategorised |
| Description | For upgrade notes in v11, we should make clear that there is a new catalogue field setting called "May contain personal information".
Instruct users upgrading to v11 that it is their personal and legal responsibility to manually review all their catalogues' fields (Content > Catalogues > Edit Catalogue, and review every field on every catalogue). And they should tick this new setting for all fields which may contain personal information or sensitive data. Document that this setting ties into the privacy system and that any fields with this setting ticked will be anonymised / purged as necessary when a member requests the purging / anonymisation of their data. By default, all catalogue fields transitioned from v10 to v11 will have this option disabled, so a manual review is necessary. Note that this process does not apply for custom profile fields; all CPFs are automatically treated as sensitive, and this cannot be turned off as they are tied into member profiles (which are sensitive by nature). However, it DOES also apply to custom fields added to content (e.g. custom fields on calendars). So webmasters also have to review those as well. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
There have been no comments yet