Community experience
How MyCommons works for your community
A clear path from roster and invitations to verified membership—then the tools residents and board leaders use every day. Built for HOAs, municipalities, and neighborhood associations.
Residents are pre-staged on a secure roster
Before anyone downloads an app, your community data is organized and ready for a controlled rollout.
Community administrators maintain an official roster: households, contact emails, roles, and optional identifiers your community already uses (such as account numbers). Roster entries can be prepared in bulk and kept in sync as people move in or out.
- Import or update members in one place—your source of truth for who belongs to the community.
- Control visibility: operational data stays inside the community tenant, not scattered across tools.
- Prepare for invitations and verification without exposing the roster to the open internet.
Example: roster table with units, names, and invitation status—blur PII in marketing shots.
Personal invitations, tied to the roster
Email invitations go to the addresses you already trust—each link is scoped to a single household or member record.
Admins generate invitations from roster entries or targeted email lists. Each invite carries a secure token, an expiry, and a clear path for the recipient to create or sign in to an account and join the right community automatically.
- Residents see which community they are joining and which email was invited.
- Admins can track pending, accepted, and expired invites and resend when needed.
- Invites complement roster-based flows—ideal for staggered onboarding across a large property.
Example: branded invite email and the “accept invitation” screen with community name.
Enrollment: verify identity, accept policies, activate access
Whether someone arrives via invite or self-serve discovery, the same enrollment standards apply.
Discovery. New users find their community by name or code, then submit details that match your official records (name, address, and optional account identifiers).
Matching. Submissions are evaluated against the roster. High confidence matches can be approved instantly; uncertain matches enter a queue for a community admin to approve or decline—always with an audit-friendly trail.
Policies. Each community maintains its own acceptable use policy. Members acknowledge it when they join and again whenever administrators publish material updates—so expectations stay explicit as rules evolve.
Activation. Once verified, the member receives the resident role and lands on the community overview with access to feed, messaging, documents, and the other modules your board enables.
60–90s walkthrough: search community → verification form → acceptable use checkbox → success state.
The member home: overview, updates, and conversations
Residents spend most of their time here—clear navigation, mobile-friendly layouts, and content that respects roles.
The overview is configurable by community leaders: highlight upcoming meetings, pinned announcements, documents residents need most, and other blocks that match how your association communicates.
- Feed — announcements and discussion threads with reactions and comments; moderators can pin what matters.
- Direct messages — one-to-one conversations inside the community context, with unread indicators and directory controls you define.
- Documents & meetings — published files, agendas, and meeting schedules with RSVP flows so attendance is visible to authorized leaders.
- Roster directory — a member-facing view of who is in the community, respecting privacy and opt-outs your policies require.
Screenshot: community overview with announcements, quick links, and personalized blocks.
Governance, requests, and compliance
Beyond day-to-day communication, communities run formal processes. Here is how those surfaces typically fit together—use your screenshots to show real forms and queues.
Formal votes & polls
Create ballots, voting windows, and outcomes residents can trust. Board workflows stay separate from casual feed discussion.
Service requests (tickets)
Residents open structured requests with categories and status—staff and vendors respond without losing context.
ARC & architectural review
Submit applications, attach plans, and track reviewer decisions in one thread per project.
Amenity reservations
Pools, clubhouses, courts, and shared spaces expose availability rules so self-service booking stays fair.
Violations & compliance notices
Document incidents with timelines and correspondence so enforcement is consistent and reviewable.
Community settings & roles
Residents manage profile and notification preferences; authorized leaders configure what the community exposes.
Optional hero video: board admin walking through tickets + vote creation in under two minutes.
Trust, privacy, and ongoing communication
Prospects and residents should always know how data is handled and how to reach a human.
MyCommons separates platform-wide legal notices (for example, privacy and cookies) from each community's acceptable use policy. Members can adjust email and in-product preferences where your deployment enables them.
Use this section for a short founder letter, SOC2 roadmap, or customer logos—whatever helps your sales motion. Pair it with a downloadable PDF one-pager using the same screenshots you place above.
Screenshot: notification preferences + link to privacy policy and acceptable use in context.
Ready to show this live?
Swap placeholders for product captures, add your brand voice, and link to a demo tenant or calendar booking—this page is static marketing copy until you wire those assets in.