Security, data storage and audit

Protect agreement countersign tokens

Send countersign links only to the intended landlord/signatory.

Audience: CRM staffPermission: Authorised reviewerModule v1.0.0

Exact navigationOnboarding workspace → Landlord Countersign

Before you begin

Use an account with Authorised reviewer 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

Send countersign links only to the intended landlord/signatory. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

Open Onboarding workspace → Landlord Countersign.
Select the exact record or option described in this guide.
Complete the displayed fields or action using the rules below.
Save or submit once and resolve any validation response.
Verify the resulting record, status, file, notification or integration effect.

Fields, choices and supported possibilities

Exact actionProtect agreement countersign tokens

Exact navigationOnboarding workspace → Landlord Countersign

Module version1.0.0

Access ruleAuthorised reviewer

VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.

Code-backed validations and workflow rules

The public controller validates onboarding ID and token.

Expected result and verification

The supported protect agreement countersign tokens 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.