Community settings for boards and admins
The six settings tabs — general, financial, notifications, AI, access, and privacy.
Community-wide configuration lives in the dashboard: open Settings at the bottom of the sidebar. Settings are organized into six tabs.
General
Your community's identity: name, address, unit count, year established, management type, website — plus branding: upload a logo and pick a primary color, and the portal and dashboard chrome adopt it. This is also where your community's Georgia legal posture lives, including the POA Act election recorded during setup; keep it accurate, because late-fee caps and collection rules key off it. This is general information, not legal advice — consult an attorney for your specific situation.
Financial
Community financial configuration — dues schedule basics and related records. Note the honest boundary: configuration here feeds the records system today; automated invoicing and online payments arrive with the payments launch.
Notifications
The community-wide defaults for how members are notified per event type (announcements, meetings, violations, and so on). Portal and email are the selectable channels in V1; SMS and postal appear in the matrix but are reserved for a later release — the interface says so rather than pretending they send. Announcement email specifically begins delivering after your email domain verification completes; the portal channel carries announcements in the meantime.
AI
How the AI presents itself in your community: the AI disclosure setting (whether chats carry an "AI-assisted" note) and response style. Supervision — how much human review each agent's work requires — is configured separately under AI Workforce → Supervision Settings, close to the inbox where you review drafts.
Access
Member access control: see everyone's role and status, reactivate inactive members, and manage who can do what. Role changes here are the administrative complement to the invitation flow.
Privacy
Community-level privacy posture for the directory and member data — the defaults residents inherit before they adjust their own switches in the portal.
Who can change what
Board members can view settings; changing them is for community admins — deliberately, since branding, financial configuration, and access control affect everyone. Every settings change writes to the audit log, so "who changed the late-fee grace period, and when" always has an answer.
Was this article helpful?