Customer work, connected.

Help & supportMyAccount
Journey types, structured intake and public applications

Complete Current licence status

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Explain the current application/licence position.

Audience: Service delivery staff, compliance managers, administrators, linked client contacts and public applicantsPermission: Create staff or public visitorModule v1.0.0
Jump to steps
Where to goService Journeys form → Property Licensing
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 this guide helps you do

Explain the current application/licence position. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Service Journeys form → Property Licensing.
  2. Go to the Property Licensing intake section containing Current licence status.
  3. Enter or select Current licence status 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 and options

Current licence statusExplain the current application/licence position.

Rules and limits

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

Check it worked

  • The complete current licence status 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page