Skip to main content
Creating an event in Orgo covers everything from a 10-person committee meeting to a 500-person ticketed conference. This guide walks through every option so you know what to use and what to skip. Create Event form with group selector, event type, title, location, dates, access (Free/Paid), audience (Members only/Public), and description

​
How to create an event

Events → Create Event, or from the Dashboard quick actions.
1

Basic details

Enter the event title, start/end dates and times, and select the hosting group.
2

Description and location

Write the event description (rich text with images and links). Add a physical address, an online meeting link, or both.
3

Registration settings

Decide whether people can register, set capacity, configure ticket types, and choose which fields to collect.
4

Visual customization

Upload a hero image, set accent colors, and configure the public page appearance.
5

Publish

Review everything, then publish. The event goes live and members are notified.

​
Event details

​
Required fields

​
Visibility: public vs. private

This is a key decision:

​
Attendable vs. informational

​
Registration settings

When “Attendable” is enabled, configure how registration works:

​
Capacity

​
Registration deadline

Set a date/time after which registration closes automatically. Useful for events with preparation requirements (name badges, catering headcount, etc.).

​
Registration fields

Choose what information to collect when someone registers:
Fewer registration fields = more registrations. Only ask for what you’ll actually use. You can always collect more information at check-in.

​
Ticketing

For paid events or events with multiple registration tiers, enable ticketing. This is a deep topic — see Ticketing for the full guide. Quick overview: you create ticket types (General Admission, Early Bird, VIP, Member, Student), set prices, and optionally limit quantities. Attendees pay via Stripe checkout and receive a QR code ticket.
Paid tickets require Stripe setup. Without Stripe configured, you can only create free ticket types.

​
Event page customization

Every event has a page — for public events, this is what the world sees. Customize it to match your brand:

​
SDG tagging

If your organization tracks impact against the UN Sustainable Development Goals (common for NGOs and civil society organizations), you can tag each event with the relevant SDGs (1-17). These tags feed into Annual Reports for impact reporting.

​
Draft vs. published

Events start as drafts: Work on drafts until everything looks right, then publish. You can still edit most fields after publishing — dates, description, location, tickets.

​
After publishing

Once live, you can:
  • Track registrations — see who signed up in the Participants tab
  • Send invitations — invite specific members or entire groups
  • Send updates — notify registered attendees of changes
  • Manage waitlist — approve waitlisted people when spots open
  • Cancel the event — registrants are notified automatically

​
Common scenarios

Orgo doesn’t have a built-in recurrence feature. Create each instance individually, or create the first one and duplicate it for future dates. For recurring meetings, some organizations create a Private Group with the meeting info pinned as a discussion post, and only create formal events for special sessions.
Yes. You can update the title, description, location, times, and hero image. Registered attendees won’t be automatically notified of changes — use the “Send update” feature to notify them explicitly.
Add both a physical location and an online meeting link. The event page shows both. You might create separate ticket types: “In-Person” and “Online” to track attendance mode.
You need posting permissions in that Local Center. Select the center as the hosting group when creating the event. Or have the local admin create it — they have the permissions by default.
Yes, if the event is public. Non-members register as guests — they provide their name, email, and any required fields. They receive a ticket/QR code by email. They don’t need an Orgo account.

​
Cover images

Event cover images are square, 1:1, output at 800 by 800 pixels. You do not need to crop before uploading. A cropper appears when you add the image and keeps the ratio for you, so upload the original and position it there.
If you keep a set of design templates for event artwork, build them at 1:1. A 16:9 banner will be cropped to square, and the crop takes the centre, so text positioned along the edges of a wide image disappears.
The same image is displayed at several sizes across the event list, the event page and the mobile app. Keep the important content near the centre and it will survive every one of them.