Britixo CRMBritixo CRM Enterprise Help Centre
Help centreService JourneysUnderstand the absence of Delete permission
Setup, access, permissions and menu badges

Understand the absence of Delete permission

The module registers no Delete capability or hard-delete controller action.

Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicantsPermission: Administrator or authorised staffModule v1.0.0
Exact navigationAdmin Area → Projects & Work → Service Journeys
Before you begin
  • Confirm 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 this guide covers

The module registers no Delete capability or hard-delete controller action. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Admin Area → Projects & Work → Service Journeys.
  2. Locate the record, endpoint, field or action used to understand the absence of delete permission.
  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, choices and supported possibilities

Workspace or endpointAdmin Area → Projects & Work → Service Journeys
PurposeThe module registers no Delete capability or hard-delete controller action.

Code-backed validations and workflow rules

  • 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.

Expected result and verification

  • The understand the absence of delete permission 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.
Understand Edit permissionOpen Service JourneysSetup, access, permissions and menu badgesBrowse all Service Journeys guidesProjects, tasks and time trackingClient portal overviewCreate a taskUpload and share customer filesConfigure SMTP email deliveryReview email delivery issues