Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Stored data, audit continuity and security

Protect personal data

Contact details, messages and documents require least privilege and retention governance. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicantsPermission: View or AdministratorModule v1.0.0
Jump to steps
Where to goAdmin Area → Projects & Work → Service Journeys
Before you start
  • Verify the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What you’ll accomplish

Contact details, messages and documents require least privilege and retention governance. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Admin Area → Projects & Work → Service Journeys.
  2. Find the record, endpoint, field or action used to protect personal data.
  3. Complete the displayed values exactly as described in this guide.
  4. Select the available save, submit, send, upload, create, update or confirm action.
  5. Return to the related register, portal, activity log or API response and verify the expected result.

Fields and options to review

Workspace or endpointAdmin Area → Projects & Work → Service Journeys
PurposeContact details, messages and documents require least privilege and retention governance.

Rules the system enforces

  • The action is available only where the supplied module exposes it and the signed-in user or API client meets the stated access conditions.
  • Internal helpers are documented under the visible workflow or endpoint they support rather than presented as invented menu pages.

How to confirm it worked

  • The protect personal data workflow completes without a validation, permission, ownership or availability error.
  • The related record, portal view, activity entry, notification log or API response shows the expected state.
  • Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.

Security, privacy and operational checks

  • Use controlled test records and non-production credentials before wider rollout.
  • Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.
Protect internal notesPreserve audit continuity on deactivationStored data, audit continuity and securityBrowse all Service Journeys guidesProjects, tasks and time trackingClient portal overviewCreate a taskUpload and share customer filesConfigure SMTP email deliveryReview email delivery issues