Inviting members and understanding roles

People join your community by invitation. Invitations come in two sizes: one at a time, or a whole spreadsheet at once.

Inviting one person

1. In the dashboard sidebar, open Members and select Invite.
2. Enter their email, choose a role (see below), and optionally link them to their property so their address, violations, and account history connect correctly.
3. Select send. They receive a branded email with a link; when they accept, they set a password and land in the right place for their role.

Inviting many people

For a full roster, use Members → Bulk Import. Upload a spreadsheet (CSV) of names, emails, and addresses, review what the import found, and send invitations in a batch. This is the fastest way to bring a whole community aboard.

What the roles mean

• Resident — uses the resident portal: documents, announcements, requests, their own account. Cannot see other residents' private records.
• Committee member — portal access plus a slice of the dashboard, mainly the Architectural review queue.
• Board member — the full working dashboard: violations, financial reports, meetings, documents, announcements, and the AI Workforce.
• Community admin — everything a board member has, plus member management and community settings. Typically the president or the person who set the community up.

A useful rule of thumb: give people the smallest role that lets them do their job, and promote later if needed. Promotions happen from the member's page in Members — open the person and use the promote option.

Good to know

• Invitations expire after a while for security. If someone's link stops working, just send a fresh one — nothing is lost.
• Role changes take effect the next time the person loads the page; there is nothing they need to redo.
• One person can belong to more than one community (a board member who owns in two neighborhoods, for example). They switch between them with the community switcher in the dashboard top bar.
• Behind the scenes, what each role can access is enforced at the database level, not just hidden in the interface — a resident cannot reach board data by guessing a web address.