Skip to main content
Some events have a page that anyone can open without signing in: cover image, description, speakers, an agenda when the event has sessions, and a card to register or buy a ticket. Built for organisers promoting an event to people who are not members yet, and who should be able to register without creating an account first. Replaces a separate event site or ticketing page that has no idea who your members are. Public event page with the cover image and Hosted by block on the left, and the event title, date, location and Get tickets card with ticket types on the right

​
Which events have one

Exactly two kinds, and this is the rule that matters:
  • events marked Public, and
  • events with ticketing enabled, whether or not they are public.
Anything else refuses the request. A members-only event with no ticketing returns nothing at the public address: the visitor gets an empty page, not a login prompt and not the event details.
Turning on ticketing makes the event page publicly readable even if the event itself is not public. If an event should stay internal, keep it free and use RSVP rather than tickets, and share the in-app link instead.
Marking an event public is gated by Settings → Events → Who Can Create Public Events. That setting is a ceiling, not an alternative route: if it is set to EVENT_TENANT, someone with only EVENT_LOCAL who ticks “Public” has the flag silently dropped on save. Events hosted by a private (non-joinable) group can never be public. Ticketing needs EVENT_TENANT. FINANCIAL_TENANT shows the Paid option and the Tickets and Payments screens, but saving a Paid event still needs EVENT_TENANT.

​
The address

On the shared domain app.orgo.space the link also needs ?workspace=<your slug> so the page knows which organisation it belongs to. On a custom domain the organisation is resolved from the domain and no parameter is needed. Open the event and use Landing page in the event sidebar to see the page as a visitor does, with the right parameters already attached. The entry appears once the event is public or ticketed.

​
What a visitor sees

Someone who already registered sees their own status instead of the ticket picker: their ticket or registration, a button to show the QR code, and, when the event runs votes, a Votes tab. That also works for a non-member ticket holder, whose emailed link carries a personal hash parameter that identifies them without an account. The {eventAgendaUrl} placeholder in emails and newsletters produces exactly that personalised link. Registration is covered in Ticketing and Registration forms. The page also shows state: “Registrations are closed” when the organiser closed them, “This event is full” when capacity is reached, and no registration card at all once the event has ended (after its end time, or 24 hours after the start when no end time was set).

​
What is never exposed

The public payload is a deliberately narrow slice of the event. These are left out entirely, so they cannot leak through the page or through the underlying request:
  • the online meeting link (visitors see only that the event is online),
  • the attendee list, and the organiser and hosting group,
  • the event’s draft or published state, and any internal report fields,
  • ticket types that name specific membership levels, which are fetched separately after sign-in and only for a member whose level is on the allowlist.
A plain Members only ticket, one with no membership levels named, is not hidden from the public page. Its name, price and remaining seats are served to anonymous visitors, greyed out with a members only badge. Only tickets that name specific levels are withheld.Treat a ticketed event page as public. If a price should not be seen by non-members, do not put it on a ticketed event.
Cover images and agenda images are copied into a public storage folder when an event becomes public or ticketed, so they can be served to signed-out visitors.

​
Appearance

Colours and the hero image rounding are set per event under Registration form → Appearance (Selected color, Button color, Hero image border radius, Display title). That editor only exists on events that require a registration form, which every ticketed event does. See Registration forms for the full table. There is no per-event logo control and no theme picker: the page uses your organisation logo and follows the visitor’s light or dark preference unless the link carries ?light or ?iframe.

​
Common questions

The link is missing ?workspace=<slug> and the visitor has never opened your organisation in that browser. Copy the link from Landing page in the event sidebar rather than from your address bar.
Yes, if your organisation has a custom domain. The page is then served from it and the workspace parameter is unnecessary. Otherwise it lives on app.orgo.space.
The /public/event/... address has no per-event preview data. Use the short share link instead: it serves a preview page carrying the event title, description and cover image, then forwards to the event. See Sharing events.
Member-only tickets are only returned to a signed-in member whose current membership level matches the ticket. Ask them to sign in on the same page, then reload.
It does. Past events keep their address and keep showing the description, agenda and speakers. Only the registration card disappears.