Community Issues
Report something that needs attention in the community, coordinate with neighbors on it, and track it until it is fixed.
On this page
Reporting an issue
Community Issues is for things you notice that need attention in the neighborhood: a broken gate light, a pothole, an overflowing bin. It is not for personal requests like a new decal or a guest-list change. those go to Resident Services. From /issues, the form at the top takes a title, a category, a description, and one optional photo. Submit and it lands as open with priority medium by default. Admins and the relevant committee (if the category is mapped to one, see below) get notified. You can also report an issue right on the community map, which drops a pin at the spot.
Photos go into a private storage bucket and are served via short-lived signed URLs when the page renders. You don’t need to do anything special: drag a photo into the form and it’s attached.
Who sees it
Community issues are visible to the whole community by default, so neighbors know something is already reported and don’t file it twice. Your name is not shown to other residents (only admins see who reported what), the same way map pins never show the reporter. If an issue is genuinely sensitive, tick Keep private when you report it and it stays between you and the office.
Talking it through
Every community issue has a discussion thread at the bottom, so neighbors can chime in: confirm they’ve seen it, share what they know, or (for a lost-pet report) say “I found them, they’re at 12 Oak St.” The reporter, anyone who tapped “I see this too,” and everyone already in the thread get notified of new replies. You can report a comment that’s out of line, and admins can remove it.
Categories and committee routing
The default category list covers the usual shared-amenity surfaces: pool / spa, gym, playground, clubhouse, common area, landscaping, lighting, parking / roads, trash, signage, and other. Your admin can override this list in Setup, including renaming categories, adding new ones, and binding a category to a specific committee.
When a category is bound to a committee, members of that committee get notified the moment a request in that category arrives, not just the admins. That’s how a landscape committee can triage landscape requests without an admin manually flagging each one.
How status flows
Requests move through four statuses: open, in_progress, resolved, and closed. The page lists the first two together as “Active” (in-progress first) and the last two as “Past.”
Open is the default after submission. In progress is flipped by staff when someone’s actively working on it. Resolved means staff believe the issue is fixed, but you can still reopen it. Closed is the terminal state; reopening from closed requires staff to do it, not you.
Priority is a separate field: low, medium, high, urgent. It’s set by staff, not by you, and doesn’t change anything about how the request flows; it’s a sorting hint for the admin queue.
Editing and reopening
You can edit your own issue’s title, category, description, and photo while it’s in open or in_progress: open the issue, tap Edit, and add, replace, or remove the photo right there. After it moves to resolved or closed, edits are locked.
From closed, only staff can reopen the request (with their own action that doesn’t require a note since they’re the ones reopening it).
When the page is hidden
Some communities run in community mode, a lighter feature set without HOA-specific workflows. In community mode the Community Issues page is disabled and a visit to /issues redirects to the dashboard. If you don’t see Community Issues in your sidebar, that’s why.