Feature catalog

visitors see a cookie banner with accept, reject optional, and customize choices. Optional Vercel Analytics and Speed Insights load only after analytics consent; signup and invitation paths stay excluded. Privacy Policy, Cookie Policy, Terms of Service, and a permanent Cookie preferences link appear in public and authenticated footers.

the marketing homepage offers a Goodness Guestbook-owned newsletter signup (separate from operator or venue marketing lists) with explicit marketing consent and stored consent evidence.

from the sign-in page, **Create account** opens a form for name, email, and password. That one login is the person's profile for future courses, retreats, and events. A course, retreat, or event join link opened while signed out makes account creation the main step, and the heading names that course, retreat, or event. Its cover photo and host logo sit beside the form when those images exist. Sign-in and a magic link stay available. If that email already has a confirmed account, the form says so and offers sign-in or a magic link. After submit they must open a branded verification email; password sign-in works only after that inbox proof. Opening the link signs them in and, for a course registration link, enrolls them in the course. They can then sign out and sign back in with the same email and password. Every password field can show the password while it is typed; it stays hidden until they choose Show password.

signing in, creating an account, sending a magic link or reset link, or verifying a code shows that action on the button and above the form until it finishes.

when you belong to one program and one property that are connected, and to no other operator or venue, sign-in offers one card, Your retreat center, plus Participant. The card says: “The retreats you host at your own place. Open the property from there when you need it.” Belonging to another operator or venue keeps the separate Operator, Venue, and Participant cards. Me stays its own card.

from the personal hub, manage password, authenticator-app MFA, sign-in email (with verification), sign out of other sessions, and review recent security activity on your account.

anyone logged out can browse `/discover`: search and filter listed retreats and courses, open a public detail page, then sign in to register for a retreat or enroll in a course. Only public fields appear (title, dates, city or place name, operator, short description, price, optional cover image). Signup tokens and street addresses never appear on the catalog. Signed-in guests see **Signed up** or **Enrolled** on offerings they already joined, with links to their retreat home or My Courses instead of repeating signup.

from the sign-in page, someone can create their login and the organization in one step and become Owner immediately. Brand colors use Goodness defaults until changed in Settings (operator edit or venue listing brand). Everyone can set up profile, spaces, and draft retreats right away. Publishing, inviting staff, messaging, inquiries, relationship requests, and taking payment stay off until that person verifies their email. A teammate who has not verified does not block an Owner who has.

from sign-in, email a link, choose a new password, and continue to My Profile once it is saved.

every guest across **retreats, standalone events, and courses** in one contact book, including completed, cancelled, and archived offerings, with search and filters. **Alumni** = two or more offerings. Open a person for a tabbed profile: registrations, **per-offering registration responses** (grant-scoped), surveys, and a private **CRM note** for your team.

track interested people who are not on a roster yet; add leads manually and convert them onto a retreat when they are ready.

every attendee, with status (confirmed, pending, waitlisted, cancelled), contact info, emergency contact, dietary needs and allergies, passport and visa info for staff who need it, and private notes. Operators can **add a confirmed guest** from Attendees (name and email) in addition to public signups; new accounts get a claim email and private profile access still requires guest consent.

mark a team member (including venue staff) as visible to guests, with a short bio.

a rundown of every guest's dietary needs and allergies, exportable.

track a person who has expressed interest but is not yet a confirmed guest, and convert them onto the roster when they sign up.

the staff directory for the operator's own company: who can log in, and their permission level (Owner, Manager, Staff, or a custom role). Owners choose which roles can view sensitive guest details and which can correct participant data. Owner keeps branding, staff, relationship, and correction permissions on. Assigning staff to a specific retreat happens here too.

request, approve, or end a working relationship with a venue. The property you have connected as your own place is left off this list. Outside venues stay on it, including request, approve, and the venue picker when you create a retreat somewhere else.

request, approve, or end a bilateral partnership with another operator (prerequisite for cohosting). Search by operator name or **invite by email** to create their operator and activate the partnership when they accept.

invite a partner operator to cohost a retreat, event, or course; accept or decline; open a shared collaboration dashboard with explicit permissions (including **shared course curriculum** editing and optional **lesson release** toggles per partner); draft and unanimously accept a **financial agreement** (profit shares, reserves, settlement terms); maintain a **shared expense ledger** with approval rules for material commitments; run **profit reconciliation** with immutable statements and ledger-only operator allocations capped by unencumbered cash; **authorize profit distributions** (schedules, readiness checks, unanimous payout approval, ready-for-transfer ledger — no Stripe transfers or paid status); **record offline settlement** of authorized profit shares (reported by the paying operator and acknowledged or rejected by the receiving operator; either party may dispute an acknowledged settlement without creating a clawback; not independently verified; no Stripe transfer).

see where each shared retreat stands with its venue (proposal, confirmed, etc.), what's owed, and any contract the venue has sent, which the operator can sign; confirm the stay, and propose or answer changes to dates, space, capacity, and place.

