What is an Occasion in Tov+?
An Occasion is the root planning object. It groups the ceremony, reception, travel, brunch, vendors, guests, assets, and permissions into one coordinated operating surface.
FAQ
Do guests need to create accounts?
No. Guest access is token-first and account-optional. Basic guest flows should work without forcing account creation.
How are vendors and guests scoped differently?
Both flow through the Actor model, but each actor receives permissioned views based on role, scope, and resource access. Vendors see operational slices, while guests see invitation-relevant details.
Can modules be turned on selectively?
Yes. Modules are configured at the Occasion level and enabled per Event, so an occasion can use RSVP everywhere while limiting seating or gallery to specific events.
What belongs in the public developer docs?
Only integration-facing material: public API endpoints, webhook events, auth expectations, and system concepts that external builders need in order to integrate with Tov+.
Where did the internal setup and admin docs go?
Internal setup, local environment, operational runbooks, admin APIs, and full internal swagger references now belong in the admin website instead of the public docs site.