Edit agreement body HTML
Review/update agreement_body_html through the supported workflow form.
Exact navigationOnboarding workspace → Agreement
Before you begin
- Use an account with Authorised tenant/rent staff 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
Review/update agreement_body_html through the supported workflow form. 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 → Agreement.
- Open the intended record from the list or preview.
- Choose Edit and change only the required fields.
- Save once and resolve any validation or permission message.
- Reopen the record and verify the update, status and audit/activity evidence.
Fields, choices and supported possibilities
Exact actionEdit agreement body HTML
Exact navigationOnboarding workspace → Agreement
Module version1.0.0
Access ruleAuthorised tenant/rent staff
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Tenant/applicantIdentity, contact, current address, employment/income, occupants, pets, smoker/benefits/children flags and right-to-rent data where exposed.
Tenancy termsProperty, tenant client, start/end/move-in dates, term, rent, frequency, deposit, holding deposit and deposit scheme.
Consent and workflowInvite mode, consents, review notes, agreement template/body, signature stage and workflow action.
Code-backed validations and workflow rules
- Do not insert unsafe scripts or unapproved legal text.
- Public application and onboarding actions use token/record checks and explicit workflow states.
- Do not advance a workflow until the required party, property, dates, financial terms and consent/evidence are complete.
Expected result and verification
- The supported edit agreement body html 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.