Statuses, timeline and authority progression

Use status: Compliance submission sent to authority

The submission has been sent to the relevant authority.

Audience: Compliance administrators, consultants, landlords and authorised client contactsPermission: EditModule v1.0.0
Exact navigationAdmin Area → Full Compliance Applications → Case → Update status
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 submission has been sent to the relevant authority. 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 → Full Compliance Applications → Case → Update status.
  2. Locate the record, setting or action used to use status: compliance submission sent to authority.
  3. Complete the displayed fields or controls exactly as described in this guide.
  4. Select the available save, submit, update, call, sign, upload or confirm action.
  5. Return to the related register, portal, dashboard or call panel and verify the recorded result.

Fields, choices and supported possibilities

StatusCompliance submission sent to authority
Status noteExplain the specific update for this case.

Code-backed validations and workflow rules

  • The visible label is “Compliance submission sent to authority”.
  • The status is visible to the landlord.
  • Applying this status records the submitted-to-authority timestamp.

Expected result and verification

  • The use status: compliance submission sent to authority workflow completes without a validation, permission or availability error.
  • The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
  • Any client-visible or public result appears only where the code explicitly allows it.

Security, privacy and operational checks

  • Use a controlled test case, contact, extension or website origin before production rollout.
  • Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.