Public tenant applications and invites

Send a tenant application invitation

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 choose property, recipient name/email, invite mode and personal message.

Audience: CRM staffPermission: Authorised application reviewerModule v1.0.0

Jump to steps

Where to goAdmin Area → Requests & Applications → Tenant Applications → Send Invite

Before you start

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

Choose property, recipient name/email, invite mode and personal message. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

Go to Admin Area → Requests & Applications → Tenant Applications → Send Invite.
Go to the source record and verify its recipient, status, totals and attachments.
Select the Send, Email, Share or Request action described in the guide.
Select recipients and attachment/signature options shown by the form.
Submit once and verify the activity, delivery metadata, public link or approval request created by the module.

Fields and options

Exact actionSend a tenant application invitation

Exact navigationAdmin Area → Requests & Applications → Tenant Applications → Send Invite

Module version1.0.0

Access ruleAuthorised application reviewer

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.

Rules and limits

The module stores invite records/tokens and default TTL is 14 days.
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.

Check it worked

The supported send a tenant application invitation 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.

Was this guide useful?Your response is stored only in this browser.