Public event pages are bounded projections served through branded CentriPOS routes. Publishing a feed does not expose private event tables, purchaser records, participant records, registration answers, ticket credentials, capacity administration, or internal calendar entries.

Before you beginConfirm the selected business, offering, occurrence, timezone, ticket option, shared capacity pool, purchaser, and attendee. Scheduled-offering access is entitlement- and role-controlled, and participant records can contain private information.

Step by step

  1. Open Events → Publishing and create a feed with a durable slug and name. Choose Draft, Published, Paused, or Archived and Public, Unlisted, or Private visibility.
  2. Select which offerings appear, their order, and featured state. A feed can use explicit offering membership and supported filters; only offerings that are themselves publication-eligible should render publicly.
  3. Configure the feed theme, SEO fields, and supported embed settings. Review contrast, focus states, mobile layout, image alt text, long descriptions, sold-out states, registration windows, venue wording, and online/hybrid details.
  4. Use only the tenant-qualified branded route generated by CentriPOS: https://pos.getcentri.com/events/feed/{tenantId}/{feedSlug}, with /{eventSlug} for one offering. The published tenantId is a required routing boundary, not a credential; never substitute a Supabase hostname, project reference, storage path, or database URL.
  5. Use the generated event detail route for a single offering. The public slug is a publishing identifier, not an authorization token. Private offerings and nonpublic assets must fail closed even if someone guesses a slug.
  6. For an external website, use https://pos.getcentri.com/events/embed/{tenantId}/{feedSlug}, with optional /{eventSlug}. The twelve formal public GET operations are feed and offering JSON, feed- and offering-scoped occurrence pages, registration bootstrap, paged registration definition, paged physical-seat availability, agenda, feed and offering calendar downloads, and feed and offering rolling calendar subscriptions. Every route is tenant- and feed-qualified; there is no slug-only route. Configure supported layout and theme options, then test desktop and mobile widths.
  7. Use Public only for an external HTTPS asset safe for anonymous delivery. Retail API asset writes reject Supabase project and Storage origins. Managers may upload an Attendees or Staff native file up to 25 MiB; it remains private and is delivered to an authorized attendee through a branded five-minute capability URL with no bucket, object path, project URL, or Supabase hostname in JSON, HTML, logs, or webhooks.
  8. Confirm every occurrence has correct local time, IANA timezone, venue, status, and recurrence exception. Use Manage exceptions for one-date cancellations, reschedules, and modifications; public JSON includes only the sanitized event-facing exception fields.
  9. Offer Add to calendar or Download calendar from the public event or authorized portal page. The public feed ICS uses stable tenant-and-occurrence UIDs, timezone-aware dates, safe location and description fields, RRULE for a recurring series, EXDATE for cancelled instances, and RECURRENCE-ID override events for cancelled, rescheduled, or modified exceptions.
  10. Use the Google Calendar link when presented. Calendar downloads are snapshots; after a reschedule or cancellation, publish the updated schedule and notify attendees through the configured operational channel. Never use public ICS as a participant, registration, or meeting-credential export.
  11. Use the company Calendar to view canonical event occurrence entries beside projected deliveries, service visits, work, projects, external events, and custom entries. Public feed visibility and internal calendar visibility are separate settings.
  12. Before launch, test anonymous feed and detail requests, direct unlisted access, private-offering rejection, branded ready checkout, every non-ready checkout status, adult self and youth guardian registration, deferred group pass, sold-out capacity, cancelled/rescheduled recurrence exceptions, embed, public and attendee-only assets, mobile keyboard/screen-reader flow, and ICS import.
  13. The exact machine routes are GET /api/events/{tenant_id}/{feed_slug}/calendar.ics for a feed and GET /api/events/{tenant_id}/{feed_slug}/offerings/{event_slug}/calendar.ics for one offering.
  14. The feed and offering ICS routes share one bounded contract. A normal response is the complete file. If either export exceeds the occurrence, exception, or 8 MiB limit, 413 calendar_export_requires_pagination supplies first_page and page_size_maximum. Request page_size 1–500 and follow the opaque cursor, RFC 8288 Link rel="next", X-CentriPOS-Next-Cursor, and X-CentriPOS-Calendar-Partial until complete.
  15. Choose Validate before Publish. Resolve every blocking IANA-timezone, missing or contradictory price, incomplete prose, inventory/capacity, unsafe or noncanonical URL, redirect, venue, registration window, recurrence, and lifecycle finding. Publish reruns the authoritative validation and fails closed if the record changed or any blocker remains.
  16. After publication, a transaction that changes the offering or a dependent venue, schedule, product or price, ticket, capacity, asset, purchase rule, access code, ticket preset, or seating record reruns the canonical validation at transaction completion. If the change would leave the live offering invalid, the entire transaction is rejected.
  17. Use /calendar-subscription.ics at feed or offering scope for Apple Calendar and webcal subscriptions. It always returns a bounded rolling attendee-safe window and refreshes at the same stable branded URL; use /calendar.ics for a complete snapshot or its documented paged export.
  18. The public list and detail pages expose List, Month, Week, Day, Map, Photo, and Summary views from one safe projection. Search and filter by event kind, reusable venue, date window, and admission state. Load more follows the opaque occurrence cursor when a large conference exceeds the initial discovery page.
  19. Feed-scoped occurrence pages are globally ordered by (starts_at, id) across every linked published offering, not concatenated one offering at a time. Follow the opaque cursor to continue that same deterministic order without skipping or repeating interleaved conference sessions.
  20. Public HTML includes canonical, Open Graph, Twitter, and schema.org Event, Offer, and Place metadata. Reusable venues provide structured address, coordinates or an approved map URL, public contact details, accessibility summary, and an enforced IANA timezone; an occurrence venue override wins for that dated session.
  21. Reserved-seat checkout starts with a compact safe seat summary and pages available seats through /registration-seats with ticket_option_id plus optional seating_config_id, section_id, search, cursor, and limit 1–250. Never fetch or render an unbounded venue layout in one browser response.
  22. Public and portal projection code recursively strips Supabase origins from URLs, HTML, nested objects, and arrays. Treat any leaked project hostname or Storage path as a privacy defect; never work around the branded boundary by rewriting it in website code.

