Inside Lumela's Organizer Portal: How Festival Organizers Reach Attendees
Lumela's organizer portal lets a festival's own team edit content and send targeted push notifications to attendees already planning around their event.
Key takeaways
- Lumela's Organizer Portal lets a festival's own team edit schedule, venue and document content, and send push notifications to attendees already connected to the event through the app.
- No separate account is needed — access is a one-festival manager binding granted to an existing Lumela sign-in after a claim (or propose-new-festival) request is reviewed and approved.
- Notifications can target everyone connected, one specific connected group, or guest devices browsing the event without an account, with built-in AI auto-translation.
- A hard quota (10 notifications a day, 5 minutes apart) and a platform-side freeze lever keep the broadcast channel from being misused.
- A stats view shows deduped reach, a 14-day new-connections trend and full push history, plus a groups list by name/size/connect date — without exposing individual member identities.
If you run a festival, the hardest part usually isn't the lineup — it's reaching the people who are already coming. A lineup change, a gate time, a weather call, a last-minute venue swap: none of that is useful if it only lives on a social post that half your attendees never scroll past, or in an email that lands in spam the morning of the show.
Meanwhile, a lot of those same attendees are already organizing their trip to your event inside Lumela — splitting costs, sharing documents, coordinating who's where. Lumela's Organizer Portal exists to close that gap: it lets the team actually running the festival reach the groups already planning around it, without hiring anyone or filing a support ticket with us every time something changes.
Signing in is the easy part#
There's no separate organizer account to set up. If you already have a Lumela account — the same email, Google or Telegram sign-in anyone uses — you request access to your event and, once approved, the portal just appears for that account. Under the hood this is a single "manager binding" tied to one festival; the server enforces it on every request, so there's no way to reach another event's data even by poking at the API directly.
Getting that binding takes one of two paths:
- Claim an existing festival already listed on Lumela — you submit your name, a phone number, a contact email and (optionally) your event's website, and the request goes to Lumela's team for review.
- Propose a new one if your event isn't listed yet — a name, a short description and your dates, also reviewed before anything goes live.
Either way, only one request can be pending per account at a time — you withdraw it before filing another, which keeps the review queue from filling up with duplicates. Approval is still a human decision on Lumela's side, and some things always stay that way: whether your festival is published, its canonical name and how people join it are not organizer-editable, by design.
What you actually get to run#
Once approved, the portal is scoped entirely to your event. You can:
- Edit the festival's content directly — the schedule, venues, documents and task-style checklist items attendees see, plus the subtitle, emoji, icon and dates on your event's page.
- Upload documents attendees might need — a site map, a vendor list, safety info — straight into the same festival-documents space the app already serves.
- Send push notifications, targeted at everyone connected to your event, at one specific group that's connected, or at guests browsing your event without an account yet. You write the message once; an auto-translate pass (built on the same AI machinery Lumela uses elsewhere) can spin it into other languages before it goes out.
A guardrail worth knowing about
Sending pushes isn't unlimited: the portal caps a festival at 10 notifications a day, with at least 5 minutes between sends. It's a deliberate brake, not a bug — a real-time channel to thousands of phones is exactly the kind of thing that needs a limit built in from day one, not bolted on after the first accidental spam.
Seeing who's actually listening#
The portal's stats view answers the question every organizer actually wants answered: is this reaching anyone? It shows the total number of people connected to your event — counted once each, even if someone is active across two of the groups attending — broken down into how many arrived as part of a group versus solo, plus how many guest devices are browsing without an account at all. A 14-day chart tracks new connections day by day, so a spike after you post something is visible, not just assumed. Every notification you've sent shows up in the same view with its status, recipient count and how many devices it actually reached.
There's also a groups view listing every group connected to your event — by name, member count and when they connected — so you can see the shape of your audience, without ever seeing who those individual members are. That boundary is intentional: an organizer gets reach and rough numbers, not a membership list to browse.
If something needs to be pulled, fast#
Lumela keeps one lever on the other side of this: a festival can be frozen from the platform side if something needs to stop immediately. A frozen event's portal goes read-only — the organizer can still see their own content and explain to anyone asking, but can't push, edit or send until it's lifted. It's the same kind of structural safeguard as the one-festival binding: the system is built so that going wrong requires an explicit platform decision, not just a bad click.
Getting started#
If your festival is already on Lumela because a group connected their trip to it, claiming it is the fastest way to start using the channel that's already there. If it isn't listed yet, proposing it is the same request, just starting from a blank page instead of an existing one. Either way, the review happens before anything reaches an attendee — nothing you submit goes live to a single phone until Lumela's team signs off on the binding itself.
For attendees wondering what's on the other side of this: it's the same festival pages behind Lumela's guest mode and the shared lineup planner — the organizer portal is simply how that content, and the notifications about it, actually get kept current by the people running the show.
Plan the next one in one shared place
Lumela keeps the itinerary, the money, the map and the packing list together — free, offline-first, on iPhone, Android and the web.