reach out to a venue about hosting a future retreat, even before a formal relationship exists. The inquiry list does not offer your own connected property.

read venue reviews the operator has written, and guest reviews of the operator.

reusable contacts for outside services (transport, catering, photography) that aren't full venue partners and don't get a login.

workshops, circles, and one-day gatherings where the start and end calendar dates are the same day (multi-day programs stay under Retreats), with an **Event readiness** panel on the roster hub for operators (Brain recommendations; waiver gaps reported as unknown when signature data is not tied to registrations).

creating an operator one-day event starts with your connected property selected, the same way a retreat does. The gathering stays on the Events list, on a single calendar day, with its own registration list. It does not become a retreat.

KPI cards, status filters (upcoming, past, drafts, cancelled), search and location/host/date filters, a sortable table with registrations and ticket price (or collected revenue when payments are wired), CSV export, and a right-hand month summary with list/calendar toggle. Each row opens the **event roster** (registration list with status filters and counts). Operators with Manager access or higher can **add a confirmed guest** from the roster (name and email) in addition to the public signup link; new accounts get a claim email. **Event settings** holds schedule, visibility (**Draft** or **Published** — published events leave the Drafts filter), location, cover photo, **ticket pricing** (tiers and optional payment plans, same model as retreats), optional **venue revenue split** (partner venue, percentage, and whether the venue can see collected totals), a **public registration link** (tokenized signup that adds guests to the event roster; works when published and signups are enabled), and **duplicate** an event as a new draft copy.

on the event roster, managers see card charges in a read-only grid and open a row to refund that payment (same payment window as retreat Payments & Finances).

name, dates, optional partner venue or a place name only (no venue record), cover photo (upload a photo or paste an image URL), capacity, currency, and guest pricing. Portfolio **Planning** means dates are not set yet. **Draft or Published** is set when creating a retreat or under **Retreat settings** (sidebar Settings while a retreat is open). **List publicly** adds a retreat to the Discover catalog when it is also published, fully dated, and not past.

on Create New Retreat, Paid operators can paste notes or write a short description. AI extracts retreat fields, labels source facts vs suggestions, and flags missing information instead of inventing it. Review and edit the preview, then create. The manual form stays available on Free and Paid.

for one retreat: how many confirmed guests, days until departure, money collected versus expected, and travel readiness.

overall readiness when meaningful, lifecycle stage and maturity, applicable and unknown check counts, category breakdown, and up to three prioritized recommendations with links to fix issues (Free; feature-flag rollout).

operator home shows up to three prioritized actionable recommendations with retreat, standalone event, or course context and links; **Action Center** lists all open recommendations with filters, snooze, dismiss, and optional task creation from a recommendation (Manager+; persisted recommendations; Free).

venue home shows suggested actions and a readiness summary (open and urgent counts) with links to full **Action Center** and **Venue readiness** pages; the readiness dashboard scores hosted retreats on venue-visible checks only; Action Center lists venue recommendations (including operator-side handoffs) with snooze and dismiss (Venue Manager+; Free; no guest payment detail on venue surfaces).

link a retreat to a partner venue and track where that conversation stands (still talking, proposed, or fully confirmed on both sides).

if you also manage the connected property, a new retreat starts with that property selected, labeled as your venue, above any partner venues. You can still pick a partner venue or a place name. When you manage both, the retreat is one you run yourselves, so one confirmation is enough and no partnership request is sent. If you do not manage the property, you can still choose it; the property confirms, the same way an outside stay works.

a retreat. A copy of a self-run retreat at your venue stays at that venue, and stays self-run when you manage both the program and the property. A copy of a retreat held somewhere else still starts without a place.

save a retreat’s operational setup as an operator-owned blueprint (structure, itinerary templates, milestones, tasks, signup and pricing shape, host welcome, internal ops notes, facilitator role templates, and approved vendor references) without copying guest rosters, payments, signed documents, or survey answers. Managers maintain drafts, publish immutable versions, archive and restore; staff may browse published blueprints only.

a guided wizard to choose sections, preview the sanitized payload, optionally copy draft pricing amounts, name the blueprint, save a working draft, and publish when ready.

managers pick a published immutable version, set new dates/timezone/destination, choose sections to apply, review shifted schedules and pricing confirmations, preview the exact create plan, and atomically create a new unpublished retreat (no participant or payment history copied).

day-by-day schedule for the retreat: sessions, transfers, free time, with control over which items guests see.

an internal countdown checklist (90, 60, 30, 7 days out) that staff see and guests never do.

reserve rooms before every guest has registered, then assign people as they sign up; when the venue is not on the platform yet, create a stand-in venue profile and room inventory until they claim it; assign guests to rooms; when the venue has its own room inventory, an assignment is proposed to the venue and confirmed there (or vice versa); roommate notes stay private to the operator. On **Accommodations & Rooming**, managers configure **lodging at signup** (on/off, venue room availability, named room-type caps) with safeguards when guests already hold or occupy inventory; the public signup page explains when on-site lodging is full but retreat registration stays open.

