> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/portal-overview/portal-modules-overview.md). # Portal Modules and Features — Overview Each section of the Member Portal is powered by a specific **Module**. Modules group the type of content you can publish (blog posts, events, directory cards, schedulers) and they map to the left-hand navigation members see on the portal. This article is a quick reference to every module — what it shows members, where to configure it, and which articles to read for setup detail. > **Note**: Each navigation item is tied to a specific engine and cannot be repurposed. The navigation is set during onboarding. ### Module reference | Module | Component | What members see | Configured in | | --------------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | **Home** | Home page | Aggregated feature page — highlights announcements, bookings, and content | Aggregated automatically; set up during onboarding (not via Manage Pages) | | **News / Blog** | Content | Reverse-chronological list of blog posts; categories filter | ENGAGE > Manage Blogs (or equivalent); ordered by Posting Date | | **Events** | Events & Promotions | Upcoming events, ticket availability, *Join Waitlist* on sold-out (MP3.0). A **List/Calendar** date-forward layout is available as an alternative to the default grid (good for high event volume) — the layout is set per club; contact your Account Manager to switch it. | SELL > Manage Events | | **Dining** | Directory Location | Restaurant directory cards (informational, bookable, hybrid) | ENGAGE > View Directory + schedulers; reservations sync from OpenTable / SevenRooms | | **Spa & Wellness** | Directory Location | Spa directory cards (bookable via native scheduler or Book4Time) | ENGAGE > View Directory + scheduler/integration setup | | **Appointments** | Directory Location | Service directory cards with scheduler bookings | ENGAGE > View Directory + SELL > All Schedulers (Peoplevine Native Scheduler) | | **Activities** | Directory Location | Activity cards such as fitness classes | ENGAGE > View Directory + a scheduler — **Book4Time or the Peoplevine Native Scheduler** | | **Workspaces / Meeting Rooms** | Directory Location | Desks, offices, and rooms bookable by time slot | ENGAGE > View Directory + SELL > All Schedulers | | **Staff Directory** | Directory Location | Team profiles ("Meet the Club") | ENGAGE > View Directory — a Directory Profile (a Form can be added to it) | | **Concierge** | Concierge | One-on-one chat with the club, via push notification or SMS | Separate module | | **Club Directory (community)** | Directory Location | Member directory (opt-in community feature) | Enabled by Peoplevine; rolled out per-club | | **Club Benefits** | Directory Location | Programs, perks, partner benefits as cards | ENGAGE > View Directory | | **Guest Passes** | Guest Pass | Available passes; share-with-guest action | Membership Program > Perks (allocation); Members > Manage Vouchers (manual issue) | | **My Schedule / My Bookings** | Account | Member's upcoming reservations and event registrations | Auto-populated from member's bookings | | **My Account > Personal Details** | Account | Editable profile fields (name, email, phone, DOB, etc.) | Profile questions configured in an associated form | | **My Account > Memberships** | Account | Active memberships, digital ID card, pay/manage actions | Auto-populated from membership records | | **My Account > Wallet** | Account | Payment methods, **House Credits** (dedicated tab — credits grouped by redemption type + expiry), house account, vouchers, tickets | Stripe / GoCardless tokenization | | **My Account > Billing** | Account | Dues, orders, invoices | Auto-populated from billing engine | | **Nominate a Member** | Form / CTA | Direct nomination form | Form configured in admin; direct link `/account/memberships/nominate` | | **Terms & Privacy (footer)** | Page | Linked Terms of Use and Privacy Policy | ENGAGE > Manage Pages with SEO keyword `terms` or `privacy` | ### How content lands on the portal Each piece of content (blog post, event, directory card) is tied to a **Module + Category + Subcategory** combination. That combination is what makes it appear under the right tab and sub-navigation on the portal. See: [How to Set Up and Use Categories](/products/portal-overview/setup-categories.md). For Directory Cards specifically, the **type** of card (Informational, Bookable, Form, Hybrid, CTA) controls what happens when a member taps the card. See: [What are Directory Profiles](/products/portal-overview/directory-profiles-overview.md). ### Content ordering Different modules use different ordering rules: | Content type | Default order | | ------------------- | --------------------------------------------------------------------------- | | **Blogs** | Newest Posting Date first; older posts lower | | **Events** | Soonest start date and time first; past events drop off the *Upcoming* view | | **Directory Cards** | Manual `Order` value per card (0, 1, 2, …) within each Module | > **Tip**: Keep `Order` values **unique within a Module** so the display order is predictable. ### Membership status gates the portal Membership status gates the **entire portal**, not just individual modules — a member needs portal access before any module is reachable. A portal can be configured to accept non-members for certain modules (for example, letting registered CRM profiles browse the events module). You cannot grant one membership program access to a whole module while barring another at the module level. Per-program access is controlled at the **Directory Profile, scheduler, event, or ticket** level. For example, all members may have access to the events module, but per event or ticket you can make it available only to certain membership programs. See: [How Members Get Access to the Portal](/products/portal-overview/member-portal-access.md). ### Best Practice * **Use a separate Subcategory per genuinely-different audience experience.** Don't lump *Fine Dining*, *Casual Dining*, and *Bar Snacks* under one *Dining* sub-navigation — let members filter. * **Match Subcategory titles to how members talk** (e.g., *Spa Treatments* not *Spa-Tier-Premium*). ### What Happens Next * **On the member side**: Each module behaves according to its content + categories + the member's status. * **Next step**: [What are Directory Profiles](/products/portal-overview/directory-profiles-overview.md) · [How to Set Up and Use Categories](/products/portal-overview/setup-categories.md) · [How Members Get Access to the Portal](/products/portal-overview/member-portal-access.md). *Last updated: 2026-06-11* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/portal-overview/portal-modules-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.