This is how Neighbors.fyi works for residents.
Start a free community for your HOA
Admin·2 min read·Updated May 18, 2026

Admin panel

The single landing page for everything an admin manages. user approvals, request queues, the financial ledger, content, infrastructure, the audit log. Organized in five groups, gated by role and plan.

On this page

Who sees it

Reaching /admin requires the admin or system_admin role on your profile. Any other account that tries the URL is redirected to /dashboard. Board members and regular residents don’t have admin access unless they’re explicitly granted one of those roles.

The five groups

The admin page is a grid of links grouped by topic, not a separate dashboard with its own widgets. Each link opens the dedicated admin sub-page for that feature. The groups:

People & Access covers user management (approve / deny pending registrations, change roles), invite codes (generate single-use or multi-use codes), and the property roster (CSV import, lat/lng, occupancy type).

Requests & Compliance is the queue side of the app: maintenance requests, architectural reviews, violations, estoppel requests, the compliance dashboard, and dues administration. Most admin time gets spent here.

Community Content holds the financial dashboard (budgets per year, categories, PDF import) and the welcome kit (the post-onboarding orientation cards new residents see).

Directory & Infrastructure holds chat-channel management and amenity-reservation administration.

System holds the emergency-alert composer (one active alert at a time, broadcast to every account) and the audit log (the read-only history of every admin action). For system_admins this group also includes Site Settings.

Why some items don’t appear

Two filters can hide items from this grid even though they exist as URLs.

Plan tier. items whose feature isn’t included on the community’s current plan are removed entirely. The corresponding admin pages still exist, but the nav and this grid don’t advertise them. an upgrade lights them back up.

Community mode. when an admin toggles the community on into the community-mode demo / placeholder state, payment-flow items (dues, violations, architectural, maintenance, estoppel, financials, compliance) are hidden from residents and from the relevant slots on this grid. The admin can still reach them via direct URL if needed.

Site Settings is gated separately
Site Settings (/admin/settings) requires the system_admin role. a plain admin doesn’t see the link on this page or have access via direct URL. That keeps app-wide config (theme, plan, categories, feature toggles) on a smaller blast radius.

Audit history

Every meaningful admin action across the portal is recorded in the audit log (creates, edits, deletes, status changes, role changes, approvals, refunds). The log is the source of truth when figuring out who did what and when, and most admin sub-pages link directly into the audit log filtered for the relevant entity. The catch-all entry sits in this page’s System group.

Like what you’re reading?
Start a free community