There are two concepts that might be easily confused - Roles (what you assign capabilities to as an organization) and Unit/Property Relationships (how an individual relates to a specific property - like Owner, Resident, Renter etc)
User Roles in Vlge
Vlge uses Roles to control what each user can see and do through a series of "capabilities." This is really a slightly more specific use of the "permissions" concept. A user can have multiple Roles at the same time and the system grants the max capabilities (when considering these roles) available at any one time.
Roles may also be useful as filters for systems like Messaging (e.g. send email to all users with "Admin" in their Roles).
Default Roles
Role | Description | Typical Permissions |
Resident | Property owner or occupant | Submit ACC requests, view documents, participate in elections |
Board Member | Elected board member | Everything Resident can do, plus view board reports |
Admin | Community administrator | Manage users, ACC requests, violations, messaging |
Super Admin | Full access administrator | All permissions including billing and settings |
ACC Reviewer | Architectural committee member | Review and vote on ACC requests |
Renter | Tenant (non-owner) | Limited access based on community settings |
👉 See Roles & Permissions in the General Settings
🔑 Here is an example of a setup using solely System role defaults
🔑 When you click edit on any role you will see all available capabilities
👉 Most Resident or Owner capabilities will be found lower in the page in "Personal & property"
Note the Quick Reference at the top right to help you understand each capability.
⚡️ Per Person overrides
You can also grant a single individual an override capability in their Person detail page (All People, find the person, click their name)
Role Requirements
Resident Role: To be assigned the Resident role, a user must have an address associated with their account. This ensures voting and other resident-specific features work correctly.
Multiple Roles
Users can have multiple roles. For example, a board member who is also a resident would have both "Resident" and "Board Member" roles, giving them access to both sets of features.
Role Assignment
Roles are assigned by administrators. If you believe your role is incorrect, contact your community administrator.
👉 Unit or Property Relationships
A Unit or Property Relationship is how a person is connected to one specific property. It answers a different question from a role: Who is this person to this lot or unit?
You set it on the person, under Associated Units (All People > open the person > below Profile Info). The same person can have a different relationship on each property they are tied to. A landlord might be Owner on one lot and have no relationship at all on the home they live in somewhere else.
These are the relationships Vlge starts with. Your community can rename the label (for example, “Designated Contact” can display as “Property Manager”). The rename changes the words on screen. It does not change what the relationship does.
Relationship | Plain meaning |
Owner-Occupant | Owns the property and lives there |
Owner / Lot Owner | Owns the property and lives somewhere else |
Guest Occupant | Lives there and is not an owner (family member, roommate) |
Renter | Tenant on a lease |
Caretaker | On-site person who needs to act for the unit in the portal |
Designated Contact | A contact for the property who does not live there |
Guest | A short-term visitor |
For the full list of what each one creates, who it emails, and which role it assigns by default, see this article.
🔎 What a unit relationship decides
Attaching someone to a property is what puts that property on their account. It also decides which side of the property they sit on: owner or occupant.
Owners receive assessments, invoices, violation and legal notices, and governance mail. Voting follows ownership. Only an owner can be the primary contact for the unit.
Occupants (renters, guest occupants, caretakers, designated contacts, guests) live at the property or are listed on it. They are included in emergency alerts along with the owners. They do not replace the owner on billing, legal notices, or the ballot.
Owner-Occupant is both. That person is on the owner list and the occupant list for that property.
Ending the relationship takes the person off that property. Their other roles in the community stay in place.
👉 A relationship can hand someone a role. That is a convenience.
When you add a relationship, Vlge can also assign an organization role, using the mapping under General Settings → Roles and Permissions → Unit Relationship Defaults. Owner-Occupant, for example, assigns Resident. Renter assigns the Renter role. Designated Contact and Guest assign no role unless you set one.
You can change that mapping, and you can still add or remove roles on the person afterward. Changing their roles leaves the property connection as it is.
One role stays tied to the property itself. Anyone with a current ownership record also receives the Owner role, and Vlge removes that role when the ownership ends. That sync follows the ownership record, separate from the defaults table.
Roles and unit relationships side by side
Use both. They answer two questions, and a person often needs an answer to each.
| Unit relationship | Role |
Question | Who is this person to this property? | What can this person see and do in the community? |
Scope | One property at a time | The whole organization |
Examples | Owner-Occupant, Renter, Caretaker | Resident, Board Member, Admin, ACC Reviewer |
Where you edit it | The person’s Associated Units | The person’s Roles, and General Settings → Roles and Permissions |
What it drives | Which property is theirs, who is billed, who votes, who gets legal mail and emergency alerts | Capabilities: screens, actions, and who a message can be filtered to |
A person can have several roles at once. Vlge grants the capabilities from all of them using the most permissive. A person can also have several unit relationships at once, one per property, and those can differ.
👀 Some words appear in both places.
Resident is a role.
Living at the property is a relationship.
Renter is both a relationship (this person leases this unit) and a role (the capabilities that come with that).
Owner on Associated Units means this person is an owner of that property.
The Owner "Role" is the set of owner capabilities Vlge keeps in sync with that ownership. (This is the one that can be most confusing)
💡 Three people, so the split is obvious
🙎🏻 Jordan lives at 12 Oak and serves on the board.
Associated Units: Owner-Occupant on 12 Oak.
Roles: Resident, Owner, and Board Member.
The relationship is why 12 Oak, the balance, and the ballot belong to Jordan. Board Member is why Jordan can open board reports. Remove Board Member and the home stays. End the ownership and the home comes off Jordan’s account, even if Board Member is still assigned.
🙍🏽♂️ Sam owns 4 Pine and leases it to Alex. Sam is Owner / Lot Owner on 4 Pine. Assessments, legal notices, and the vote go to Sam. Alex is Renter on the same property: Alex lives there, gets emergency alerts, and uses the renter portal. Alex does not get Sam’s invoice.
🙍🏼♀️ Priya runs the community office and does not own a lot. Priya’s role is Admin. Priya has no unit relationship. Priya can manage people, requests, and settings. Priya is not on a property, does not get a ballot, and does not receive assessment mail.
👉 Where this shows up on a person
On the person page, Associated Units is the property connection. Roles, just above or beside it, is what they can do in the organization. Set the relationship for the property. Set the role for access. If the defaults already assigned the right role when you added the relationship, leave it.
Two narrower controls sit beside this, and they are separate from both:
A capability override on one person, from that person’s page, adds or removes a single capability without changing their role. See the override section above.
For a non-owner on a specific property, ACC access and notice access can be turned on from the property’s Resident Access section. See Property Level User Permissions.
🛟 Need more help? Just ask!






