Britixo CRMBritixo CRM Enterprise Help Centre
Help centreFull Compliance ApplicationsOpen the client portal workspace
Setup, access, permissions and module structure

Open the client portal workspace

Use the Full Compliance Applications link added to the authenticated client navigation.

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

Use the Full Compliance Applications link added to the authenticated client navigation. 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 open the client portal workspace.
  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

WorkspaceClients Area → Full Compliance Applications
ActionUse the Full Compliance Applications link added to the authenticated client navigation.

Code-backed validations and workflow rules

  • The action is available only when the supplied module exposes it and the signed-in user has the required module and core CRM access.
  • Hidden helpers and internal background methods are documented under the user-facing workflow they support rather than presented as separate menu pages.

Expected result and verification

  • The open the client portal workspace 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.
Open the administrator workspaceUnderstand client portal routingSetup, access, permissions and module structureBrowse all Full Compliance Applications guidesCompliance MonitorReal Estate ManagementClient portal overviewCreate a proposalTrack proposal status and acceptanceAdd and manage customer contacts