Britixo CRMBritixo CRM Enterprise Help Centre
Help centreFull Compliance ApplicationsDescribe previous compliance history
Landlord and client portal workflows

Describe previous compliance history

Select Not sure/not applicable, No previous, Continuing existing, Authority already contacted or Previous refused/queried.

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

Select Not sure/not applicable, No previous, Continuing existing, Authority already contacted or Previous refused/queried. 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 → New Application.
  2. Locate the record, setting or action used to describe previous compliance history.
  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 actionSelect Not sure/not applicable, No previous, Continuing existing, Authority already contacted or Previous refused/queried.

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 describe previous compliance history 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.
Choose preferred contact methodExplain urgency or deadlineLandlord and client portal workflowsBrowse all Full Compliance Applications guidesCompliance MonitorReal Estate ManagementClient portal overviewCreate a proposalTrack proposal status and acceptanceAdd and manage customer contacts