Quick map
Site: A Village
Staff: Dashboard users who manage the village
Resident: Occasionally referred to as a Member is someone who lives at the Site.
Address: The resident's Unit/Villa/Apartment Number
Tags: Groups used for targeting and filtering
Site
A site is a single retirement village. Most settings and content are site based:
staff access
residents (members)
broadcasts and channels
events and facilities
requests
documents and newsfeed
If you are a super admin, you can operate across multiple sites. Always confirm which site you are working in before saving changes.
Admins
Are the Staff are the people who log into the Admin Dashboard.
Key points:
controlled by roles and permissions
usually limited to one site, unless multi site access is assigned
actions appear in activity logs in requests and feedback workflows
Common staff workflows:
create residents
send broadcasts
approve facility bookings
manage requests
publish content
export data
Resident
A Resident is a the profile of whoever lives at the village. Important behaviours:
Residents exist by virtue of the data Conpago is provided in the import, or added by your team, even if they never download the app
The resident profile is the source of truth for contact details used for email and SMS escalation
Residents can be invited and later become logged in app users
You manage:
name and contact details
address and unit
tags
privacy settings
Mobile, Email, Home Ph. and Unit # being visible in the resident's digital phone book.
Address
An address is linked to a resident (or two) and used across the platform.
Where it matters:
Requests default location often uses the resident address.
It improves operational clarity for staff.
Practical tip:
If a job is in a common area, override the request location rather than relying on the resident address.
Tags
Tags group residents for targeting and filtering.
You can use tags to:
target broadcasts
target surveys
Segment resident lists
Examples:
Stage 3
Building A
Street Name
Pet owners
Social club
Committee
Practical rule:
Targeting is only as accurate as tagging.
How these objects connect
Use this mental model:
A site contains staff and members.
A member can have an address, Requests, and tags.
Requests attach to a member and default location from the address unless overridden.
Broadcasts, events, and content are scoped to a site, then targeted using tags or roles.
Only exception is a "provider wide" class of data which is across the entire portfolio of villages.
If something feels wrong, check these first
Correct site selected
Correct Admin with the appropriate permissions is undertaking the task
Resident contact details are accurate
Resident address is correct
Tags are applied consistently
Related articles
Tags explained and best practice
How to create a request on behalf of a resident