Organization Onboarding
A step-by-step guide for organization administrators getting a new club ready in Hearth & Hall.
Use this after your organization exists in the product. Today, a Hearth & Hall platform operator creates the organization and works with you through concierge onboarding (personalized setup — not a self-serve signup). Before members can use the organization, someone with Accept Terms of Service key terms.accept must accept the current Terms in the product (hard gate) — typically an Admin, or an officer role such as President that was granted that permission. Creating the org does not count as acceptance, and Hearth & Hall platform operators cannot accept on behalf of your club. Self-serve club signup may come later — the configuration steps below stay the same.
What you get on day one
When the organization is created, Hearth & Hall seeds:
| Seeded item | Purpose |
|---|---|
| Organization | Name + URL slug (used in routes such as /orgs/{slug}/...) |
| Founding membership type | One roster type (default name Member, overridable at org create) with the Member role as baseline, so the operator can invite the first real admin |
| Seeded role | Member only — everyday participate permissions |
Nothing else is configured yet — no Certificate Holder / Guest / Board / Treasurer concepts, no reservation catalog, no members. A platform operator invites the first admin. That admin creates the membership types and officer roles the club needs.
How access works
Hearth & Hall uses roles and permissions rather than a single fixed rank:
- Each membership has an Admin on/off flag. Admins have every permission in the organization. Only an existing Organization Admin can turn that flag on or off.
- Permission keys are fixed by Hearth & Hall (billing, catalog, documents, …). Orgs do not invent keys.
- Everyone else gets permissions from the roles they hold. You name roles for your club (Board, Treasurer, Hospitality, …) and attach the keys each role needs.
- A membership can hold zero or more roles. Roles come from two places:
- Type baseline roles — every membership of a type automatically gets that type’s baseline role(s). The founding type starts with the seeded Member role; attach baselines when you create more types.
- Assigned roles — officer/committee roles you create and assign to individual members from the roster.
| Role | Who defines it | Typical use |
|---|---|---|
| Member (seeded) | Platform starter | Directory, book/cancel own reservations, add family members |
| Your officer roles | You (Admin) | e.g. Board → catalog/events/documents; Treasurer → estimates/invoices |
| Admin flag | Membership setting | Everything (superset of all roles) |
Hold Admin yourself for setup. Create Board / Treasurer (or whatever names your bylaws use), grant them the right permissions, then assign colleagues so catalog and billing can proceed in parallel.
Checklist overview
- Sign in and open the organization
- Accept the Terms of Service
- Review membership types
- Create officer roles and grants
- Invite officers and primary members
- Build the roster (family / sub-accounts)
- Configure the reservation catalog
- Prepare billing
- Optional: forums, mailing lists, events, and documents
- Smoke-test before members arrive
1. Sign in and open the organization
- Open the member app — from the public site use Members, or go directly to
members.in production (local UI in development). - Sign in with the account that was made Admin when the org was created (or the Admin Hearth & Hall assigned to you).
- Open the invite link from your welcome email to choose a password. If you already have a password and forgot it — or the invite email is missing — use Forgot Password? on the sign-in page. A reset link is emailed when that address has an account, including before a password has been set.
- After sign-in, ordinary members land on their organization dashboard (the club they used most recently if they belong to more than one). Platform administrators land on Platform first — open your club from the context switcher. Use the context switcher anytime to change organizations.
Until Terms are accepted, members cannot use organization features. Anyone with Accept Terms of Service sees a blocking accept screen; other members see that the organization is not activated yet. After acceptance, navigation is org-scoped under sidebar groups: Club (Dashboard — today’s ops home — see Dashboard, Members, Forums, Events, Map), Book, Communications (Mailing Lists, Email Members, Email Templates when granted mailing-lists.manage), Money, and Ops (Documents, Vendors when granted vendors.directory.view, Reports when granted). On a phone, open the menu that shows the current area to switch between those features; on a wider screen the same areas appear as the lodge sidebar.
2. Accept the Terms of Service
Who: Anyone with Accept Terms of Service key terms.accept — organization Admins always have it; you can also grant it to an officer role (for example President) under Members → Roles.
- Read the Terms (and linked Privacy policy) presented on the accept screen — the screen shows the revision you are accepting; full text also lives on the public site at
www./terms with the same revision. Accepting the Terms also accepts the then-current Platform Pricing Agreement (public Pricing page), unless your club has a written pricing override with Hearth & Hall. Fee tables are not copied into the Terms; they are linked from them. - Confirm you have authority to accept on behalf of the organization.
- Accept the current revision. The product records which member accepted, which organization, which revision, and when (for support and audit).
Members cannot use the organization until this is done. If Hearth & Hall publishes a new Terms revision later (including when platform pricing changes), administrators are notified by email under the Terms; the revision is deemed accepted unless the organization notifies Hearth & Hall in writing within sixty (60) days. A new revision does not block your organization again; the in-product accept screen appears only before the first acceptance.
Platform operators: Hearth & Hall staff who created your organization can help set up roles and invites, but they cannot accept Terms for you — a club member with the permission must do that.
3. Review membership types
Where: Members → Membership Types (Admin only)
Membership types are your dues / roster / pricing classes. Hearth & Hall does not ship club-specific type names (Certificate Holder, Guest, …) — you create what your bylaws need. Day one includes only a founding roster type so the operator can invite the first real admin; rename it and add more types as needed.
Capabilities such as booking, voting, and adding family members come from roles, not type checkboxes. Attach the seeded Member role (or others) as baseline roles on each roster type.
Suggested types (examples — create these if they fit your club)
| Example name | Typical use | How members are added |
|---|---|---|
| Provisional / Certificate Holder | Primary members who sign in | Invite Member when Requires Email is on |
| Active / family | Linked household members under a primary | Add Family Member when Requires Email is off and Requires Primary Account is on |
| Staff / Steward | Operators who sign in but are not club members | Invite Member when Requires Email and Staff Member are on; omit Member baseline unless you want self-book |
| Guest Adult / Guest Child | Pricing only — not roster memberships | Never invited; used when booking a named guest when On Roster is off |
Configure each type
| Setting | What to decide |
|---|---|
| Name / Description | Labels members and staff will recognize |
| On Roster | Off = pricing-only (no roster row / no baseline permissions unless you attach roles); on = real membership rows |
| Requires Email | On → Invite Member; off (with roster on) → Add Family Member |
| Requires Primary Account | Linked sub-account under a primary (typical for children / household members) |
| Staff Member | On = operator / steward accounts: hidden from the default Members → Roster (use Include Staff to show them), excluded from “all members” email and announcement blasts, and not offered as book-for subjects on Reservations → Book / Grid (staff book for club members via reservations.create.for-member, not as reservation subjects themselves). Still invited with email; not counted toward platform primary fees. Requires On Roster. |
| Baseline Roles | Which roles every member of this type receives (founding type starts with Member; staff types usually omit it) |
| Active | Deactivate instead of deleting if the type is already referenced |
Tips
- Match names to your bylaws.
- Keep at least one pricing-only type with On Roster off if non-members book resources.
- Prefer deactivate over delete when a type is already used on members, prices, or reservations.
- For stewards: create a Staff type, create a Stewards role (§4), invite with that type, and assign the Steward role.
4. Create officer roles and grants
Where: Members → Roles — needs members.roles.assign, which Admins always have
Only Member is seeded. Create the officer hats your club needs before inviting colleagues who should not be full Admins.
Suggested starter roles (names are yours — match your bylaws):
| Role name (example) | Grant these permissions (examples) |
|---|---|
| Board | resources.catalog.manage, events.manage, announcements.create, forums.categories.manage, mailing-lists.manage, mailing-lists.send, documents.manage, members.roles.assign, reservations.cancel.any, reservations.create.for-member, reservations.create.guest, reservations.reprice, audit.view |
| House / Property (optional) | vendors.directory.view, vendors.directory.manage — contractor black book under Ops → Vendors. Not seeded on Member |
| Stands / Property (optional) | resources.map.manage — set the club home location and place stand pins. Not included in catalog manage |
| President (optional) | Often includes terms.accept (and broad leadership keys) when the club wants the President — not only Admin — to bind the Terms |
| Treasurer | billing.estimates.manage, billing.charges.waive, billing.invoices.send, billing.invoices.view-all, audit.view |
| Hospitality (example; clubs may still label the role Steward) | reservations.create.for-member, reservations.create.guest, reports.day-sheet.view, billing.estimates.manage (edit open member tabs before invoice; catalog prices only). Assign to people on a Staff membership type (§3), not the founding Member type. |
You can add committees (Hospitality, Property & Grounds, …) the same way — create a role, attach keys, assign people.
Audit Trail: Admins (and any role granted audit.view) can open Audit Trail in the top nav to review who changed security-sensitive, financial, document, and vendor-directory records.
Reports: Grant reports.day-sheet.view on your Steward / Hospitality role so those members see Reports → Meal Planning and Reports → Day Sheet. Meal Planning shows today and tomorrow headcounts for active resources under the platform Meals kind (Breakfast / Lunch / Dinner style), refreshing about every 20 seconds. The Day Sheet lists day-of reservations (meals, lodging, tee times, boats, …) for kinds and resources marked On Day Sheet in Catalog Setup — turn that off for items like service fees. Staff can print a day (or 3-day / week) sheet, mark attendance on paper, then update open tabs from Billing (Add Catalog Charge, change quantities, remove lines) or Reservations → Book / Grid. Both views are read-only.
Organization admins can enable the morning report email (scheduled digest at 6:00 in the organization timezone) so members with Day Sheet view receive today/tomorrow meal totals and overnight lodging counts. Recipients follow permission grants — there is no separate recipient picker yet.
Hospitality staff prepare draft estimates from Billing → Member Tabs (Prepare Estimate). A treasurer Converts that estimate on Billing. Week Sheet is not currently available.
5. Invite officers and primary members
Where: Members → Roster → Invite Member (needs the invite permission; Admins always have it)
- After officer roles exist, invite colleagues so catalog and billing can proceed in parallel.
- For each invite, choose:
- Name — how they appear on the roster (edit later from the roster if needed)
- Membership type (a roster type you created for adults who sign in)
- Roles — optionally assign the officer roles you created (e.g. Board, Treasurer) if you have Assign Roles (
members.roles.assign) or are Admin. These attach to the pending membership and carry through when the invite is accepted. - Organization Admin — only an existing Organization Admin can check this.
- The invitee appears on the roster as Pending immediately.
- They open the invite link and become Active. New accounts set a password (entered twice to confirm). Existing Hearth & Hall accounts enter their current password instead — or, if already signed in as that email, confirm with Accept Invite without re-entering a password. After accept they land in your organization. If they set a password or sign in before accepting, they may see No Organizations Yet until they open the invite link — Accept Invitation still works while signed in.
- You can assign roles on the invite (step 2) OR after they accept — open their roster row → Edit. Both paths need Assign Roles (
members.roles.assign) or Admin. - If someone is still Pending, use Send Invite on their roster row to email a fresh link — even when Sign-in already shows Active (they already have a password).
Assigning access for a new club
| Give them… | So they can… |
|---|---|
| Admin flag | Manage types, invites, roles, and membership details — full access |
| Your Board-style role | Whatever you granted (typically Catalog Setup, events, documents, …) |
| Your Treasurer-style role | Whatever you granted (typically estimates & invoices) |
| Member role (baseline) | Everyday member features — comes automatically with roster types |
You remain Admin. A Hearth & Hall platform operator is not added to your roster. They can set the club up without a membership. A real membership, if you invite them later, can be disabled like anyone else’s.
6. Build the roster (family / sub-accounts)
Where: Members → Roster
Add households once the primary is on the roster. A Pending primary does not need to sign in first. Ordinary members see names, type, status, and photos on the roster; Email, Sign-In, and Roles columns are for Admins and officers with members.update / members.roles.assign. Primaries still Send Invite for household adults from Actions.
- Primaries whose role grants sub-account creation (the Member baseline role does) — or Admins — use Add Family Member for household members who do not need their own email yet.
- Capture relationship (Child, Grandchild, Grandparent, Parent, Partner, Spouse) and optional Under 13 for linked family members only (child vs adult rate brackets; blocks email and sign-in). Primaries cannot be under 13.
- When a family member is 18+ and should sign in themselves, use Send Invite on the roster. The same action resends a fresh invite link for members who are still Pending (including when they already have a password).
Billing note: Only primary members are billable. Charges for a linked sub-account resolve to the primary’s open tab / invoice.
7. Configure the reservation catalog
Where: Reservations → Catalog Setup — requires resources.catalog.manage, or Admin
Do this before opening booking to the membership. Work kind → resource → rules → prices.
6a. Create resource kinds
A kind is a category of bookable thing (lodging, meals, boats, courts, …). Every organization is seeded with platform Meals (Fixed Slot, locked) and Lodging (Interval by default) kinds — rename them if you like; they cannot be deleted (deactivate to hide from Book). For Lodging, choose Interval (named rooms / cabins) or Quantity (a pool of identical rooms with capacity). Add any other kinds your club needs.
- Create Kind (custom kinds only — Meals and Lodging already exist).
- Set Details: name, booking mode, icon, Sort Order, Active, and On Day Sheet.
- Interval — date/time ranges; exclusive named resources (e.g. Room 12, boats)
- Fixed Slot — grid of slots (e.g. tee times, meal seatings)
- Quantity — pool of identical units (e.g. room pools, carts)
- Sort Order — controls kind order in Catalog Setup and column order on Reservations → Grid (lower numbers first; same order within a kind uses each resource’s Sort Order)
- On Day Sheet — include this kind on Reports → Day Sheet for hospitality staff (leave off for pricing-only items like service fees)
- Open Schedules and define when that kind is generally available (weekly windows, seasons, blackouts). Mark a default schedule.
- Open Policy — lead time, duration limits, cancel-before, capacity-related limits. (Who may book is governed by the booking permission on a member’s roles, not a per-policy minimum role.)
- Open Pricing — default and optional per membership type rates (Flat, Per Hour, Per Night, Per Slot). Add Guest / child rates if your club uses them. Optional effective date ranges for seasonal prices.
Under Meals, create resources such as Breakfast / Lunch / Dinner — those drive Reports → Meal Planning. Under Lodging: for numbered rooms create one Interval resource per room; for a fungible pool set Lodging to Quantity, create one resource (e.g. Rooms), and set Capacity to how many rooms are available.
6b. Create resources under each kind
- Select the kind → Create Resource.
- Details: name, capacity (required for Quantity pools; optional for Fixed Slot party limits), Active, On Day Sheet, On Map (include this resource on the club Map; leave off for lodging, meals, and other items that are not stands), optional schedule inheritance vs custom.
- Availability: inherit the kind’s default schedule, pick another kind schedule, or override with resource-specific rules.
- Price: optional resource-level overrides when one instance differs from the kind default.
6c. Verify booking paths
From Reservations → Book (guided stay wizard):
- Plan a test lodging + meals stay for yourself (and a guest if applicable): Who → Check-In / Check-Out → Lodging nights → Meals → Review / Confirm.
- Stewards (or anyone with Create Reservations For Members) can search Book for Member on the Who step for phone/text bookings, leave Me unchecked, then continue the same guided flow. Ordinary members only see household checkboxes, not the full roster search.
- Confirm the reservation quote (priced lines that land on the open tab) looks right for membership type and age bracket.
- Confirm cancel behavior matches policy.
Use Reservations → Grid for amenities, steward multi-person matrix booking, and other non-stay kinds. The stay wizard covers platform Lodging and Meals only.
Deactivate kinds or resources that should not accept new bookings; delete only when nothing references them.
6d. Club map (optional)
Where: Map — placing the home pin and stand pins requires resources.map.manage, or Admin. The On Map catalog flag is in Catalog Setup (resources.catalog.manage). Members can view the map after setup.
- In Catalog Setup, leave On Map on for stands (it saves when you flip the switch) and off for lodging, meals, and similar.
- Set the club home location (center of the woods, lodge door, or another landmark) before any stand pins can be placed.
- Place GPS pins on stand resources. Members can open Map to see those pins; the home pin shows the organization name.
See Map.
8. Prepare billing
Where: Billing (billing permissions, or Admin)
- Ensure at least one person has your billing role (or is Admin) and can sign in.
- Confirm reservation booking creates / updates the member’s open tab when prices are configured.
- Practice the billing loop on Billing → Member Tabs: click a primary (including Pending) → Prepare Estimate (date filter + selected completed charges) → treasurer Convert on Billing → Estimates → Send on Billing → Invoices (emails the bill-to member a My Profile link to pay or download a PDF) → the member pays with a saved card on My Profile after Billing → Configuration (Stripe Connect) can accept charges. Estimates and invoices list the bill-to member. Someone with Manage Estimates can Add Catalog Charge (priced from the catalog — no typed overrides), change quantities, or remove draft charges that are not already on an estimate. Removing a reservation-linked charge unlinks it from the tab and leaves the stay booked; Waive (
billing.charges.waive) comps the charge without canceling the hold. Cancel the stay from Book or Grid only before the start date after the charge is waived or removed. Upcoming charges stay on the same open tab. Waived charges go on the estimate and invoice at $0.00 marked Waived. Charges already on an estimate leave the tab. Open-tab charges that are not billed to a current primary, or whose reservation is missing or cancelled, appear as an Orphaned row; check people, dates, or charges and Move to Member onto a primary’s open tab, then Prepare Estimate from that tab. Someone with Manage Estimates can Void a draft estimate so those charges return to the open tab. Use Download on any invoice for the PDF. Someone with Send Invoices (or Admin) can Refund an individual succeeded payment from Payment History on an invoice, or Void an unpaid invoice so its charges return to the open tab. - Someone with View All Invoices (typical Treasurer grant, or Admin) can use Billing → Invoices → Export to QuickBooks to download invoices and payments for a date range. Hearth & Hall keeps
INV-####; record the QuickBooks DocNumber from the invoice ⋯ menu so export can show both. - Member history & profile: members open My Profile (click their name or avatar in the header) for a read-only household open tab, invoices, payments, saved cards, and Pay — not under Billing — and optionally set a photo and a short About Me note. Linked family accounts bill to the primary and see that household’s history with a billed-to note — see the billing note under Build the roster.
- Payout setup (Stripe Connect): member dues settle to the club via Stripe Connect, not to Hearth & Hall. Someone with Send Invoices (typical Treasurer grant, or Admin) opens Billing → Configuration, starts Stripe’s hosted onboarding (identity + bank), and returns to Configuration when finished. Use Refresh Status if the page does not update on return. Members may save a card on file on My Profile before payout setup is complete, but Pay stays blocked until Stripe reports the connected account can accept charges.
- Past-due reminders (optional): someone with Send Invoices (or Admin) can enable Billing → Configuration → Past-Due Reminders so unpaid invoices email the bill-to member at 30, 60, and 90 days after the invoice was created. Paid and voided invoices are skipped. Off by default — see Billing.
Never enter club bank account or card PANs into Hearth & Hall forms outside Stripe-hosted or embedded flows — the product stores tokens only.
9. Optional: forums, mailing lists, events, and documents
Configure these when your club is ready to use them; they are not required to open reservations.
| Area | First actions |
|---|---|
| Forums | Create categories members will recognize; pin welcome threads if useful. Each category has an All Members switch — turn it off to pick the specific roles that may view/post in the category (leave the role list empty for Admin only). Admins always see every category; creating/editing categories needs forums.categories.manage |
| Mailing Lists | Create a saved audience (e.g. “All Members”, or a membership type / org role filter). The All Members audience switch controls who receives messages; when off, pick a membership type or role. Staff membership types are never included in “All Members” audiences (so membership-only topics such as compensation stay off staff inboxes); target a staff type or role explicitly when you need to reach operators. The separate All Members Can Manage access switch (+ role picker) controls who may use the list. Creating/editing lists needs mailing-lists.manage |
| Email Templates | Org-shared subject/body drafts for Email Members (with optional {{MemberName}} / {{OrganizationName}} / {{SenderName}} placeholders). Manage on Email Templates (mailing-lists.manage); apply or Save Template from Email Members |
| Email Members | Compose subject/body (or load a template), pick an audience (all members, admins, membership type, role, or saved mailing list), review the recipient list (name and email) for that audience, then send. “All members” excludes staff types (same rule as mailing lists). Messages send from the platform address; replies go to your personal email (Reply-To). You need an email on your account before you can send. Needs mailing-lists.send, and list ACL when targeting a saved list. Send history shows subject, audience, count, and time |
| Events | Create upcoming club events; confirm registration / waitlist behavior |
| Documents | Create folder tree (bylaws, minutes, forms); set each folder’s access with the All Members switch — turn it off to pick the specific roles that may open the folder (leave the role list empty for Admin only). Admins always see every folder; creating/editing folders needs documents.manage |
| Vendors | Contractor black book (company, contact, phone, email, notes, service tags). Grant vendors.directory.view / vendors.directory.manage — not on Member. Vendors do not sign in or receive Hearth & Hall payments — see Vendors |
| Map | Set the club home location, then pin stand resources (resources.map.manage). Members can view the map after setup — see Map |
10. Smoke-test before members arrive
Work through this as Admin (with officers who hold your catalog/billing roles if needed):
- Membership types match how your club actually admits people
- Officer roles exist with the right grants; at least one catalog officer and one billing officer can sign in (or you stay Admin for both)
- A primary invite accepts and reaches Active
- A family member can be added under a primary who is still Pending, and under one who has accepted
- Catalog has every kind members will book, with schedules and prices
- Club map home location is set and stand resources you want on the map have pins (or map is intentionally deferred)
- A test reservation quotes the expected rate and lands on the primary’s tab
- Someone with billing permissions can convert / send an invoice on the test path
- Forums / mailing lists / events / documents are ready enough for launch day (or intentionally deferred)
Access at a glance
The Admin flag is a superset — it grants everything regardless of roles. A member can hold several roles at once; their access is the union of those roles’ grants.
| Capability | How you get it |
|---|---|
| Everyday member features | Seeded Member baseline on roster types |
| Catalog, events, documents, forums, mailing lists, cancel/reprice any | Role you create + grant (e.g. Board) — or Admin |
| Club map home location and stand pins | Role you create + grant resources.map.manage (e.g. Stands / Property) — or Admin |
| Estimates & invoices | Role you create + grant (e.g. Treasurer) — or Admin |
| Membership types | Admin (or a role with members.types.manage) |
| Update member type or status | Admin (or a role with members.update) |
| Assign extra roles on invite or roster Edit | Admin (or a role with members.roles.assign) |
| Organization Admin flag | Existing Organization Admin only |
After go-live
- Invite remaining members in waves; keep Pending visible on the roster until they accept.
- Adjust prices and schedules seasonally without rebuilding the catalog — use effective dates and schedule seasons where available.
- Deactivate obsolete types or resources rather than deleting history.
- Contact Hearth & Hall support (or your platform operator) for org rename / slug changes and production payment go-live.