Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Six-stage managed-service workflow

Stage 6: Onboarding & Kick-Off

Complete onboarding/kick-off after earlier stages. 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: EditModule v1.0.0
Jump to steps
Where to goAdmin Area → Projects & Work → Service Journeys → Application → Workflow → Complete stage
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

Complete onboarding/kick-off after earlier stages. 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 → Application → Workflow → Complete stage.
  2. Find the record, endpoint, field or action used to stage 6: onboarding & kick-off.
  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

StageStage 6: Onboarding & Kick-Off
Compliance managerRequired for stage 2; hidden/zero for other stages unless the view provides it.
NoteOptional stage evidence.

Rules the system enforces

  • Complete earlier stages first.
  • Stage completion is retained as workflow history.

How to confirm it worked

  • The stage 6: onboarding & kick-off 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.
Stage 5: ProposalSix-stage managed-service workflowBrowse all Service Journeys guidesProjects, tasks and time trackingClient portal overviewCreate a taskUpload and share customer filesConfigure SMTP email deliveryReview email delivery issuesFull Compliance Applications