Statuses, timeline and authority progression

Understand landlord-action flags

Recognise statuses that require documents, missing information or an authority-query response from the client.

Audience: Compliance administrators, consultants, landlords and authorised client contactsPermission: ViewModule v1.0.0
Exact navigationAdmin Area → Full Compliance Applications → Case
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

Recognise statuses that require documents, missing information or an authority-query response from the client. 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.
  2. Locate the record, setting or action used to understand landlord-action flags.
  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

WorkspaceAdmin Area → Full Compliance Applications → Case
ActionRecognise statuses that require documents, missing information or an authority-query response from the client.

Code-backed validations and workflow rules

  • Documents requested, More information required and Authority query received are installed as landlord-action statuses.

Expected result and verification

  • The understand landlord-action flags 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.