Skip to main content
Once an event has a public page, there are three ways to put it in front of people: the Share button, a directory of everything coming up, and embeds for your own website. Built for organisers who post events to Facebook or LinkedIn, keep an events page on their own site, and want both to stay current without copying details around. Replaces manually maintained “upcoming events” pages and hand-built social cards.

Sharing from the event page

Open a published event and use Share in the bar above the event page. It opens Quick Share: Your unique link with a Copy link button, and buttons to post to Facebook, WhatsApp or LinkedIn.
  • For a Public or Private link event, the link is the event’s public page.
  • For a Members only event, the link is the event page inside the app, which only signed-in members can open.
  • A draft has no Share button. For a public draft, use Share preview instead (see Previewing a draft).
Visitors can share too. The public event page has its own Share button with the same options (desktop only).
Social platforms and messaging apps read a page’s preview tags without running its JavaScript, and the public event page is a JavaScript application. A pasted link may therefore show your organisation’s generic details rather than the event’s title and cover image.

The public event directory

Every organisation has a page listing its public events:
From inside the app, open Events (with no group selected) and choose Public events in the header menu to jump to it. Visitors reach it from the button at the top of any public event page, which carries your organisation’s name and “Events”, or from “Explore events” on a phone. Public event directory showing the next event as a large hero card, a list of upcoming events with dates and cover images, and a month calendar with event dates marked It shows only events that are both published and Public. Private link events are never listed, and a members-only ticketed event has no public page at all. Visitors get no search box and no filters. Those controls are for signed-in members on the internal event list.

Embedding on your own website

The directory and the agenda are both embeddable in an iframe. Adding iframe=true to the address strips the page down for embedding: it hides your logo and the “built with Orgo.space” line, and forces the light theme so the embed does not turn dark on a visitor whose device prefers dark mode.
Give it generous height. The embed does not resize its parent frame, so a short frame cuts the list off rather than scrolling neatly.
If your organisation uses the built-in website, its “Upcoming events” section already embeds this exact page for you, so you do not need to paste anything.

Embedding the agenda

For a conference the agenda is often what people want on the website. Open the event, go to Program & Speakers (the second word follows the label the event uses for speakers), and use Iframe URL. The button appears for people who can edit the event, and only when the event is public or ticketed. It copies an address of the form https://<your app domain>/public/event-agenda/<event uuid>?workspace=<your slug>&iframe=true, ready to drop into an iframe. The embed shows the sessions grouped by day with their times, stages and locations, and speaker cards that open a profile with the speaker’s bio and their other sessions. The event title is hidden in embed mode so it sits under your own heading. Embedded event agenda showing sessions grouped by day with start and end times, stage labels and speaker avatars, without the event title Session data is cached for five minutes, so a change to the schedule shows up on the embed shortly after you save it. For events that are neither public nor ticketed the address returns “not found”, which is the same rule the public page follows.
The public page address is a plain URL, so any QR code generator can turn it into a code for posters and flyers. Nothing in Orgo needs to be configured for that, and the code keeps working as long as the event exists. Do not confuse it with the QR code an attendee receives after registering. That one identifies the person, not the event, and is what gets scanned at check-in.

Search engines

Do not plan a search strategy around the public event page. It is a JavaScript application whose browser tab title is your organisation name, not the event name. Private link events ask search engines not to index them. If search visibility matters, publish the event on your own site and link out to the Orgo page for registration.

Permissions

Organization admins can do all of these across the organization.