Landlord and client portal workflows

Use the Full Compliance Applications client portal

View owned cases and start a new authenticated application.

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

View owned cases and start a new authenticated application. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Open Clients Area → Full Compliance Applications.
  2. Locate the record, setting or action used to use the full compliance applications client portal.
  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

Client portal actionView owned cases and start a new authenticated application.

Code-backed validations and workflow rules

  • The authenticated customer must own the application.
  • Only landlord-visible timeline and document information is returned.

Expected result and verification

  • The use the full compliance applications client portal 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.