Journey types, structured intake and public applications

Complete Authority or third party

Identify the authority, provider or external party.

Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicantsPermission: Create staff or public visitorModule v1.0.0
Exact navigationService Journeys form → One-Off Services
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

Identify the authority, provider or external party. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Service Journeys form → One-Off Services.
  2. Go to the One-Off Services intake section containing Authority or third party.
  3. Enter or select Authority or third party using the supported value described below.
  4. Continue to the next step or save the current brief so autosave records the value.
  5. Reopen the brief or review page and confirm the value is shown correctly.

Fields, choices and supported possibilities

Authority or third partyIdentify the authority, provider or external party.

Code-backed validations and workflow rules

  • The field is stored as part of the current request or intake answer set.
  • Leave an optional field blank only when the form permits it; required fields must pass server-side validation.

Expected result and verification

  • The complete authority or third party 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.