Conpago uses roles and permissions to control what staff can see and do in the Admin Dashboard. This keeps villages secure, reduces mistakes, and makes day to day work faster.
How roles work
A role is a permission bundle. It defines:
which modules a staff member can access
what actions they can take inside those modules
which screens and buttons appear for them
Important rules:
Everyone with the same role has the same permissions.
The only difference between two staff members with the same role is which sites they can access.
Example:
A receptionist role can be applied to one receptionist at one village, and another receptionist who covers three villages. The permissions are the same, but site access differs.
What a module is
A module is a major feature area in the dashboard. For example:
Requests
Messaging and broadcasts
Events and facilities
Newsfeed
Documents
Surveys
Tags
Conpago can turn modules on or off per role, and in some cases per site.
Conpago sets up your roles in implementation
During implementation, Conpago will work with your key decision makers to:
map your internal processes
define the roles you need
decide which modules each role should access
confirm any site scope needs for staff who cover multiple villages
You can request new roles or changes later. There is no fixed limit to how many roles you can have.
Site access vs role permissions
Think of Conpago as two layers:
Layer 1: Role permissions
What a person can do.
Layer 2: Site access
Where they can do it.
A staff member can have:
one site access
multi site access (for travelling staff, roving reception, head office roles)
Common role patterns in retirement villages
Here are typical examples of why permissions differ:
A seasonal casual might need access to resident lists and contacts, but not the ability to publish broadcasts or newsfeed articles.
A village manager might need full access to publish content, manage requests, and oversee events and bookings.
A maintenance team leader might need full access to requests and service provider assignment, but not surveys or newsfeed.
Your exact role design should reflect your local operating model.
Retirement offering modules and what they do
This is a plain English guide to the modules referenced in Conpago.
Core operations
Members: resident profiles and core resident data
Contacts: access resident contact information in the dashboard
Emergency contacts: register and manage emergency contacts against residents
Tags: group residents for targeting and filtering
Staff: create and manage staff users, roles, and access
Communication and engagement
Messages: conversations and broadcasts
SMS: allows broadcasts to send SMS, when enabled
Newsfeed: create and publish news articles in the app
Curated content: digital library for images, PDFs, audio, and video
Documents: shared documents and PDFs
Calendar and facilities
Calendar: create and manage events
Custom calendars: create additional calendars beyond the default
Facilities: create facilities and approve or decline bookings
External share: generate shareable links, such as a calendar link for external recipients
Requests and forms
Requests: receive, approve, manage, and report on maintenance and gardening requests, and other request types if configured
Forms: standard forms and connected forms
Connected forms: forms that can be attached to a request workflow to capture consent or extra detail
Surveys: create and manage surveys for residents
Maps and extras
Map: upload a PDF map and make it accessible in the app
Feedback capture: build custom data capture tools that appear as a dedicated button in the app and feed into a dashboard workflow
Vacations: allows residents to submit a vacation request via the app, when enabled
Reporting
Embedded analytics: reporting and analytics tools inside the dashboard, where enabled
Turning modules on or off per site
Conpago can enable or disable modules by site.
Example:
If you operate five villages and one is newly acquired, you might run surveys in four sites and temporarily disable the surveys module in the fifth. It can be re enabled later.
Passwords, deactivation, and lockouts
Depending on your permissions:
Admins or super admins can reset staff passwords
Admins or super admins can deactivate or archive staff who have left
If your only super admin is locked out or has left the business, contact Conpago Support and we will prioritise restoring access.
Service providers: what they are and what they are not
Service providers are used for workflow and reporting.
Key points:
Service providers do not log into Conpago.
They exist so you can assign them to requests and filter and report on external work.
They improve visibility when managing contractors across many requests.
Data import and onboarding
Conpago manages the initial import of your data using a secure import process.
You will be asked to provide data in a specific structure. Conpago can support data clean up and manipulation. Costs may apply depending on your contract.
Admin Dashboard access and devices
The Admin Dashboard works best on a computer or laptop.
It is responsive and can be used on tablet or phone.
There is no separate Admin Dashboard app. Staff access it through a browser using work credentials.
Related articles
Staff roles and permissions (Hub)
How to add a staff member
How to reset a staff password
Multi site overview: what changes for super admins
Protected fields explained: why some edits are blocked
Support ticket checklist