see and correct each guest's flight details, arrange ground transport, track visa status, manage transfer runs to and from the airport, and optionally turn on a guest carpool board so confirmed travelers can post ride offers and join each other's cars.

send custom questions to guests and read their answers on file.

every guest's balance: pending deposit, on a payment plan, or paid in full.

record an offline payment or refund, share a pay link for guest installment Checkout, and pay the venue deposit or balance by card when the venue has connected Stripe. Card charges on a retreat’s Payments & Finances page and on a one-day event roster sit in a read-only grid (guest, Signup, date and time in Mountain Time, amount, and Paid, Partially refunded, or Refunded), newest first. Opening a row refunds that one payment in full or in part, with an optional reason, and shows the guest’s roster link, a Stripe receipt when one exists, the charge split (charged, platform fee, and what the operator keeps), refund history, the guest’s email, and the Stripe payment id with copy. A full refund of a signup payment removes the guest from the roster; a partial refund leaves them on it. The offline payment form stays on the page.

managers run a guided **Cancel offering** flow on a retreat (standalone events and courses follow the same pattern): record cancellation (closes signup, preserves history), review per-guest refundable card totals, approve a refund batch, and execute Stripe refunds with retry for failures. A cancellation dashboard shows refund status, audit history, and collaboration finance flags when reconciliations or distributions need attention.

managers open **Collections** under Finances to see outstanding retreat guest balances and pending course installments, with links to each retreat’s Payments tab or course Students roster.

on a course’s **Students** tab, managers refund paid course installment card charges; a full refund revokes access tied to that installment.

create operator-wide promo codes (percent or fixed amount off, optional usage limits and date range) from Integrations; guests enter a code when paying for retreats, courses, or events on your account.

per retreat, plan line items (venue, vendors, marketing, travel, and more) with estimated and actual amounts; see guest revenue minus actual costs on the same Payments page.

on Payments & Finances, managers create draft financial scenarios (accommodation mix, costs, fees, cash timing), compare projected profit and break-even, promote a planning baseline with immutable snapshots — without changing live guest billing or ledger entries. A new draft starts the platform-fee assumption at 0.5% and says that matches checkout. A saved draft with another percentage is labeled a historical or custom planning assumption. Changing that assumption does not change checkout.

managers compare an approved baseline snapshot to live guest obligations, collections, refunds, operating budget actuals, and venue settlements with variance analysis and completeness warnings — read-only; never writes ledger or payment data.

the total of everything actually collected from guests, across every retreat.

a read-only view of what this retreat owes its venue partner, kept separate from guest revenue.

after a retreat ends, a summary of guest revenue collected, still outstanding, refunds — minus what was paid out to the venue.

