Property owners, landlords and client links

Create a landlord CRM customer

Create the customer/contact record required for landlord linking and portal use.

Audience: CRM staffPermission: Customers: CreateModule v1.0.0
Exact navigationAdmin Area → Customers → New Customer
Before you begin
  • Use an account with Customers: Create 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 this guide covers

Create the customer/contact record required for landlord linking and portal use. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

  1. Open Admin Area → Customers → New Customer.
  2. Choose the New, Add, Create or Start action exposed on that screen.
  3. Complete the required fields described below and review any linked record, currency, tax, approval or recipient selection.
  4. Save or submit the form once; correct any validation message rather than bypassing it.
  5. Open the resulting record and verify its number, status, totals, files, activity and downstream links.

Fields, choices and supported possibilities

Exact actionCreate a landlord CRM customer
Exact navigationAdmin Area → Customers → New Customer
Module version1.0.0
Access ruleCustomers: Create
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Property ownership and listingConfirm the property owner/landlord, estate-agent company, listing type, transaction type, privacy and status before saving.
Address and mapComplete address, city, country and latitude/longitude where the map is used.
Commercial valuesReview price/rent, commission, fees, income/expense values, currency context and availability dates.
Organisation/personName, code, email, phone, website, tax/VAT, address, status and profile image where exposed.
Access and structurePlan, role, administrator flag, departments, staff type/company link, approval-manager and public flags where applicable.

Code-backed validations and workflow rules

  • Complete company/name, primary contact, email, phone, address and portal access as required.
  • Property visibility and actions are controlled by real_property view-own/view/create/edit/delete capabilities.
  • Property status, account status and approval workspaces are separate from the main listing form.
  • Company, owner, broker and staff records use different capability groups and ownership checks.
  • Email-exists checks prevent duplicate staff/company identities in supported forms.

Expected result and verification

  • The supported create a landlord crm customer 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.