Everyone sees exactly their part.
A per-role, per-module matrix you adjust from the dashboard, no code involved. Every change lands in the audit log, with who made it and when.
From MX$22 per active unit, VAT included · No contracts
Per role
operational and board, each with its own matrix
Per community
what you change here leaves the others alone
Audited
every change, with who and when
From the role to the matrix, and on to the log
You invite with a role; you adjust what that role may do; everything gets written down.
Invite with a role
Reception, security, maintenance or a board seat: each person comes in with their role's permissions.
Adjust the matrix
Turn each permission on or off per module — view, log, edit, approve — for that community.
It all lands in the log
Every change to the matrix is recorded with who made it, when and what changed.
For the team and for residents
You decide who does what.
Your community's matrix, editable on the spot: one switch per permission and per role.
- Per-role, per-module matrix, editable from the dashboard
- Team rules each community inherits or adjusts
- Nobody can grant a permission they don't hold
Each seat with its own reach.
President, treasurer and secretary come in with what their office requires — and nothing more.
- President: broad read access and approvals
- Treasurer: the community's finances
- Secretary: minutes and announcements
Key features
What a permission does, who holds it and from where.
Editable matrix
One switch per permission and per role, grouped by module. "View" first; the rest unlocks from there.
Board seats by office
President, treasurer and secretary with permissions of their own office, not a generic "board" role.
Scope per community
A collaborator bound to one community never sees the others; and what you adjust here leaves the rest of the team alone.
Every change audited
Who turned on what, when and in which community, in the dashboard's audit log.
What's included, in detail
Every row is a capability that already works today — and how many of the competitors we compare publish it on their site.
| Capability | Published by |
|---|---|
| Gate and front desk with their own permissions | Nobody else publishes it |
| Audit viewer: who did what, and when | Nobody else publishes it |
| What you change in the matrix governs real access | 1 of 6 |
| An editable permission matrix per role | 2 of 6 |
| Board by office: president, treasurer, secretary | 4 of 6 |
“Published by” counts how many of the 6 competitors we compare mention the capability on their own public site. It reads what they say, not how they solve it.
And also
The team sets the rule; the community adjusts it
Each community inherits the team's rules and can change one in particular — the matrix tells you whether a value is inherited or changed here.
No viewing, no editing
Each module unlocks from its read permission; the matrix won't let you turn on "edit" where "view" is off.
Nobody grants what they don't hold
An administrator cannot hand out a permission they don't have themselves, nor widen their own role.
Frequently asked questions
Can I create new roles?
The roles come predefined — administration, reception, security, maintenance, cleaning and the three board seats — but what each one may do is yours to adjust, permission by permission.
Can the board edit data?
It depends on the seat. The president has broad read access and approves; the treasurer runs the community's finances; the secretary keeps minutes and announcements. And those permissions are adjustable from the matrix too.
Can a collaborator see another community?
Only with a seat in it. Data scope is resolved per community: someone bound to one never sees the charges, treasury or visits of the others.
Who can change permissions?
Whoever holds the manage-permissions right in that community. With two limits: they cannot grant what they don't hold, and on their own role they may only remove, never add.
To each their own.
Invite your team with the right role — and adjust the rest from the dashboard.
Start for Free