> 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/glossary.md). # Glossary *** ## How to Use This Glossary * **Bold terms** are the canonical name used in the platform * **"Not to be confused with"** callouts highlight terms that are easily mixed up * **Where you'll see it** tells you which Control Panel module or context uses the term * Terms are grouped by domain, not alphabetically — read the section relevant to your work *** ## People and Accounts ### Customer Every person who has an account is a **Customer**. This is Peoplevine's universal person record, storing contact info, demographics, transaction history, and engagement metrics. > Not to be confused with **Member** (a Customer who holds an active membership) or **User** (a staff account for the Control Panel). Where you'll see it: **CRM** module, everywhere across the platform. ### Contact A Customer with minimal engagement — typically just a newsletter signup or a form submission. They exist in the system but haven't transacted or joined anything. > Think of it as the lightest type of Customer record. ### Prospect A person who has shown interest in membership (attended a tour, downloaded a brochure, requested information) but hasn't submitted an application. ### Applicant A person who has submitted a membership application and is awaiting review. Once approved and enrolled, they become a **Member**. ### Application A multi-step enrollment form flow that gates access to membership. Applications are assembled from individual forms, support couples membership (storing spouse data as a separate CRM record), and include configurable instructions and confirmation messaging. Once an Applicant is approved **and** enrolled, they become a Member — approval alone does not automatically enroll them. > Not to be confused with **Form** (a standalone data-collection page). An Application is a structured multi-step process built from one or more Forms. Where you'll see it: [**ENGAGE > Survey & Forms > Manage Applications**](https://control.peoplevine.com/survey/groups). > **Note (Pro Dash):** ENGAGE > Surveys & Forms > Survey Applications. ### Form A standalone data-collection page used to gather information from members, guests, or prospects. Forms support multiple question types (short/long answer, dropdown, radio, checkbox, date picker, file upload, signature, payment capture, and more), CRM field mapping, attribute tagging, and customizable branding. Each form has a direct link that can be shared or assigned a **Vanity URL**. Forms can be attached to an **experience** (replacing the default form for Contact Us, Guest Pass, Nominate a Member, etc.) or used independently via a direct link. Response modes: **One Response**, **Multiple Responses**, or **Edit Enabled**. > Not to be confused with **Application** (a multi-step gated enrollment process built from one or more Forms). A Form is a single data-collection page. > **Note**: The **Contact Us** form is a standard form loaded for every new account. It should always be set to **Multiple Responses** — setting it to Edit Enabled causes data display issues. Where you'll see it: [**ENGAGE > Survey & Forms > Manage Forms**](https://control.peoplevine.com/surveys). ### Member An umbrella term for any Customer with an active membership status — including both paying members (subscription-based programs) and comped members (ID Card / free programs). Members get special access, pricing, perks, and benefits defined by their **Membership Program**. Within both paid and free programs, you can set up a primary and sub-member structure. The system tracks `isMember` and `wasMember` flags on each Customer. > Not to be confused with **Customer** (the broader person record) or **Sub-Member** (a dependent/family member on someone else's card). Where you'll see it: **MEMBERS** module. > **Note (Pro Dash):** REWARD module. ### Guest A non-authenticated visitor, or a member of a different location who is visiting. Guests do not have access to the member portal. > Not to be confused with **Prospect** (who has shown interest in membership). ### Sub-Member A secondary person linked to a primary member's card — typically a spouse, child, or family member. They share the primary member's membership but have their own card (tracked via `parent_membership_card_no`, with `isPrimary` flag on the primary card). Sub-members have the **same access rights** as primary members — the only difference is that their member status is dictated by the primary member's status. In a membership that allows sub-members, such as a **Family Membership**, the sub-member is added after the primary member is enrolled. Sub-members inherit access (including Global Network access, when applicable) and may receive perk allocations (e.g., guest passes) if configured on the membership program. Stipend perks can be scoped to primary-only or shared with sub-members. A sub-member can optionally charge purchases to the parent member's house account (controlled by a checkbox on the membership card). If the primary member's status changes (e.g., billing fails, suspension, cancellation), the sub-member's status changes accordingly and they also lose access. Sub-members never see a payment option on the Failed Dues Paywall — payment must be handled by the primary account holder. > Also called **Dependent** or **Family Member** in various contexts. In member exports, sub-members are identified by `primary_membership_card_no` containing their primary's card number (primary members always have this field = 0). > **Swapping primary and sub-member roles:** There is no direct swap function. The recommended process is: cancel the sub-member's membership, remove the parent-child relationship, enroll the former sub-member as a new primary, then enroll the former primary as a sub-member under them. Note: the "Sub Member" tag may persist on the membership card after re-enrollment — archiving and re-enrolling is the only way to clear it. ### User A **staff account** for the Control Panel. Users are operators and administrators — they manage the platform. This is completely separate from Customers/Members. > Critical distinction: **User** = staff. **Customer** = people in the CRM. They are different entities with different authentication, different permissions, and different API token types. ### Operator Informal term for a User (staff member) who is actively working in the Control Panel. Used in workflow documentation to describe the person performing administrative actions. ### Affiliate A referral partner who earns commissions on member spend and dues. Tracked separately from regular Customers. *** ## Membership System ### Membership Program The **template** or **plan definition** for a membership — e.g., "Gold Membership", "Platinum Annual", "Student Pass". It defines pricing, billing frequency (monthly, quarterly, semi-annually, annually), benefits, sub-member allowance, global network, and ID card design. Programs also configure initiation fees, proration, optional service fees, and enrollment method (**Admin-Only** or **Public**). Members don't hold a program directly; they hold a **Member Card** that links them to a program. **Billing Types** (set at program level): * **Paid Subscription** — recurring billing based on the service plan options (most common) * **Add-On Feature** — upsell membership/access when a member subscribes to another membership * **ID Card** — free, no billing. Use for **lifetime memberships**: charge the member one time via virtual POS, then enroll in the ID program without a subscription. Do not use $0 subscriptions — they cause billing engine issues. If the client requires deferral amortization, use a subscription-based program with the next billing date pushed far into the future instead. * **Temp Guest** — temporary guest access (e.g., hotel guest), excluded from total member count > **Add-On Feature vs Service**: An Add-On Feature is a membership program — the member gets a membership card. A **Service** is a standalone recurring billing item with no membership card, created in SELL > Manage Subscriptions. For **Couples Memberships**, the program's "allowed sub-members" count is set to 1, permitting one spouse/partner. The sub-member is added after enrollment or the primary member, not during — the enrollment flow creates the primary card first, then the operator links the spouse from the membership card screen. Enrollment method determines how members join: * **Full-Service Admin Only** (recommended) — enrollment happens via the Control Panel or through the Application flow. The public cannot self-enroll. * **Public** — members can sign up directly from the portal or website. If an Application is assigned, they must complete it first (good lockdown). Without an application, anyone can join and pay. > Also referred to as **Membership**, **Membership Tier**, **Membership Plan**, **Membership Level**, **Membership Type**, or **Subscription Plan** in various contexts. These all refer to the same thing: the program definition. When a client or team member says "membership" on its own, they almost always mean the Membership Program. Where you'll see it: [**MEMBERS > Memberships > Manage Membership Programs**](https://control.peoplevine.com/admin_membership_list.aspx) in the Control Panel. > **Note (Pro Dash):** REWARD > Memberships > Membership Programs. ### Member Card The **individual enrollment record** that links a specific Customer to a specific Membership Program. When someone "joins a membership," what actually happens is: a Member Card is created for them. The card has its own ID, join date, renewal date, status, and (for family memberships) a reference to a parent card via `parent_membership_card_no`. Membership IDs can be auto-generated (5-character numeric string by default, configurable via `member_id_length`) or manually defined. > Not to be confused with **Membership Program** (the template). The Program is "Gold Membership." The Card is "Jane Doe's Gold Membership, active since Jan 2024." Card Statuses (7 validated): **Active**, **Pending**, **Suspended**, **Failed** (auto-set), **Expired**, **Cancelled**, **Archived**. Additionally, **Failed** is auto-set by the billing engine when a recurring payment fails. It triggers the Failed Dues Paywall at portal login; the system retries at Day 3 and Day 7. Best practice: never manually set a member to Failed — use Suspended instead to restrict access, or generate an invoice on the failed subscription to return the member to Active. > **Pending** removes access until the start date or next billing date. **Failed** triggers the Failed Dues Paywall at portal login; the system retries at Day 3 and Day 7. **Upgraded**, **Downgraded**, and **Archived** are subscription statuses. See [Status Code Reference](/status-codes-reference.md). ### Membership Subscription The recurring billing record attached to a Member Card. This handles the automatic charges for membership dues — billing runs daily based on each member's next billing date. It's a specialized type of subscription — distinct from the general-purpose **Subscription** entity used for services. > Not to be confused with **Subscription** (the general-purpose entity for recurring services). ### Dues The recurring payment a member owes for their membership. Charged per the billing cycle defined in the Membership Program. Supported frequencies: `monthly`, `quarterly`, `semi-annually`, `annually`. > "Charge dues" and "charge membership" mean the same thing in Peoplevine. ### Initiation Fee A one-time charge assessed when a member first enrolls in a Membership Program. Configured at the program level alongside dues pricing. Initiation fees may be routed to a different payment processor than ongoing dues (e.g., ACH via GoCardless for high-value charges). ### Check-In A facility entry scan — the record created when a member (or guest) scans or taps their card at a location. Check-ins are timestamped activity records used for tracking facility usage and member engagement. Check-in records include a **Scan Type** that indicates how the check-in was created: **"user"** for manual scans via the check-in app (includes location data) or **"Arrived"** for check-ins auto-created by integrations such as SevenRooms (may not include location data). Where you'll see it: [**MEMBERS > Check-ins > Recent Check-Ins**](https://control.peoplevine.com/admin_membership_card_activity.aspx). > **Note (Pro Dash):** REWARD > Memberships > Check-In. ### Reward Program A loyalty tier within the membership system. Defines point multipliers, minimum points for tier qualification, and rank. Members earn points through **Loyalty Activities** and progress through reward tiers. Where you'll see it: [**MEMBERS > Rewards > Manage Reward Programs**](https://control.peoplevine.com/loyalty/programs). > **Note (Pro Dash):** REWARD > Loyalty > Rewards Programs. ### Lifecycle Stage A CRM-level classification that tracks where a person is in their relationship with the organization. The system auto-updates this field based on membership status changes — no manual configuration needed. | Value | Stage | | ----- | --------- | | 1 | Contact | | 2 | Prospect | | 3 | Applicant | | 4 | Guest | | 5 | Member | The system sets this automatically based on the data it has on the person. When a membership card is activated, the stage updates to Member (5). On cancellation or reactivation, the stage changes accordingly. Where you'll see it: [**CRM > View People**](https://control.peoplevine.com/customers) (Lifecycle Stage filter dropdown). ### Loyalty Activity A rule that defines how members earn points — e.g., "10 points per dining visit," "50 points for completing a survey," "5 points per dollar spent." Each activity has a type, point value, and activation period. *** ## Commerce ### Order A collection of items being purchased by a Customer. An Order can contain products, event tickets, appointments, or subscriptions as line items. It is the container for a purchase. > Not to be confused with **Transaction** (the payment record) or **Invoice** (the bill). One Order can generate multiple Transactions (e.g., split payments, retries). Where you'll see it: [**SELL > Sales Dashboard > View Orders**](https://control.peoplevine.com/orders). ### Order Item A single line item within an Order. Each item references a specific Product, Event Ticket, Schedule Booking, or Subscription, with its own quantity, price, tax, discount, and status. > Also called **Line Item**. ### Transaction A single payment attempt or record. This is the **financial event** — it records the amount, payment method, processor response, and outcome. When a customer pays, that creates a Transaction. Key date fields: **Charged On** (when the charge was initiated), **Paid On** (when payment was confirmed — same as Charged On for direct charges, but different for invoice payments), **Matched On** (when reconciled with a payment batch), **Modified On** (when last updated). > Not to be confused with **Order** (what they're buying) or **Invoice** (the bill). A Transaction is the answer to "did the money move?" Where you'll see it: [**SELL > Sales Dashboard > View Transactions**](https://control.peoplevine.com/transactions) (`/admin_transactions.aspx`). > **Note (Pro Dash):** SELL > Transactions > View Transactions. ### Invoice A bill for an amount due — an **unpaid** Transaction. When Peoplevine generates a charge that hasn't been collected yet, it creates an Invoice. Once paid, it becomes a completed Transaction. Peoplevine supports two invoice PDF formats, selectable under **Platform Settings**: * **Version 1.0** — basic PDF receipt; sufficient for most domestic clients. * **Version 2.0 (Regional Requirements)** — an enhanced, Peoplevine-managed invoice format. Supports regional tax breakdowns, QR codes, multi-language translations, and custom field visibility. Recommended for international clients and any club requiring itemized tax detail. To enable or customize it, contact your Account Manager. > Not to be confused with **Receipt** (proof of completed payment). Invoice = "you owe this." Receipt = "you paid this." ### Receipt Proof of a completed payment. Generated after a Transaction is successfully processed. ### Product A physical or digital item for sale in the catalog. Has a SKU, price, stock level, brand, category, and visibility settings. Products can have **Add-Ons** (optional enhancements) and can be set up for recurring purchase via **Product Subscription**. Where you'll see it: [**SELL > Catalog > Manage Products**](https://control.peoplevine.com/commerce_products.aspx). > **Note (Pro Dash):** SELL > Ecommerce > Products. ### Service A **standalone recurring billing item** — the underlying billing mechanism in Peoplevine. A Service defines the title, price, auto-renewal rules, trial options, initiation fees, and billing frequency. Examples: "Wine Locker Monthly", "Premium Parking", "Gym Pass." Memberships contain a service (which is how the membership is billed), but services can also be sold independently without a membership wrapper. When subscribing a person, the **Service** tab shows standalone services; the **Membership** tab shows membership programs. > Critical distinction: A **Service** is the plan definition. A **Subscription** is a person's active enrollment in that Service. Think of Service as the menu item and Subscription as the customer's order of that item. Where you'll see it: [**SELL > Catalog > Manage Subscriptions**](https://control.peoplevine.com/services). > **Note (Pro Dash):** SELL > Transactions > Services > Manage Services. ### Subscription A Customer's **active recurring billing enrollment** in a Service. When someone signs up for a Service, a Subscription record is created. It tracks auto-charge settings, billing frequency, rate, next billing date, renewal date, and remaining payments. > Not to be confused with **Service** (the template) or **Membership Subscription** (the membership-specific variant). Statuses: Active, Pending/Paused, Failed, Suspended, Upgraded (reporting-only), Downgraded (reporting-only), Expired, Cancelled, Archived. > **Failed** triggers automatic payment retry at Day 3 and Day 7. Cycle anchor dates persist through retries (e.g., a first-of-month billing date remains first-of-month). Only **Active** and **Pending** subscriptions with a future next billing date are processed through recurring billing. **Archived** hides from customer view; still shows on CRM profile and in reporting. Where you'll see it: [**SELL > Sales Dashboard > View Subscriptions**](https://control.peoplevine.com/subscriptions). > **Note (Pro Dash):** SELL > Transactions > Subscriptions. ### Gift Card A stored-value instrument with a balance. Has a code, certificate number, face value, and remaining balance. Can be purchased in Orders and used as a payment method. Gift Card is one of four **Certificate Types** available under SELL > Gift Cards + Stipends: **Gift Certificate**, **Reward Certificate**, **Stipend**, and **Deposit**. During house account billing, gift cards apply **first** before cards are charged. If the subsequent card charge fails, the gift card deduction is **reverted** — the balance is returned to the member's account and no partial payment is recorded. This reversion behavior was introduced to prevent scenarios where gift card funds were consumed but the overall payment remained incomplete. > **Gift cards cannot be set as the payment method for recurring subscription billing.** Subscriptions require a persistent payment method (credit card, ACH, etc.). To apply a gift card toward membership dues, set the subscription billing to Invoice mode, then select Gift Card as the payment type when processing the invoice. > Not to be confused with **Voucher** (a digital benefit like a guest pass or drink ticket). Gift Cards hold monetary value. Vouchers are non-monetary perks. Where you'll see it: [**SELL > Gift Cards + Stipends > View All Issued Certificates**](https://control.peoplevine.com/giftcards). ### Coupon A promotional code or offer that applies a discount at checkout. Coupons have usage limits, expiration dates, and rules for what they apply to. > Not to be confused with **Discount** (a price reduction that can be applied manually or automatically). A Coupon is a specific code; a Discount is the broader concept. *** ## Perks and Benefits ### Voucher A digital benefit issued to members — guest passes, drink tickets, complimentary items, day passes. Vouchers have an issue count, redemption count, and expiration. They are **non-monetary** — they represent a specific benefit, not a dollar amount. > Not to be confused with **Gift Card** (which holds monetary value). Vouchers are perks; Gift Cards are payment instruments. Where you'll see it: [**MEMBERS > Vouchers > Manage Vouchers**](https://control.peoplevine.com/vouchers). > **Note (Pro Dash):** REWARD > Vouchers > Digital Vouchers. ### Stipend A membership perk that provides a recurring or one-time monetary credit — e.g., "$50/month food & beverage credit." Stipends are issued on a schedule defined by the perk configuration and can be scoped to the primary member only or allocated to sub-members too. > Not to be confused with **Gift Card** (a stored-value payment instrument purchased separately). A Stipend is an entitlement issued automatically as part of membership. ### Guest Pass A specific type of Voucher that allows a non-member to access a facility or event. Issued to Members as a membership benefit. Guest passes use "virtual pass" issuance — records materialize upon issuance, with configurable daily or monthly limits and adjustable release times (e.g., 4 a.m. instead of midnight) to prevent gaming. Guest pass lifecycle terminology: | Term | Meaning | | --------------- | --------------------------------------------------------------- | | **Issued** | Pass allocated to the member (as part of their membership perk) | | **Transferred** | Member sent the pass to a guest | | **Redeemed** | Guest pass scanned at check-in | > The day the guest pass is transferred is the day it will be redeemed — the pass expires at the end of the day. > When a guest pass is transferred, a guest CRM profile is automatically created. The guest profile shows the pass under **Received Passes** and links back to the member under **Linked People** ("guest of \[Member Name]"). > To view all transferred passes: **MEMBERS > Manage Vouchers** (or **REWARD > Manage Vouchers** in Pro Dash) → click into the voucher type → **TRANSFERRED VOUCHERS** section. Most recently transferred passes appear first. This section is not exportable. > To view redeemed passes (scanned at check-in): [**MEMBERS > Activity Report**](https://control.peoplevine.com/admin_membership_activity.aspx) (or [**REWARD > Activity Report**](https://control.peoplevine.com/admin_membership_activity.aspx)). Sort by date range to see total visits per member and guest. > **Note on portal access:** Some clients allow public access to their portal. If enabled, a non-member can enter their email and the system will prompt them to create an account. Contact the Peoplevine team to configure public portal access. ### Perk The general term for any benefit included in a membership — vouchers, discounts, guest passes, etc. Perks are what make membership valuable. Key configuration concepts: * **Perk Date** — a configurable field on the member card that controls when daily/monthly/annual perks begin issuing. If the perk date is changed after enrollment, previously issued perks are not clawed back — the member may receive a double issuance. Handle with care during backdated enrollments. * **Vendor Key Discount** — a discount code (e.g., a Micros discount key like "20%") attached to a membership program. When the member is identified at the POS, the integration passes this key to apply the correct pricing tier. * **Expiry Window** — each perk defines a validity period (e.g., 30 days for monthly stipends). Perks expire at the end of their window; there is no automatic rollover. ### Credit "Credit" appears in several contexts across Peoplevine, each with a distinct meaning: | Usage | What It Actually Means | Where You'll See It | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | | **House Credit** | Internal account balance a member spends against | Customer profile, House Account billing | | **Stipend** | Recurring monetary perk issued via membership (e.g., "$50/month F\&B credit") | Membership Program > Perks configuration | | **Reward Certificate** | One-off monetary certificate manually issued by an operator — a certificate type alongside Gift Certificate and Stipend | SELL > Gift Cards + Stipends > Sell a Gift Card / Issue Stipend | | **Gift Certificate** | Stored-value payment instrument with a balance (also called "Gift Card" in menu labels) | SELL > Gift Cards + Stipends | | **Credit Card** | A payment method in a Customer's Wallet | Customer profile > Wallet | | **Credit Balances** (report) | Report of outstanding stored-value liabilities (gift cards + stipends) | REPORTS > Credit Balances (`/reporting/giftcard/balance`) | > Key rule from the UI: "Both stipend and giftcard are considered House Credits; however only giftcards can be used towards House Account payments." This means **House Credits** is the umbrella container that holds both stipends and gift cards as spendable balances — but when the system sweeps a house account (Daily/Monthly billing), only gift card balances and card-on-file are charged. Stipends must be spent directly at time of purchase. ### Reward Certificate A one-off monetary certificate manually issued by an operator to a Customer's account. In the UI, it appears as one of four **Certificate Types**: Gift Certificate, Reward Certificate, Stipend, or Deposit. Unlike a Stipend (auto-issued by membership) or a Gift Certificate (purchased), a Reward Certificate is a discretionary balance addition — used for goodwill gestures, error corrections, or promotional incentives. > Not to be confused with **Stipend** (auto-issued via membership perks) or **Gift Certificate** (purchased stored-value). A Reward Certificate is manually created by staff. Where you'll see it: **SELL > Gift Cards + Stipends > Sell a Gift Card / Issue Stipend** (select "Reward Certificate" as Certificate Type). ### Deposit One of four **Certificate Types** in the Gift Certificate engine (alongside Gift Certificate, Reward Certificate, and Stipend). A Deposit is a charge you can issue through the gift card engine to collect a deposit balance on a customer's account. > Not to be confused with **Initiation Fee** (a membership enrollment charge) or **House Credit** (a spendable balance). Deposit is specifically a Certificate Type in SELL > Gift Cards + Stipends. ### House Account An internal account balance that a Customer can use for purchases and services. When `house_account_enabled` is set, the Customer can charge against their house credit balance. House account billing supports three schedules: **Off** (no auto-billing), **Daily** (aggregates same-day charges into one payment to reduce per-transaction fees), or **Monthly** (charges prior-month invoices on the 5th, collecting unpaid invoices up to one year back). Card selection during house account billing follows **bucket logic**: SPA card → Billing card → Default card → next available card. Gift cards apply first, then cards. *** ## Events and Bookings ### Event A scheduled occurrence with ticketing and attendance tracking. Events have a title, date/time, venue, capacity, and registration settings. They can be public or private. Where you'll see it: [**SELL > Events > Manage Events**](https://control.peoplevine.com/events). ### Event Ticket An **entry pass type** for an Event — e.g., "General Admission", "VIP", "Members Only." Defines price, available quantity, and sale dates. This is the ticket definition, not the individual purchased ticket. > Not to be confused with **Event Ticket Log** (the individual purchase record). Event Ticket = "VIP tickets cost $100, 50 available." Event Ticket Log = "Jane Doe bought 1 VIP ticket, barcode ABC123." ### Event Ticket Log The individual ticket purchase record — one per person per ticket purchased. Contains the barcode for scanning/check-in, scan timestamp, and transfer history. ### Booking The general term for any reservation of a resource or time slot. Covers appointments, dining reservations, room reservations, and class registrations. > Not to be confused with **Reservation** (specifically a table/venue/resource hold) or **Appointment** (specifically a scheduled service). ### Reservation Holding a table, venue, or resource — typically for dining or a room. A reservation is about **securing a resource** for a time period. > Not to be confused with **Appointment** (a scheduled service with a provider). A reservation holds a table; an appointment books a massage. ### Appointment A scheduled service at a specific time — e.g., a massage, a consultation, a personal training session. An appointment involves **a service being delivered**. > Not to be confused with **Reservation** (holding a resource). Appointment = "your massage is at 2pm." Reservation = "your table is at 7pm." ### Schedule The configuration that defines a bookable calendar — "Massage Appointments", "Dining Reservations", "Yoga Classes." Each Schedule defines the type (appointment, reservation, class), duration, capacity, payment requirements, and available time slots. The **Daily** booking type is designed for PMS integrations — the Scheduler does not support date-range booking (e.g., multi-night hotel stays). > Also called **Scheduler** in the Control Panel. Where you'll see it: [**SELL > Scheduler > All Schedulers**](https://control.peoplevine.com/schedulers). > **Note (Pro Dash):** SELL > Scheduler > All Schedulers (same path). ### Schedule Slot An available time block within a Schedule. Has a start time, end time, capacity, and booked count. This is what a Customer selects when making a booking. ### Schedule Booking The actual reservation record created when a Customer books a slot. Links a Customer to a Schedule Slot with party size, notes, and status. Statuses include: Booked, Confirmed, Cancelled, Pending, Pending Payment, Arrived, Completed, and Waitlisted. *** ## Communications ### Newsletter (Marketing Newsletter) A **single-send** email, SMS, or push notification sent to an audience. You compose it, select recipients, and send (or schedule). One message, one send. Marketing newsletters are audience-based and include an opt-out option. Targeting supports various filters for audience segmentation. Newsletters support dynamic content — snippets for upcoming events, recent blog posts, directory profiles, and more can auto-populate at send time, enabling recurring newsletters (weekly/monthly) with fresh content each send. Contact Peoplevine Support at for dynamic content setup. The **Send Via** field allows enterprise clients to route emails through their own SMTP gateway instead of Peoplevine's default (SendGrid). Misconfigured gateways are a common cause of email delivery failures — if emails are failing, check the Send Via setting first. > Emails require explicit **Approval** before sending. **High Importance** emails override opt-in for active members and should be reserved strictly for urgent alerts — overuse causes spam filtering and brand damage. > Not to be confused with **Campaign** (a multi-step automated workflow) or **Triggered Response** (an operational/transactional email). Newsletter = one marketing blast. Where you'll see it: [**CONNECT > Group Messaging > Manage E-mails**](https://control.peoplevine.com/newsletters?message_type=email) (for email newsletters). SMS and App Push are under separate subsections within Group Messaging. ### Triggered Response An **operational or transactional** email/SMS sent automatically in response to a system event — e.g., application confirmation, booking reminder, password reset. Triggered responses are event-driven, typically do not include marketing opt-out, and are distinct from audience-based newsletters. Where you'll see it: Not visible as a standalone menu item in Standard Dash. Access via Manage E-mails > Newsletter type = Triggered Response. > **Note (Pro Dash):** CONNECT > Notifications > Triggered Response. ### Campaign A **multi-step automated workflow** with triggers and timed sends. Campaigns fire based on dates, behaviors, or events — e.g., "send welcome email on signup, follow up 3 days later, then send survey after 2 weeks." Campaign types include: * **Date-Based** — birthdays, anniversaries, join date, billing date, renewals, bookings, date attributes; supports day offsets (before/after) * **Drip** — time-based nurture sequences * **Completed** — chain actions based on completion or read status * **Follow-Through** — ensure completion of a target action after a trigger or newsletter * **Attribute Tag** — trigger on applied attributes/tags * **Pre-Arrival** — send preparatory communications before scheduled engagements (reservations, appointments, hotel stays) * **When-It's-Over (Post-Event)** — collect feedback or follow up after an event, appointment, or class * **Checking-In** — verify whether an applicant or member has completed a required action (e.g., finished an application step); sends a reminder if the action remains incomplete after a configurable delay > Not to be confused with **Newsletter** (a single manual send) or **Triggered Response** (a single operational email fired by one event). Also not to be confused with **Follow-Through Campaign** — a Checking-In Campaign monitors for completion of a specific action, while Follow-Through monitors completion after a trigger or newsletter send. Where you'll see it: [**CONNECT > Automations > Manage Campaigns**](https://control.peoplevine.com/campaigns). > **Note (Pro Dash):** AUTOMATE > Campaigns. ### Staff Note An internal note attached to a Customer's record, visible only to staff. Used for recording interactions, follow-ups, and internal context. Notes have types (Priority, General, Subscription Modified, etc.) and optional follow-up dates. > These are operator-only — Customers never see Staff Notes. Where you'll see it: **CRM > Customer profile > Notes**. ### Touchpoint Any interaction or communication point with a Customer. Peoplevine tracks touchpoint count and last touchpoint date per Customer as engagement metrics. ### Profile Question A configurable field on the CRM registration/edit form — e.g., "Lead Source", "Dietary Preferences", "Wine Preferences." Profile Questions define what additional data is collected when a person is registered or edited. To manage Profile Questions, edit the CRM form under [**ENGAGE > Survey & Forms > Manage Forms**](https://control.peoplevine.com/surveys). Use controlled input types (dropdowns, radio buttons, checkboxes) for segmentation-critical data; avoid free-text fields for anything you'll need to filter on. > Profile Questions can be tagged as **Attributes** to enable segmentation. Where you'll see it: On the CRM person form when registering or editing a person. Configured via [**ENGAGE > Survey & Forms > Manage Forms**](https://control.peoplevine.com/surveys). ### Dynamic Content (Templating) Peoplevine's templating system used within newsletters, email builders, and campaign templates to inject dynamic content at send time. Out-of-the-box snippets include upcoming events, recent blog posts, and directory profiles. Advanced dynamic content can pull membership details, available appointments, calendars, and product listings — but custom snippets require development work. Dynamic content is what makes recurring (weekly/monthly) newsletters possible with fresh content each send. Contact Peoplevine Support at for setup. Where you'll see it: Inside the newsletter builder as pre-built snippet blocks. ### Keyword Engine An SMS and concierge auto-reply system that matches incoming text messages against configured keywords and sends automatic responses. Keywords can use **exact match**, **starts with**, **ends with**, or **anywhere in message** matching. Wildcard characters (`%`) create broad catch-all replies. The system uses **closest-match** logic — longer keyword matches take priority over shorter ones (e.g., "today's hours" beats "hours"). Three-character minimum enforced for keywords. Keywords can also forward messages to management, post to external services, or tag attributes on the sender's CRM profile. Where you'll see it: [**CONNECT > Automations > Manage SMS Keywords**](https://control.peoplevine.com/admin_keywords.aspx). > **Note (Pro Dash):** AUTOMATE > Intelligence > Keywords. ### High-Importance Email A newsletter setting that overrides the opt-in/opt-out flag for **active members only**. When enabled, the email is delivered even to members who have opted out of marketing communications. Intended strictly for urgent operational alerts (closures, safety notices, critical policy changes). Overuse causes spam classification, opt-out confusion, and brand damage. > This is a setting on a newsletter, not a separate entity. ### Send Via A newsletter configuration field that specifies which email gateway to use for delivery. By default, Peoplevine sends through its own infrastructure (SendGrid). Enterprise clients can configure their own SMTP gateway. Misconfigured Send Via settings are the most common cause of email delivery failures — always check this field when troubleshooting. ### Attribute Group A set of custom tags used for customer segmentation. Examples: "Account Manager", "Budget Range", "Dietary Preferences", "Industry". > Think of these as custom segmentation fields with predefined values that Customers can be tagged with. Attributes can be created by marking Profile Questions as attributes, or applied automatically via form mapping — when a form question is set to **Segment into Groups (Attribute)**, the respondent's answer is saved as an attribute value. The attribute title must match an existing attribute name exactly or it will create a duplicate with the variance. Where you'll see it: [**CRM > Attributes > View Attribute Groups**](https://control.peoplevine.com/admin_customer_attributes.aspx). > **Note (Pro Dash):** CRM > Analytics > People Attributes > View Groups. *** ## Content and CMS ### Blog Post A content article published through the ENGAGE module's content management system. Blog posts have a title, body (rich text), featured image, preview text, posting date, and publish status. Posts can be assigned to categories (Club Updates, News, Family Articles, etc.) and include SEO fields (meta keywords, descriptions). Blog posts support version history ("View Past Versions") and traffic statistics tracking. Blog content can also be pulled dynamically into newsletters via dynamic content snippets — enabling automated "recent posts" sections in recurring email sends. Where you'll see it: [**ENGAGE > Content > Manage Blog Posts**](https://control.peoplevine.com/blog). API: `GET /api/blogs`. > **Note (Pro Dash):** ENGAGE > Content > Blog. ### Content Page A standalone web page created and hosted within Peoplevine's CMS. Content Pages are used for landing pages, informational pages, and custom portal content. Each page has a title, body (rich text editor), URL/keyword path, visibility settings (Anyone PUBLIC, specific member groups, etc.), and category assignments. Pages can be linked to a **Page Layout** for consistent styling. > Not to be confused with **Blog Post** (a dated content article). A Content Page is a static or semi-static page; a Blog Post is a time-stamped article. Where you'll see it: [**ENGAGE > Content > Manage Pages**](https://control.peoplevine.com/pages?page_type=content). API: `GET /api/pages`. > **Note (Pro Dash):** ENGAGE > Content > Pages. ### Page Layout A reusable design template that controls the visual appearance of Content Pages and portal screens (legacy). Page Layouts define header, footer, CSS styling, and structural elements. Layouts can be linked to multiple pages and include scheduling availability for time-limited designs (seasonal themes, event branding). Where you'll see it: [**ENGAGE > Content > Manage Page Layouts**](https://control.peoplevine.com/admin_page_layouts.aspx). > **Note (Pro Dash):** ENGAGE > Layouts & Templates > Web Layouts. *** ## Billing and Financial Concepts ### Billing Cycle The interval between recurring charges — monthly, quarterly, semi-annually, annually, or one-time. Defined at the Service or Membership Program level. ### Renewal Reactivation of an expired or expiring membership or subscription. Can be **automatic** (auto-renew enabled, system charges on renewal date) or **manual** (Customer or Operator initiates). ### Proration Adjusting a billing amount to align with a calendar period — e.g., if a member joins mid-month on a monthly plan, the first charge is prorated for the remaining days. ### ARR (Annual Recurring Revenue) Annualized revenue from subscriptions and membership dues. A financial metric displayed in dashboards. ### Service Fee A surcharge applied to credit card payments — configured at the Membership Program level. Currently applies only to credit card transactions. ### Billing Contact The person designated as financially responsible for a membership. The billing contact may differ from the member themselves — e.g., a corporate sponsor paying for an employee's membership, or one spouse paying for a couples membership. Set during enrollment. ### Authorization / Capture The two-step payment flow where Stripe first verifies the card and the issuing bank reserves (holds) funds (**Authorization**), then collects the funds (**Capture**). Transactions using this flow show as **Authorized** in View Transactions until captured. When **Auto Capture** is configured on the processor, Stripe automatically captures the authorized funds — no manual action is needed. The transaction updates to **Processed** once captured. An **Auto Capture** tag appears alongside the **Authorized** tag in View Transactions to indicate this. The most common use of the two-step flow is for **F\&B transactions** through POS integrations (Micros, Lightspeed). The authorization holds the check amount, allowing time for the member to add a tip. If a tip is added, the system captures the final amount (original + tip) in one transaction. If no tip is added, the system **auto-captures** the authorization at a configurable time (default: midnight local time, adjustable in Platform Settings). > Not to be confused with a standard **Processed** transaction, which captures funds immediately without a separate authorization step. ### Card-on-File A payment method stored on a member's profile that is used for automated charges — POS payments, house account billing, and recurring dues. Card-on-file enables frictionless experiences where the member never pulls out their wallet. Each card can be designated for a specific purpose: **Default**, **Billing** (membership dues & general house account), or **F\&B/POS**. During house account billing, the system selects the card matching the charge category (F\&B credit card for dining orders); if no match exists, it falls back through: Billing → Default → next available card. ### Payment Bucket Logic The internal routing and fallback sequence used during house account billing. House account billing **breaks out charges by category to specialized processors**: F\&B, Spa, and PMS charges are each sent to their designated processor first, then the remainder goes to the Billing processor (or Default if Billing isn't configured). For card selection within each category, the system looks for a card designated for that category. If none is found, it cascades: category-specific card → Billing card → Default card → next available card. Gift cards are always applied **before** cards. ### Auto-Sweep The automated process that collects open house-account invoices on a schedule. Configured in **Platform Settings** with three modes: **Off** (manual only), **Daily** (charges yesterday's invoices each morning — reduces per-transaction fees by batching), or **Monthly** (charges all prior-month invoices on the 5th, collecting up to one year back — the traditional club model). Daily mode is recommended for clubs with high F\&B volume to reduce Stripe per-transaction fees. ### Processor Scenario Override A configuration that routes specific payment types to specific Stripe connections. See **Payment Processor** for the six named override slots. Overrides enable multi-entity clubs to direct hotel charges to one Stripe account, restaurant charges to another, and spa charges to a third — each receiving funds directly. ### Wallet A stored payment method on a Customer's account — credit card, bank account, or gift card. Each Customer can have multiple wallet entries, with one marked as **default**. Wallets store tokenized card information (last four digits, expiry, brand). Payment methods are categorized as **persistent** (Credit Card, ACH, Invoice — suitable for automated billing) or **non-persistent** (Wire, Cash, Paper Check, Not Required — require manual handling). When adding a payment method on a CRM profile, the **Use For** selector assigns the card to a specific purpose: **Default Payment Method**, **Membership Dues Billing**, **Food & Beverage**, **Spa and Activities**, **Hotel Stays**, or **Add to Wallet**. This determines which processor handles charges for this card in staff-side and automated flows (membership billing, integration charges). In Member Portal checkout, "Use For" is not enforced — members see all saved cards and choose freely. Where you'll see it: **CRM Profile > Add Payment Method** (Control Panel). In the **Member Portal**, payment methods appear under the **Wallet** tab — "Wallet" as a section label is portal-only. ### Payment Processor The external payment gateway configuration. Currently supported processors are **Stripe V2** (credit cards) and **GoCardless** (ACH / Direct Debit). Stripe supports multiple connections and scenario-based overrides; GoCardless is limited to a single active connection per company (adding a second invalidates the prior token). Processor assignments can be overridden per scenario using six named slots: | Scenario Override | What It Covers | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Default** | Required. Fallback for any payment not matched by another override. | | **Membership Billing** | Recurring dues and initiation-fee charges. Often set to ACH (GoCardless) for high-value initiation fees to reduce transaction fees. | | **POS / Virtual POS** | Third-party point-of-sale integrations (Micros, Toast, Lightspeed) and the Control Panel's Virtual POS screen. Supports **Force Payment** flag to restrict cloud-rail charges to a specific processor. | | **PMS / Hotel** | Property management charges (Opera, Mews). Hotel room folios and incidentals. Supports **Force Payment** flag. | | **Spa** | Spa integration charges (Book4Time). Post-pay transactions from spa bookings. Supports **Force Payment** flag. | | **House Account Routing** | Controlled by the House Account Routing setting in Platform Settings — routes non-specific house account invoices to either the Default Processor or the Membership Billing Processor. House Account is not a payment processor — it is a billing/invoice collection route. | Each slot can point to a different Stripe connection, enabling multi-entity clubs (hotel, restaurant, spa) to route revenue to separate Stripe accounts. > **Pre-selection**: When staff charge through Virtual POS, the POS processor is pre-selected but can be overridden per transaction. > **Force Payment** is supported on POS, Spa, and PMS overrides — but **not on Default**. It restricts charges in that category to the designated processor. > A default payment provider is mandatory — missing defaults cause payment failures. *** ## Accounting and Tax ### Tax Group A named collection of one or more **Tax Rules** that can be assigned to any taxable item — membership programs, event tickets, products, subscriptions, or schedulers. Tax groups override the system-wide default tax rate when attached to a specific item. They enable complex multi-jurisdiction tax scenarios (e.g., city + state + county taxes applied together). > Not to be confused with the **default tax rate** set under Platform Settings, which applies when no tax group override is assigned. Where you'll see it: [**SETTINGS > Accounting > Tax Groups**](https://control.peoplevine.com/tax/groups). ### Tax Rule A single tax line within a Tax Group — e.g., "State Tax 4%" or "City Tax 6.25%." Each rule specifies a name, whether it's a percentage or a flat amount, and the rate. Multiple rules stack additively within a Tax Group; the system calculates each independently against the item price. ### GL Account A **General Ledger Account** number used for accounting integration. GL accounts are mapped to revenue-generating items (membership dues, initiation fees, scheduler bookings, products) so that exported transaction data routes to the correct chart-of-accounts bucket. Supports split allocations (e.g., 75% to club revenue, 25% to hotel revenue). Where you'll see it: [**SETTINGS > Accounting > G/L Accounts**](https://control.peoplevine.com/admin_chart_of_accounts.aspx) and on individual item configuration screens. ### Cost Center A secondary accounting dimension used alongside GL Accounts to track which department or business unit generated the revenue. Cost centers appear in the accounting data extract alongside GL accounts and transaction line items. *** ## Platform and System ### Control Panel The **administrative interface** where Operators manage all platform functions. This is the staff-facing side of Peoplevine — where you manage customers, process orders, configure memberships, send communications, and run reports. > Not to be confused with **Member Portal** (the customer-facing interface). ### Member Portal The **customer-facing website/app** where Members view their profile, manage bookings, check membership status, and interact with the organization. This is what your customers see. > **Public access:** The portal can be configured to allow non-members to create an account — for example, to register for public events. A non-member enters their email and the system prompts them to set up an account (no membership required). Anonymous access is not supported — a portal account is always needed. To enable public registration, contact the Peoplevine team. Additionally, the event itself must be set to **Public** visibility with **Anyone (Public)** registration in the Control Panel. ### Company The tenant/organization in Peoplevine's multi-tenant architecture. Each Company is an isolated account with its own Customers, Products, Memberships, and settings. A `company_id` foreign key appears throughout the data model. > Not to be confused with **Business** (a directory listing entity). A Company is your organization's Peoplevine account. A Business is an entry in a business directory within your account. ### Business An entity in the business directory — a vendor, partner, or listing. Can have multiple locations, products, and schedules. > Not to be confused with **Company** (your Peoplevine tenant). Business is a directory entry; Company is the account owner. ### Business Location A physical location belonging to a Business — a store, studio, office, or venue. Locations have addresses, hours, tax rates, and can independently process orders and transactions. ### Global Network A feature that connects multiple companies (properties) into one network. Through configuration, CRM profiles, member activity (bookings, transactions, etc.), payment methods, and members are enabled into the Global Network to allow cross-syncing and access. Members experience single sign-on in the member portal as they toggle between locations. Member sync runs approximately every 10–15 minutes; access and IDs propagate across connected clubs and integrated systems. Sync relies on **email matching** — if a member's email changes, they will not sync automatically. Two manual sync options: **Sync Global Members** (on the membership program page, syncs all members) and **Push Member** (on the CRM profile below the photo, syncs one member). > **Caution:** Do not assign a global-network-designated membership program to the global network itself — this risks a sync loop. Integrations sync member records to external systems but do not create external membership programs; those must be pre-configured in the external system with matching SKUs. ### Webhook An outbound HTTP callback triggered by system events. Peoplevine supports 150+ webhook action types for integrating with external systems. Where you'll see it: [**SETTINGS > Integrations > Manage Webhooks**](https://control.peoplevine.com/webhooks). > **Note (Pro Dash):** AUTOMATE > Integrations > Webhooks. ### Rule A conditional automation rule that triggers actions when specific criteria are met. Rules enable business process automation without code. Where you'll see it: [**SETTINGS > Platform > Rules**](https://control.peoplevine.com/rules). ### Vanity URL A custom, branded URL that redirects to a Peoplevine page — e.g., `yourdomain.com/feedback` pointing to a form, or `yourdomain.com/events` pointing to the events page. Vanity URLs make links easier to share and more professional. They can also redirect traffic from retired pages to replacement pages. Where you'll see it: [**SETTINGS > URLs > Manage Vanity URLs**](https://control.peoplevine.com/vanity-urls). > **Note (Pro Dash):** SETTINGS > URLs & Domains > Manage Vanity URLs. ### Alert A notification (email or SMS) sent to **staff or members** when a specific platform event occurs. Alerts can be configured at the **form level** (for individual form submissions and response status changes) or **globally** (across CRM, membership, subscription, commerce, booking, loyalty, event, and other activities). SMS alerts require your own **Twilio** account — you must sign up at twilio.com and provide your Account SID and Auth Token in the integration settings. Where you'll see it: Form Detail page > **MANAGE ALERTS** (form-level) or **Hello, \[your name]** > **View Alerts** (global). ### FaceSheet A PDF report that generates a printable snapshot with photos and key details. Available in two contexts: * **Applications**: A consolidated list of applicants with the associated filters. Designed for leadership review — e.g., generating a list of applicants recommended for approval. Accessed via the **FACE SHEET** button on the **View Applicants** list page (select one or more records, then click the button). * **Events**: A printable attendee list with photos, names, member types, ticket details, and fun facts where available. Accessed from the event detail page. Where you'll see it: [**ENGAGE > Survey & Forms > Manage Applications > View Applicants**](https://control.peoplevine.com/survey/group/0/responses) (select records > FACE SHEET button); event detail page (green export button, top center). *** ## Integrations and POS ### EMC-Based Setup The deployment method for the Micros POS integration using Oracle's **Enterprise Management Console** (EMC). EMC manages Micros Simphony terminal configurations. The Peoplevine integration requires deploying DLL files and configuration to each terminal — EMC is used to manage this across locations. Supported on Simphony versions 18.2 and above. ### Tender Type A payment method configured within any integration that routes payments through Peoplevine — POS (Micros, Toast, Book4Time), PMS (Opera), and spa systems. Tender types map integration payment options to Peoplevine actions — e.g., "PV Card on File" triggers a cloud-based card charge, "PV House Account" creates an invoice. At least one Peoplevine tender type must be configured for payment integration to work. ### Revenue Center A location or business unit within a POS system (e.g., "Main Dining Room," "Pool Bar," "Terrace") that determines how transactions are categorized and where revenue is routed. Revenue centers are mapped during integration setup and appear in the integration configuration alongside tender types and discount codes. ### SKU Mapping The practice of matching a **SKU** (Stock Keeping Unit) between Peoplevine and an external system. SKU mapping works in both directions: Peoplevine uses SKUs to map members to a membership in external systems (Book4Time, Opera, Micros), and POS orders sync products with SKUs back to Peoplevine. When SKUs match, the integration can sync membership tiers correctly, apply tier-specific pricing, and attribute product sales. External systems must have the membership program pre-configured with matching SKUs — Peoplevine does not create programs in external systems. *** ## Control Panel Modules The Control Panel is organized into modules. Menu names differ between **Standard Dash** and **Pro Dash**: | Standard Dash | Pro Dash | What It Manages | | --------------- | --------------- | --------------------------------------------------------------- | | **CRM** | **CRM** | People, customer records, notes, attributes, demographics | | **SELL** | **SELL** | Commerce — orders, events, scheduling, products, billing | | **MEMBERS** | **REWARD** | Memberships, check-ins, vouchers, loyalty, rewards | | **ENGAGE** | **ENGAGE** | Forms, surveys, content (blog, pages, FAQs), media, directory | | **CONNECT** | **CONNECT** | Messaging — email, SMS, push notifications, affiliates | | **REPORTS** | *(not present)* | Standard and custom reports, exports, sales and billing reports | | **SETTINGS** | **SETTINGS** | Configuration, integrations, users, rules, domains | | *(not present)* | **AUTOMATE** | Campaigns, keywords, webhooks, triggered responses | > **Note:** Pro Dash moves campaigns, keywords, and webhooks into the AUTOMATE menu. Standard Dash keeps them under CONNECT and SETTINGS. Reports functionality exists in both but is accessed differently. Toggle between views: click your name in the top-right > View Profile > Dash Version dropdown. *** ## Common State Values For a complete reference of all status codes — memberships, subscriptions, transactions, applications, bookings, orders, and vouchers — including what triggers each status and its operational effect, see: [Status Code Reference](/status-codes-reference.md). *** ## Easily Confused Terms — Quick Reference | Term A | Term B | The Difference | | -------------------- | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Customer | Member | Customer = anyone in the system. Member = has an active membership. | | Customer | User | Customer = person in the CRM. User = staff account for the Control Panel. | | Member | Sub-Member | Member = primary card holder. Sub-Member = dependent/family on same card. | | Membership Program | Member Card | Program = the plan template. Card = one person's enrollment in that program. | | Service | Subscription | Service = subscription plan template. Subscription = a customer's active enrollment. | | Subscription | Membership Subscription | Subscription = general recurring service. Membership Subscription = recurring billing for a membership card. | | Order | Transaction | Order = what's being bought. Transaction = the payment record. | | Invoice | Receipt | Invoice = bill (unpaid). Receipt = proof of payment (paid). | | Newsletter | Campaign | Newsletter = single manual send. Campaign = multi-step automated sequence. | | Voucher | Gift Card | Voucher = non-monetary perk (guest pass, drink ticket). Gift Card = stored monetary value. | | Discount | Coupon | Discount = price reduction (can be automatic). Coupon = specific promotional code. | | Reservation | Appointment | Reservation = holding a resource (table, room). Appointment = scheduled service (massage, consultation). | | Event Ticket | Event Ticket Log | Ticket = the ticket type definition. Ticket Log = individual purchase record with barcode. | | Company | Business | Company = your Peoplevine tenant/organization. Business = directory listing entry. | | Control Panel | Member Portal | Control Panel = staff admin interface. Portal = customer-facing website. | | Newsletter | Triggered Response | Newsletter = audience-based marketing send with opt-out. Triggered Response = operational/transactional, event-driven, no opt-out. | | Application | Form | Application = multi-step gated enrollment process. Form = standalone data-collection page. | | Stipend | Gift Card | Stipend = recurring perk credit issued via membership. Gift Card = stored-value payment instrument. | | Persistent Payment | Non-Persistent Payment | Persistent (Credit Card, ACH, Invoice) = auto-billable. Non-persistent (Wire, Cash, Check) = manual only. | | Failed | Declined | Failed = payment attempt that will be retried (Day 3, Day 7). Declined = payment rejected outright. | | Tax Group | Tax Rule | Tax Group = a named collection of rules assigned to an item. Tax Rule = a single tax line (name + rate) within a group. | | F\&B Authorization | F\&B Capture | Authorization = hold placed on card at POS check open. Capture = final charge (with tip) collected later or auto-captured overnight. | | Checking-In Campaign | Follow-Through Campaign | Checking-In = monitors whether a specific action was completed after a trigger. Follow-Through = monitors completion after a newsletter send or trigger, then follows up if incomplete. | | Invoice 1.0 | Invoice 2.0 | 1.0 = classic PDF format, basic layout. 2.0 = enhanced Peoplevine-managed format — supports regional taxes, QR codes, multi-language translations, and custom templates. | | House Credit | Stipend | House Credit = the account balance container. Stipend = one type of credit that flows into it. Gift Cards also flow into House Credits, but only gift cards can pay house account bills. | | Reward Certificate | Gift Certificate | Reward Certificate = discretionary one-off certificate issued by staff. Gift Certificate = stored-value instrument with a balance, purchasable by anyone. Both are Certificate Types in SELL > Gift Cards + Stipends. | | Deposit | Initiation Fee / House Credit | Deposit is a **Certificate Type** in the gift card engine — a charge you can issue to collect a deposit balance. Not the same as an Initiation Fee (membership enrollment charge) or House Credit (spendable balance). | | Blog Post | Content Page | Blog Post = dated article with featured image and statistics. Content Page = static/semi-static page for landing pages and portal content. | *** *** ## Supported Integrations Peoplevine connects with the following external systems. Integration setup is managed under [**SETTINGS > Integrations > Integrated Platforms**](https://control.peoplevine.com/admin_authenticate.aspx). | Category | System | Status | | ----------------------- | --------------------------------------------------------- | -------------- | | **POS** | Micros | GA | | | Toast | GA | | | Lightspeed K | GA | | | Silverware (via connector) | Pilot | | | InfoGenesis (via connector) | Pilot | | | Shiji (via connector) | In Development | | **PMS** | Oracle Opera Cloud (OHIP) | GA | | | Oracle Opera On-Premise (OXI) | Retiring | | | Mews (profiles + reservations only — payments on roadmap) | GA | | **Bookings and Dining** | SevenRooms | GA | | | Book4Time | GA | | | OpenTable | Beta | | | TableCheck | GA | | | TripleSeat | GA | | | Lightspeed Golf | In Development | | **Access Control** | Salto | Beta | | | VIZpin | GA | | | Hikvision | GA | | | Seam connector (Salto, Assa Abloy, Dormakaba) | In Development | | **Payment Processing** | Stripe V2 (credit card) | GA | | | GoCardless (ACH / Direct Debit) | GA | | | Worldpay | Retiring | | **Accounting** | QuickBooks | GA | | | Impact (Greek fiscalization only) | GA | | **Messaging** | Twilio (messaging) | GA | | | Alliants | GA | | | Infobip | Beta | | **CRM Sync** | Salesforce (via Webhooks) | GA | > **Note**: "Beta" integrations are available but may have limited support or feature coverage. "Pilot" integrations are live with select clients. "In Development" integrations are not yet available. Contact your Peoplevine onboarding team for setup guidance. > > Peoplevine also supports outbound **webhooks** that allow other systems to connect — see [Developer Resources](https://www.peoplevine.com/developers-resources) for details. *Last updated: 2026-07-12* --- # 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/glossary.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.