Data model (high level)
These aggregates describe how work is grouped—not an exhaustive schema:
| Domain | Conceptual building blocks |
|---|---|
| Tenancy | Organizations, memberships, invitations, billing relationships |
| Guest web apps | Landing pages, configurable tiles, FAQs, embeddable widgets |
| Geo and plans | Places, groups, points of interest, venue site plans, map-oriented layers |
| Tours | Tours, ordered stops, media, assignments, optional monetization tiers |
| Events | Programs, schedules, invitations, ticketing where enabled, attendee state |
| CRM and communications | Customers, interaction history (protocols), tasks, documents, newsletters, mail threads |
| Commerce (checkout) | Orders (what was bought), payments (provider charge state, amounts), price tiers |
Commerce, orders, and payments
- Minor units: Stored prices and payment amounts are integers in the smallest currency unit supported for that currency (for example cents where applicable), consistent with Stripe’s model.
- Presentment currency: Each organization configures a single checkout/presentment currency (ISO 4217). Product prices (such as ticket types or tour tiers) do not carry their own currency code; they are interpreted in the owning organization’s currency.
Paymentrecords: A payment row storesamountandcurrencyfor reconciliation and admin reporting. For Stripe, the amount and currency are updated again when the provider confirms the charge (for example from the PaymentIntent or charge object) so the ledger matches what was actually captured.- Orders vs payments: An order describes line items and entitlement; a payment describes money movement. Support for refunds, disputes, and finance review should use the payment and provider dashboard together with the order.
CRM relationships (dashboard language)
In the dashboard, protocols are structured interaction logs tied to customers (calls, meetings, notes, mail). They connect naturally to tasks, projects, milestones, documents, campaigns, and events when teams link records together.
Support questions usually start from the customer profile. From there, check the related tasks, protocols, project milestones, linked files, newsletter audiences, mail history, or event participation.
Related concepts: Product model, CRM and operations, Customer management overview.