Protect agreement countersign tokens | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/protect-agreement-countersign-tokens Publisher: Pixie Technologies LLC Security, data storage and audit Protect agreement countersign tokens Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Follow this guide to send countersign links only to the intended landlord/signatory. Audience: CRM staff; Permission: Authorised reviewer; Module v1.0.0; Where to goOnboarding workspace → Landlord Countersign Before you start - 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 helps you do 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. Follow these steps - Go to 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. - Check the resulting record, status, file, notification or integration effect. Fields and options 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. Rules and limits - The public controller validates onboarding ID and token. Check it worked - 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. Related guides Protect public application tokens (https://pixiecrm.com/help-centre/protect-public-application-tokens)Protect renter identity and income evidence (https://pixiecrm.com/help-centre/protect-renter-identity-and-income-evidence)Apply least privilege to Real Estate Management (https://pixiecrm.com/help-centre/apply-least-privilege-to-real-estate-management)Review Real Estate email templates (https://pixiecrm.com/help-centre/review-real-estate-email-templates)Troubleshoot Real Estate activation (https://pixiecrm.com/help-centre/troubleshoot-real-estate-activation)Browse all Real Estate Management guides (https://pixiecrm.com/help-centre/category/real-estate-management)Customers Contacts (https://pixiecrm.com/help-centre/category/customers-contacts)Contracts Documents (https://pixiecrm.com/help-centre/category/contracts-documents)Invoices Payments (https://pixiecrm.com/help-centre/category/invoices-payments)