Site settings

The system_admin-only knob room: plan + billing, account owner, custom domain, integrations, feature toggles and site modes. Your community name, logo and colors live on Setup, and payment settings live on Dues.

Who can open it

Site Settings requires the system_admin role. A plain admin doesn’t see the link on the admin panel and is redirected to /admin if they hit the URL directly. The intent is to keep platform-level changes (plan, custom domain, feature toggles, site modes) on a small blast radius. one or two people per community.

Page layout

The page is a single column of sections. Each one is a self-contained accordion with its own save button. nothing here is a single global save.

The sections, grouped

Plan & billing. Current tier, household count basis, link out to manage subscription on the admin portal. Custom domain (e.g. portal.your-hoa.com) is configured here too. you get DNS records to set on your registrar after saving.

Integrations. Google Meet OAuth (connect an account so admins can generate meet links from event forms).

Feature management. Per-page on/off toggles for ~23 resident-facing surfaces. Disabling a feature hides its nav item and redirects its URL to /dashboard. Items locked by community-mode display a lock until the mode is cleared.

Site modes. Community mode, for a community run on an outside management system: dues, financials, estoppel, issues, architectural review and violations are hidden. Turning community mode on or off updates Feature Management to match; a toggle you set by hand on another page is left alone.

What moved off this page

Anything your board decides for itself now lives where the people who decide it work, so it no longer needs a system_admin.

Community identity. Community name, phone, Reply-To email, time zone, logo, and appearance (theme, colors, saved color combinations) are the first card on /admin/setup. See the Setup tutorial.

Payment settings. How residents pay (an external payment URL or integrated Stripe), card acceptance, who covers the processing fee and the payment note shown on the pay screen are on /admin/dues, for anyone with Site Settings admin access. For an external portal, pick your bank if it’s listed (Alliance Association Bank, for example) to start from ready-made resident instructions and get a warning if the link is an old address or is missing your community’s ID. Otherwise choose Other. Connecting the Stripe account itself stays with the account owner.

Estoppel fee. The fee your community charges for an estoppel certificate, and how long a certificate stays valid, are also on /admin/dues, for anyone with Dues admin access. The Neighbors.fyi processing fee added at checkout is not a community setting.

Who pays the card fee

The payment settings card on /admin/dues holds the one setting that changes what your residents are charged, so it is worth understanding before you touch it. The fee choice only appears once the community is on integrated Stripe.

Absorb (the default). The resident pays exactly their assessment and the association nets the assessment minus Stripe’s processing fee. The fee becomes a budget line item, the same way it would with any merchant account.

Pass-through. A service fee is added at checkout, shown to the resident in dollars before they pay. The resident picks bank or card first, and bank always carries the lower fee.

Debit cards never carry the fee. Card network rules prohibit surcharging debit, so a resident paying by debit pays the assessment exactly and the association absorbs that (smaller) cost. You will still have some processing cost under pass-through, and that is expected.

Rates are set by Stripe’s agreement with your association, not by us. Every payment is a direct charge on your own Stripe account, so your rate is whatever you have with Stripe. see stripe.com/pricing. Bank payments cost the association substantially less to process than cards, which is the usual reason a board restricts card payments.

Switching modes is audit-logged, and turning cards off never cancels an existing auto-pay. see Dues & payments for what residents experience.

Account Owner & handover

One system_admin is the community’s Account Owner. the person responsible for the neighbors.fyi subscription and the payment method on file. It’s set automatically to whoever first sets up the community, and it’s shown in the Account Owner section on this page (right below Plan & billing).

Transferring ownership. If you’re the Account Owner and want to hand the community to someone else (a new board treasurer, say), pick them from the member list and send the transfer. They’re made a system_admin and asked to add their own payment method, then accept. On accepting, the subscription is repointed to their card and the previous owner’s card is removed, so ownership only moves once billing is genuinely re-homed. the community is never left without an owner, and you’re never left paying for a community you handed off.

Closing the community. If there’s genuinely no one to hand off to, the Close community option cancels the subscription at the end of the current billing period and starts the wind-down. Use this when the community is shutting the portal down, not for a routine handoff.

Why some sections don’t show up

A section that has nothing to configure is left off. The Google Meet section only appears once the integration is set up, and Feature Management lists the pages your plan doesn’t include as locked rather than as toggles. The page reads the hidden-feature set on render; an upgrade puts the corresponding sections back the next time you load Settings.

Audit trail

Every section save goes through an audited server action, so the change shows up in the audit log with the system_admin user, the field name, and the before / after values. The top of Settings has a direct link into the audit log filtered to entity_type=settings, which is the fastest way to answer “who turned this feature off”. Saves made on Setup and Dues land in the same filter.