A resident reaches the Chainels resident portal through an invitation from Chainels. Their place in the app comes from their booking in Lavanda.
Chainels is a third-party application and every setup is configured separately, so what is available to your organisation may differ from what is described here. Confirm the detail with your Lavanda contact.
Before you begin
The resident has a confirmed booking with an email address recorded against them.
The building has been connected to Chainels.
You are a community manager in Chainels if you need to resend an invitation.
What you need to know
Chainels sends the invitation, not Lavanda. No email from the PMS carries the sign-up link.
The resident sets their own password and completes their profile in Chainels.
Access follows the booking. When the booking ends, access normally ends with it.
A community manager can send a password reset link to a resident who cannot get in.
When a resident says they have no access, check the booking first. A missing or incorrect email address is the most common cause, and it is fixed in Lavanda rather than in Chainels.
When would you use it
A resident has moved in and cannot get into the app.
You are chasing sign-ups before a building opens.
A resident has changed their email address.
Things to note
Changing an email address in Lavanda does not move an existing Chainels account to the new address. Update it in Chainels as well.
Whether access ends immediately at checkout, and whether a resident is warned, depends on how your setup is configured.
Company contacts held in Lavanda for invoicing are not normally given app access. A community manager adds them by hand where they need it.
Lavanda Support cannot resend a Chainels invitation. That is a community manager action in Chainels.