upload general files, a packing list (what to bring / what's provided), and a waiver that tracks who has signed the latest version.

see uploaded flight itineraries, insurance, and other files; view a passport scan only with elevated permission.

create photo albums per retreat, choose whether guests can upload, and share directly from the dashboard.

on **Create New Retreat**, Paid operators can paste notes or write a short description. AI extracts retreat fields, labels source facts vs suggestions, and flags missing information (dates, place, itinerary, packing) instead of inventing it. Review and edit the preview, then create a draft retreat that appears on the operator dashboard. Generate uses a fixed credit cost; approving does not use more credits. The manual form stays available on Free and Paid. PDF upload and event/course AI create are not in this slice. There is no global chatbot.

on **New course**, Paid operators can describe the program in a short brief; AI drafts a preview (modules, lessons, community channels) before you create a draft to edit in the CRM. Approving a preview does not use more credits. The manual form stays available on Free and Paid.

each course opens to a dashboard with cover art, publication status, edit and learner-preview actions, live enrollment and curriculum metrics, paid revenue from recorded installments (or “Free course” when tuition-free), average learner completion, and a vertical curriculum snapshot with module numbers and lesson titles, plus a **Course readiness** panel (Goodness Brain: delivery-aware checks for self-paced, scheduled live, and hybrid paths; recommendations in Action Center; Free).

the operator **Courses** list shows summary counts (total, published, draft, enrollments), search and filters (status, enrollment, price, sort), and horizontal cards with cover art, copyable URL slug, short description, schedule/format/includes metadata, price and enrollment state, **Edit course**, quick links to overview, curriculum, students, and settings, and **Duplicate** (Manager+) to copy a course as a new draft with curriculum, pricing plan, facilitators, and community configuration—without enrollments or payments.

while editing a lesson, title, introduction, lesson body, and content blocks save automatically after a short pause, with a clear status near the lesson title (unsaved, saving, saved, or failed with retry). A **Save now** control next to the status saves pending content immediately without waiting for the debounce. Interrupted sessions can restore a local draft after confirmation; publishing, drip, and visibility stay on **Save lesson settings** only. The lesson body stays aligned with the first text block in order.

create modules and lessons with a **rich text editor** for course descriptions, module intros, lesson introductions, teaching blocks, and assignment/reflection prompts (headings, lists, links, callouts, images); learners read lessons in an editorial layout with serif typography and clear paragraph spacing. Upload a cover photo (or paste an image URL), set free or paid pricing, optional installment schedules with Stripe Connect checkout on **My Learning → Payments** when the operator has connected, link courses to one or more retreats (retreat-only or also open outside the roster), mark **featured facilitators** on the learner dashboard (operator staff or anyone added by name and email — optional headshot upload, label, bio, sort order), and **list publicly** on Discover when published and open for enrollment. Operators can **upload, replace, or remove** audio and download files within lesson blocks (orphaned storage objects are cleaned up when safe) (private storage, signed URLs for learners). Each lesson supports **ordered content blocks** (text, video, audio, downloads, live join, practice, quiz, assignment, reflection, and more). Choosing a lesson type applies starter blocks; operators can add, remove, and reorder freely. Quizzes support single/multiple choice and short answers with auto-grading, optional pass %, retakes, and facilitator review of short answers. Assignments accept text and/or files with submit, approval, or optional feedback flows. Reflections are a private learner journal by default, with an optional shared-with-facilitators mode and clear notice. Facilitators review pending assignments and quizzes from the course Students page.

confirmed retreat guests add themselves without paying; operators add students by name and email (comp access) or share a registration link for self-enroll; learners receive enrollment (and access-unlock) emails; operators with an Integrations email address receive enrollment alerts; first paid installment unlocks lessons (refund revokes access).

per course, operators can enable automatic emails when a lesson unlocks (all drip types), customize subject and intro, preview and send a test, **send a specific session’s email on demand to enrolled learners**, and review delivery history; messages include inline lesson content (not link-only). Live sessions support details-available and 24h/1h reminders when scheduled; learners can opt out on Privacy & data without affecting enrollment or payment mail.

one private community per course with a warm participant **hub**: operator-configurable **spaces** (template packs plus rename, reorder, archive, and visibility), a **feed** of threaded posts with reactions, replies, bookmarks, and reports, a **member directory** sidebar, and lifecycle controls (access window, alumni access, welcome and guidelines copy). Operators manage spaces and lifecycle from the course CRM. *Rollout:* unified data model and a basic per-space channel board ship first; the approved hub UI is tracked in [community-phase1-tracker.md](./community-phase1-tracker.md).

**opt-in direct messaging** after connections ([community-phase2-tracker.md](./community-phase2-tracker.md)); **lesson-linked conversation prompts** so operators attach a discussion prompt to a curriculum lesson (optional calendar open date) from course Community settings; enrolled learners see a **Lesson conversations** strip on the community hub and a threaded **cohort discussion** on the lesson page (distinct from private reflections), with unlock + open-date rules and an operator **Preview** of the participant view.

from one **Community experience** panel per course, retreat, or standalone gathering, operators turn **Discussion feed**, **Member directory**, **Connection requests**, and **Group lobby** (retreats) on or off, plus existing **post-program access** rules; disabled surfaces are enforced in the app and database (defaults stay on for existing programs).

**post-program lifecycle policies** for courses, retreats, and standalone gatherings with community access: close when the program ends, time-limited alumni access, stay open indefinitely, or **alumni-only spaces**; operators set alumni end date, read-only vs posting, custom post-program welcome copy, and one-click **Add alumni spaces**; participants see a clear **alumni transition** banner with links to **My People** and **Messages** (connections and DMs are never removed when community access ends). Alumni-only spaces respect cohort membership and visibility ([community-cohort-privacy.md](./community-cohort-privacy.md)).

optional manual issue and revoke; learners open the digital certificate while it is active.

wherever a registration, signup, invite, Discover, newsletter, or guest-portal link can already be copied, the host can show a QR code for that same link, copy it, enlarge it, or print it. Scanning uses the phone’s normal browser. Guest portal codes open that guest’s existing pages after they sign in.

from a guest’s page, a host can show a short-lived QR code. The guest confirms on their phone, and Goodness Guestbook emails a login link to the address on file. The code is not a login by itself. It expires in 10 minutes and works once.

a host can show a QR code to a signup page for their own email list. The visitor has to check a box before they are added. The Goodness Guestbook newsletter has its own QR code on the marketing site.

each active discount code can be shown as a QR code that opens a page with the code in large type. The visitor still enters the code on the payment page.

send an email to a chosen audience on a retreat, with an option to also post it as an in-app announcement guests can read.

a private one-on-one thread with each guest who reaches out for help.

one conversation with the venue. Messages about an inquiry stay in that thread after the venue accepts and the retreat exists.

staff can remove any message in the guest group chat (the chat itself lives in the guest experience, not on the operator's menu).

create and send one-time marketing emails to your subscriber list with personalization, segmentation, and scheduling. Goodness Paid only; Free operators can still read past campaigns.

manage your email list with tags, sources, and subscriber status tracking. Add people one at a time, import a CSV (`email`, `first_name`, `last_name`, `tags`), or collect via signup forms. Adding subscribers requires Goodness Paid; the list stays readable on Free.

embeddable form for your website or landing pages with customizable tags and source tracking.

multi-step email workflows triggered by events like retreat signup, pre-arrival milestones, or post-event follow-ups. Creating, editing, activating, and enrolling require Goodness Paid.

add email steps, delays, and conditions to create sophisticated nurture campaigns.

use merge tags like {{first_name}} in subject lines and message bodies for personalized outreach.

automatic unsubscribe links in all marketing emails with confirmation pages.

track sends, deliveries, and failures for each campaign and sequence when Goodness Paid includes analytics; names, status, and dates stay visible on Free (engagement tracking coming soon).

a page guests see and register from once the retreat is **Published** in settings (or on create). Marketing holds the public copy and registration switch. A signup link for a draft retreat shows a generic holding page (no retreat details) instead of a 404. Guest portal preview works before publish.

see exactly what guests will see inside their retreat space, read-only, even before the retreat is published. Guests' personal records stay out of the preview.

turn signups on, set capacity, and hold a pending roster spot during paid Checkout so oversell refunds instead of confirming (waitlist auto-promote still planned). When **lodging at signup** is enabled on a venue-linked retreat, guests can reserve a specific lodging unit or a named room type during registration; inventory holds expire with abandoned Checkout like roster holds.

**Products** in the operator Experiences menu and under venue **Finances**: managers create physical or digital SKUs with description, categories, optional SKU, base and sale pricing (calendar sale dates), draft / active / sold out / archived status, optional inventory with an adjustment audit log, and private product images (signed previews for staff). Staff browse read-only. Each operator and each venue owns an isolated catalog. Public shop and Stripe checkout are planned in a later release.

name and brand colors for the operator's public-facing pages.

an Owner of both the retreat business and the property can connect them from Settings. The team, the brand, and the property profile stay separate. Connecting them changes how retreats at this place are created and how you move between the two homes, and the two sides share one Goodness Paid plan and one pool of AI credits. If both already have a paid plan that is still running, the connection waits until one plan has ended. Disconnecting does not change retreats, contracts, or payments that already exist, and it does not copy the subscription. If current or upcoming retreats still use the pair, you confirm that those retreats stay as they are. The sidebar names the property; the name is a link only when you also belong to that property. The account menu offers **Your venue** or **Your programs** next to Switch experience, with the same rule: the item is there only when you already belong to the other record, and choosing it does not add access.

Stripe Connect so the operator’s account receives guest card payments (paid public signup for retreats and one-day events, guest installments, and course installments). Before and after Stripe is connected, Integrations says card processing is 2.9% + 30¢ and that this operator covers it. Goodness Guestbook keeps 0.5% of each eligible guest card charge, on the free plan and on Goodness Paid, and the owner cannot change it. A $100 example shows the charge, card processing, the Guestbook fee, and what is left. Also a calendar feed of retreat dates, a reply-to address edited from Integrations, and an accounting export of guest charges.

a personal landing page for retreats and one-day events: "Manage your retreats, one-day events, guests, and logistics all in one place."

if you belong to one operator, that workspace opens immediately. If you belong to more than one, you pick from photographic cards (logo or a branded monogram) on the same welcome canvas as choosing an experience. Switch operators from the sidebar or account menu. Personal hub and the wordmark always take you back to your own Goodness Guestbook home. Opening one operator never shows another operator's data, and never mixes in venue tools.

choosing another page, a course section, or an event section keeps the sidebar in place and shows “Loading…” over the current page until the next one is ready, with a spinner on the item you clicked.

total retreats, total attendees, revenue collected, and upcoming trips in the next six months, each one click from the detail behind it.

every retreat as a photo card, sorted into Upcoming, Planning, and Past, with a calendar view and a one-click way to start a new retreat.

the same card treatment for standalone events (upcoming, past, drafts, cancelled tabs) with links into each event roster and **Create Event**.

the leader's to-dos across every retreat, soonest due first, with priority and a checkbox to complete.

a running log of what just happened: a registration, a rooming update, a payment, a new itinerary item, a new lead.

jump straight to messaging a group, managing payments, sharing documents, building an itinerary, or viewing reports, for any retreat.

Goodness Free is the manual platform for running retreats, events, courses, bookings, and guest payments, without AI generation and without email campaigns, automated sequences, or adding marketing subscribers. Existing lists and past messages stay visible. Goodness Paid is $19/month and includes those marketing tools plus 100 AI credits per paid billing period on **Billing**. Unused credits expire at the end of that period and do not roll over. A scheduled cancellation shows the date it ends. Retreats, courses, and drafts stay. Stripe Connect on Integrations stays for guest payments. Paid checkout stays off until it is explicitly enabled. When the retreat business and the property are the same retreat center, they share that one plan and that one pool of credits. A partnership with a separate retreat leader does not.

when this operator and a property are the same retreat center, the home page lists the next retreats at that property. Guest revenue stays on its own card. The property's occupancy and leader payments stay in the venue workspace.

lead conversion, upcoming capacity fill, and guest retention (alumni) on the operator Reports page, alongside revenue collected and outstanding.

record operating expenses with optional receipt uploads or CSV import; see guest revenue minus expenses for a date range and export a P&L CSV (separate from the guest-charges export on Integrations).

every request from a leader who wants to host at the venue, with a timeframe (a season, a month, a year), and the ability to accept (which starts a booking), decline, or reply. Inviting a leader who isn't on the platform yet creates their login as part of accepting.

the single list of every stay at the property, filterable by status and by leader: create a booking, see its status (draft, in conversation, proposed, or confirmed), apply a rate package, and open the shared conversation with the leader.

a sidebar destination for partnerships with retreat leaders: pending requests, active operators, shared event counts, and find-or-invite when the venue can manage relationships.

when an outside leader runs the retreat, a booking is confirmed only once both the venue and the leader have said yes, and a change to dates, event space, group size, or place goes to the other side as a proposal that applies when they accept.

once a booking is fully confirmed, see guest names, emails, arrival and departure times, and any dietary needs the guest has shared — exportable, but no guest payment info, passport, or other private guest data.

for each individual booking, set meals, headcount, and service times; this feeds the guest's meal summary and itinerary.

reusable contacts for produce, linen, maintenance, catering, and other local suppliers (no login for vendors).

company name, service type, primary contact, email, phone, and internal notes.

optional recurring drop-off windows per vendor (day of week and time).

log what was ordered, expected delivery, and mark items ordered or received.

a month grid to open up dates the venue is offering, or block dates off (with a reason).

every room the venue owns: name, beds, capacity, amenities, and house notes, with a status of occupied, available, or maintenance.

propose or confirm which guest goes in which room for a booking; a maintenance outage with dates can also block those dates on the calendar.

how full the house is, room-by-room, tracked for the year to date.

the meeting rooms, ceremony spaces, and shared amenities (yoga deck, pool, kitchen) the venue offers besides bedrooms.

managers publish weekly shifts (date, time, role, assignee); everyone on the team sees who is on duty.

each staff member sets recurring availability windows and date ranges when they are unavailable.

assignees ask the team to cover a shift; teammates volunteer; the requester or a manager accepts an offer and the shift reassigns automatically.

the property's own photos (rooms, grounds, food) with captions and an order, a choice of which appear on the public listing, and a cover photo for each booking on the venue's lists. These never land in a retreat's guest album.

the venue's own public page: story, photos, amenities, a rates teaser, and a button for leaders to send an inquiry — including leaders who don't have an account yet. Turning the listing on never publishes a retreat.

managers enter a public website URL; the platform crawls allowed pages and builds a reviewable AI draft of profile fields, room types, and event spaces (one complimentary import per venue; human review before apply; does not publish the listing or import marketing photos).

keep an email list of retreat leaders and event planners. Add people one at a time or import a CSV (`email`, `first_name`, `last_name`, `tags`) on Goodness Paid; the list stays readable on Free.

reviews written by operators and guests after a confirmed stay, with the ability to reply (not edit) each one.

the paperwork between the venue and a leader (or operator-only participant and facilitator agreements): upload a file or **generate a draft with AI** on the venue's Goodness Paid plan, prefill from retreats and partnerships, edit sections, preview or print to PDF, track draft / ready for review / sent / signed, tied to a relationship and optionally one retreat. Those credits are the venue's, or the shared retreat-center pool when the operator and venue are the same place. A partnership does not spend the retreat leader's credits.

one conversation with each operator. It starts on an inquiry and continues on the booking after the venue accepts, with the earlier messages still there. No guest messaging and no group chat live here — those stay in the guest experience.

name, address, place description, timezone, and branding for the public listing.

an Owner of both the property and the retreat business can connect them from Settings. Outside leaders stay on Operator Relationships, contracts, and inquiries. The sidebar names the programs; the name is a link only when you also belong to that operator. A new retreat can start with those programs selected, and with “we run this ourselves” checked only when you manage both. You can turn that off, or pick another leader. Connecting them shares one Goodness Paid plan. If both sides already have a paid plan that is still running, the connection waits until one of those plans has ended. Disconnecting does not delete bookings, contracts, or the plan that was already paid.

the same Free and Paid plans as an operator, on the venue's own Billing page. Owners and managers can subscribe or open the billing portal. Staff can view the plan and remaining credits. Canceling keeps the venue's bookings, contracts, and courses.

before and after Stripe is connected, Settings says card processing is 2.9% + 30¢ and that this venue covers it. Goodness Guestbook keeps 0.5% of each eligible guest card charge, on the free plan and on Goodness Paid, and the owner cannot change it. A $100 example shows the charge, card processing, the Guestbook fee, and what is left.

a name and phone number guests see once their retreat is published.

invite and manage who can log in for this venue, and their role (Manager, Staff, or custom). Owners choose which roles can view sensitive guest details and which can correct participant data, with the same Owner protections as the operator.

"Manage your space, retreats, one-day events, and relationships with retreat leaders," with one main action: add availability.

if you belong to one venue, that workspace opens immediately. If you belong to more than one, you pick from photographic cards (logo or a branded monogram) on the same welcome canvas as choosing an experience. Switch venues from the sidebar or account menu. Personal hub and the wordmark always take you back to your own Goodness Guestbook home. Opening one venue never shows another venue's data, and never mixes in operator tools.

find a retreat, a leader, or an inquiry from one search box.

a bell that flags a new inquiry, a stay waiting on the venue's confirmation, a change a leader proposed, a contract waiting for a signature, or a new partnership request.

short guides and step-by-step tutorials for running the venue, plus a way to book time with the Goodness Guestbook team.

venue tools sit in collapsible sections (Overview, Bookings & Calendar, Venue & Spaces, Operations, Relationships, Finances) with Marketing, Billing & Plan, and Settings as top-level links; the section for the current page stays open while you work inside it.

choosing another page, a course section, or an event section keeps the sidebar in place and shows “Loading…” over the current page until the next one is ready, with a spinner on the item you clicked.

confirmed retreats (plus how many are still in inquiry or draft), total guests across every retreat, projected revenue for the year, and the current occupancy rate.

when this property and a retreat business are the same center, the home page lists the next retreats that business runs here, separate from outside leaders. Occupancy and leader payments stay on their own cards.

the next one-day events at the property as photo cards with registration counts and links into each event roster.

the next retreats booked at the property, with dates, guest count, the leader's name, and where that booking stands.

a month view showing booked retreats, one-day events, and blocked-off dates.

the newest requests from leaders who want to book.

a simple breakdown of occupied, available, and maintenance rooms.

the same yearly revenue projection, broken out by month.

which operators book the most, ranked by retreats and guests.

the venue's own price list: per room, per guest, or per stay, and what's included; applying one to a booking sets that booking's amount owed.

the yearly revenue projection (confirmed bookings only) with a monthly breakdown, the amount owed on each booking, a place to record deposits or balances received, and a spreadsheet download for the year. This is entirely separate from what guests pay the operator, and it doesn't have card processing on the venue's own account in this version.

when an operator enables a revenue split on a one-day event and allows visibility, venue staff can open that event to see guest revenue collected and the venue's percentage share (planning view; not guest checkout).

upload operating expenses (receipt or CSV), see payments from retreat leaders minus expenses for a date range, and export a P&L CSV (separate from leader invoice tracking on Payments).

on a phone or tablet browser, add Goodness Guestbook to the home screen for a standalone window with the same sign-in and **Me** experience (no separate app store build).

a QR code from the host opens registration, the guest’s retreat or course home, payments, documents, surveys, community, or live sessions in the browser. A sign-in help code asks before emailing a login link and never signs the guest in by itself.

`/me/privacy` consolidates private profile links, community discoverability summary, marketing list unsubscribe, a per-grant data-sharing table with withdrawal, JSON **Download my data**, and password-confirmed account deletion with clear retention notes.

choosing another page in the personal hub, a retreat, a one-day gathering, or a course keeps the surrounding menu and shows “Loading…” over the current page, with a spinner on the menu item or course tab you clicked, until that page is ready. Marketing, sign-in, choose, and other pages without a sidebar show the same panel.

a welcome, then **My Experiences** (upcoming and past retreats and one-day events as cards with a cover, dates, place, roster or registration status, and payment progress when money is owed; enrolled courses on the same home dashboard with cover, enrollment status, and links into My Learning) and **Explore Goodness** (a card with a link to the public Discover catalog to browse new retreats, events, and courses). When the participant has no registrations yet, **Explore Goodness** appears right under the welcome line and empty experience sections are omitted; once they have enrollments, **My Experiences** comes first and empty past sections stay hidden on the home page (full history remains on My Retreats and My Courses). Hub nav includes My Courses, **Discover**, and Payments.

photo, name, email, phone, address, clothing size, and directory intro, with edit on My Profile.

the operators and venues this person knows through retreats plus any they save from directory search, with the full list on My Connections; search spans every operator and venue on the platform, guests can add hosts to My Connections, and each connection opens a offerings page (public Discover retreats and courses for that host or venue).

opt-in program member directories (course, multi-day retreat, or standalone one-day event) with separate visibility and “open to connect” choices; voluntary connection requests, in-app notifications, and a cross-program list at `/me/people` after both people accept. Standalone events use `/me/gatherings/{eventId}/community`; retreats use Community → Members; courses use the community member directory page.

private one-to-one threads between accepted connections at `/me/messages`, opened from People or notifications; unread counts, block/report/remove controls; removing a connection hides the thread from the inbox and the old thread URL is not found; no operator browsing of guest DMs.

every retreat on the roster and every standalone event registration, plus any retreat this person facilitates without a roster row; one-day events open a simple registration summary with **Your preparation** (registration fields, payment on paid events, waiver, optional forms) scoped to that registrant only.

at `/me/payments`, the card charges this person paid through Goodness Guestbook, newest first: the date, the retreat or one-day event (plus the offering or installment when there is one), the amount, and the status. The retreat name opens that retreat; a one-day event name opens that event. Offering, installment, and course labels stay as text beside the name. A receipt link opens when Stripe stored one. The Guestbook application fee is not listed as its own charge.

My Learning dashboard at `/me/courses`; each enrolled course opens to a participant landing with cover hero, **Your learning checklist** when Brain has actionable prep (payment, lessons, live sessions, resources—no readiness percentage), **Continue learning**, journey or module exploration, and community previews; lessons use a constrained reading column, distinct teaching vs reflection/assignment blocks, curriculum sidebar on desktop, and a drawer on mobile — driven by real modules and blocks (including day-style journeys when the curriculum is structured that way). Per-course player at `/me/courses/[enrollment]` with hero, tabs (**Dashboard** back to `/me` for retreats and events, plus course, community, live sessions, resources, announcements), module outline, lesson URLs, and a featured teaching team when the operator marks facilitators as visible; the My Learning shell sidebar includes the same **Dashboard** link; operator five-color learner theme with per-course override; **Community** tab moving to the approved warm hub (spaces, feed, directory) per [community-phase1-plan.md](./community-phase1-plan.md); digital certificates when issued.

the retreat summary sits beside the registration card. The account step and the host’s questions stay as the host configured them. The same person account created from sign-in or from a course enroll link is the one used here. After signup (free or paid), a welcome screen confirms the booking, shows **Your preparation** when it is ready, and opens the retreat or one-day event home—not a generic profile page.

a personal greeting, the retreat's cover photo, and a countdown to departure (or "in progress" once the trip has started).

a personal checklist on the retreat welcome page (forms, waiver, payments, travel, accommodation, schedule) grouped as To do, Coming up, and Complete with links into existing guest flows—no readiness percentage and no duplicate data entry.

one tap to the itinerary, travel details, room assignment, or packing list.

total paid, percent complete, and each installment's due date or paid date, with a pay button when a payment is due.

flight route, transfer arrangement, and passport/visa/insurance status at a glance.

photos of fellow confirmed guests and facilitators, with a link into the full group directory and the group chat.

guest-visible facilitators highlighted on the welcome page (profile headshot, role label, and optional bio), with a link into the group directory. Hosts add them on the retreat **Facilitators** page (operator staff or external teachers by email) and can upload the headshot when saving.

the guest's own dietary preference and allergy info, with a link to edit.

which required documents are uploaded or signed, and which are still missing.

a note that the group space stays open after the trip ends, to keep in touch and share photos.

a waitlisted guest sees they're on the waitlist and can still read announcements and resources; a canceled guest keeps their booking history and signed waiver to read. Until the host publishes the retreat, host pages say so plainly, and guests can already fill in their own details.

the day-by-day schedule the host has published, once the retreat is open, with the venue's meal times on each day.

the guest enters their own flight details, sees the transfer plan the host has set, sets or reads their own visa status, and when the host enables it, posts carpool offers or ride requests and joins other guests' shared rides.

read-only view of the guest's assigned room, its amenities, house notes, and roommate first names.

what to bring and what's provided.

any general documents the host has chosen to share.

the guest's own balance, the full installment schedule, receipts for anything already paid, and a pay button for the next amount due. In a group booking, each person only ever sees their own charge (or that it was paid by someone else on their behalf).

name, photo, contact info, clothing size, activity tags, and whether the guest wants to appear in the group directory (with a short intro).

dietary preferences, allergies, medications, and emergency contact — private until the guest chooses to share it with the host.

upload a passport, flight itinerary, and travel insurance (buy coverage via an optional partner link, save provider and policy number, and upload the certificate); sign the retreat's waiver; upload any other personal files.

a single warm place per retreat or event: **Feed** (threaded discussions in operator spaces), **Lobby** (casual group chat — same `group_chat_messages` backend as today, not migrated into posts), and **Members** (directory with opt-in profiles and facilitator labels). Courses use the same hub pattern without Lobby unless the operator enables it for a linked retreat. Lifecycle respects operator access windows and alumni access.

today: **My Group** for confirmed, opted-in guests and visible facilitators; guests can leave or rejoin. Phase 1 moves this into **Members** inside the hub with the same privacy rules.

today: host announcements, private help thread, and group chat from the top bar. Phase 1 keeps announcements and help; group chat becomes the **Lobby** tab inside Community while preserving message history.

view retreat photo albums, and upload their own photos where the host allows it.

after the trip, directory, lobby chat, photos, and closing notes stay available when the operator allows alumni access.

once the trip is over, a guest can review the venue and, separately, the host. The venue can reply to its review but never change it; the host review goes only to the host.

the host's contact info, the venue's front-desk contact (once published), a private message line to the host, and a separate Goodness Guestbook support contact for platform issues.