Screen and contract reference

Control or areaWhat it means
Publication feedThemeable collection of eligible event offerings.
Tenant-qualified feed routePublished tenantId and feedSlug together identify the public projection; neither value is a private credential.
Public / Unlisted / PrivateDiscovery and access boundary for a feed or offering.
FeaturedFeed-specific merchandising flag for an offering.
ThemeSupported colors, typography, spacing, and presentation tokens.
SEOFeed title, description, and supported indexing metadata.
Embed settingsBounded layout and website-placement options.
Public assetExplicitly approved offering or occurrence image, attachment, document, map, video, or download.
checkout_statusPublic ticket state: ready only after storefront, event_ticket, registration, sales-window, and capacity validation; every non-ready state fails closed.
RRULEPublished normal cadence for a recurring series.
EXDATECancelled series instance omitted from normal expansion.
RECURRENCE-IDException component that identifies the original instance being cancelled, rescheduled, or modified.
Master company calendarPrivate operational calendar spanning events and other scheduled work.
Branded routeCustomer-facing URL beneath https://pos.getcentri.com; never an internal data origin.
checkout_statusready, storefront_unavailable, ticket_product_unavailable, registration_unavailable, or sold_out.
Attendees assetAttachment available only through registration-authorized portal access; never placed in an anonymous feed.
Paged ICSBounded page_size/cursor export used when either a feed or offering calendar would exceed the public safety limits.
Offering calendar ICSGET /api/events/{tenantId}/{feedSlug}/offerings/{eventSlug}/calendar.ics; the attendee-safe schedule for one published offering.
Validate before PublishServer-authored blocking and advisory findings; publishing repeats the check and cannot be bypassed by browser state.
Rolling calendar subscriptionStable /calendar-subscription.ics URL for Apple Calendar or webcal clients; bounded to a rolling safe window instead of returning a pagination error.
Occurrence pageFeed- or offering-scoped public continuation page used by giant conference discovery views.
registration-seatsAnonymous-safe, ticket-scoped available-seat page with opaque continuation and bounded filters.
Structured venueReusable Place identity with structured postal address, map data, accessibility summary, public contacts, and an IANA timezone.
Discovery viewsList, Month, Week, Day, Map, Photo, and Summary presentations of the same filtered public data.
Recursive origin scrubFail-closed removal of Supabase project and Storage origins from every public or portal projection depth.

Expected result

The published branded feed, event detail, embed, approved public assets, registration state, recurrence exceptions, and calendar download agree while private participant, ticket, registration-answer, and internal calendar data remain inaccessible anonymously.

Troubleshooting

  • Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.
  • Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.
  • Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.