Email, PDF branding and integrations

Use CRM customer-profile tabs

Follow this guide to open property links, landlord/supplier payouts and related module tabs. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM staffPermission: Customers: ViewModule v1.0.0
Jump to steps
Where to goAdmin Area → Customers → open customer
Before you start
  • Use an account with Customers: View and confirm the intended record or setting before making a change.
  • Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
  • Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What you’ll accomplish

Open property links, landlord/supplier payouts and related module tabs. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Admin Area → Customers → open customer.
  2. Select the relevant record, filter, report, model or configuration described below.
  3. Use the displayed action or read the current values without altering unrelated data.
  4. Compare the output with the code-backed rules and expected result in this guide.
  5. Record or correct any mismatch before relying on the output in production.

Fields and options to review

Exact actionUse CRM customer-profile tabs
Exact navigationAdmin Area → Customers → open customer
Module version1.0.0
Access ruleCustomers: View
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.

Rules the system enforces

  • The module adds tabs through hooks; each tab applies its own record scoping.

How to confirm it worked

  • The supported use crm customer-profile tabs flow completes without bypassing permission or validation checks.
  • The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
  • Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

  • Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
  • Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
  • Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
  • Test settings and automated jobs with controlled records before production-wide use.