The Organizer Guide

Tap Create from the home screen to start a new event. You'll fill in:

• Title, description, date & time, location (or an online event link for virtual events).
• Cover image - upload your own or generate one.
• Visibility - public, private, or invite-only (see section 2).
• Paid event toggle - turn your event into a ticketed event with a price, ticket limit, and optional per-person cap (see sections 4-5).
• Attendance tracking - opt into per-day check-in tracking for multi-day events (see section 9).
• Polls - add nomination-style polls attendees can vote in (see section 13).

Happa deduplicates accidental double-submits: creating an event with the same title and date twice in a row returns your existing event instead of creating a duplicate.

Visibility	Who can see it	How people join
Public	Anyone, discoverable in the app	Open - anyone can join or buy a ticket instantly
Private	Only people you share the link with	Requires your approval (join request)
Invite-only	Only people you explicitly invite	Requires your approval (join request)

Before you can publish a public event, Happa asks you to verify your identity once. From Settings → Verify as organizer, you'll submit:

• A government-issued ID (national ID, passport, driver's licence, or voter ID).
• Your personal details as they appear on the document.

A member of the Happa team reviews the submission and either approves it or rejects it with a reason - you'll get a push notification either way. Verification only needs to happen once; after approval, every public event you create is unlocked immediately.

Turn on Paid Event while creating your event to sell tickets. You'll set:

• Ticket price in TZS (Tanzanian Shillings) - currently the only supported currency.
• Ticket limit - the total number of tickets available for the whole event.

Attendees pay by mobile money or from their Happa wallet balance. Once a payment is confirmed, a ticket is issued instantly with its own QR code. Ticket price and ticket limit lock in once at least one ticket has sold or is mid-purchase - this protects buyers from a price changing under them after they've paid.

Optionally cap how many tickets a single person can buy in one purchase (1-10). Leave it blank for no limit beyond the app-wide maximum of 10 per purchase. This is a simple anti-scalping control for in-demand events - set it low (e.g. 1 or 2) for high-demand or invite-style paid events.

Open Ticket Design from your event's organizer tools to customize what attendees see on their ticket:

• Accent color and an optional background image.
• Header note (e.g. "Doors open 7:00 PM") and fine print (e.g. "Bring a valid ID").
• Toggle whether the date, location, and attendee name show on the ticket.
• Scan limit - how many times each ticket can be scanned before it's marked used (default 1, to prevent sharing a screenshot).
• Ticket transfers - allow or block attendees from sending an unused ticket to someone else (see section 10).

Every attendee's ticket renders from this same design, and changes apply immediately to unscanned tickets.

Open the Scan tool from your event to check attendees in with your phone camera. Each scan is validated on Happa's servers, not just on-device, so a screenshot or fake QR code will never pass:

• The ticket must belong to your event and be fully paid.
• The QR code's embedded secret must match exactly.
• A ticket already used shows "already checked in" instead of admitting twice.

For simple, single-day events, each ticket admits once (or up to your configured scan limit for legacy group tickets). For events with attendance tracking enabled, see section 9 for how check-in works across multiple days.

You don't have to scan every ticket yourself. From Scanner Invites, invite trusted people to scan tickets at the door on your behalf. Once they accept, they can open the Scan tool for your event without needing to be the event's organizer of record - useful for large events with multiple entry points.

For festivals, conferences, or any event that runs across specific days (not necessarily consecutive - you choose the exact dates), turn on Attendance Tracking when creating your event and list the dates that count (e.g. a Friday and the following Sunday, skipping Saturday).

How daily check-in works

1. An attendee's ticket can only be scanned on a date that's in your list. Scanning outside those dates is rejected.
2. Once scanned for a given day, that ticket can't be scanned again that same day - it unlocks again the next tracked date.
3. If someone misses a day entirely, nothing "breaks" - their ticket keeps working on every later tracked date. A missed day is simply never made up retroactively.

Viewing the report

Open Revenue on your event to see a day-by-day breakdown (how many people checked in each day) and a per-attendee summary (days attended vs. days missed). This report is computed live each time you open it - there's nothing to configure or wait for.

By default, attendees can send an unused ticket to another Happa user directly from their ticket screen - useful when someone can no longer attend. The recipient gets a request they can accept or decline; nothing transfers until they accept.

• Only unused, valid tickets can be transferred - once checked in, a ticket can no longer move.
• You can turn transfers off entirely from Ticket Design if you'd rather tickets stay locked to the original buyer. Turning transfers off only blocks new requests - any transfer already accepted before you turned it off stands.

Every paid ticket sale credits your Happa wallet. From your event's Revenue screen you can see total revenue by currency, tickets sold, checked-in count, cancellations, failed payments, and anyone who's wishlisted your event (asked to be notified when tickets go live).

From Wallet, you can:

• See your available balance and full transaction ledger.
• Request a payout to withdraw your available balance.
• Top up your wallet balance via mobile money, which you can then spend on tickets to other events.

Free, social events (recurring meetups, community gatherings) have their own lightweight roster: turn on Attendance Tracking, list the dates, then mark people present or absent per date from the event's attendance screen - like a sign-in sheet. Percentages and per-attendee attendance rates are calculated automatically.

Add nomination-style polls to your event (e.g. "Best Dressed," "Song of the Night"). Configure whether results are always visible, only after voting, or only after the poll closes, and whether votes must be attributed to a named voter or can be anonymous.

Attendees can post comments and replies on your event page. As the organizer, you can delete any comment or reply on your own event in addition to deleting your own.

For private and invite-only events, people who want to attend submit a join request instead of joining instantly. From Join Requests you can approve or reject each one - approving adds them as an attendee immediately.

If an event about you or your brand already exists on Happa (for example, imported from a social media link) but you're not listed as its organizer, you can submit a claim with proof of ownership. Happa's review team checks the evidence before transferring organizer control - track your submissions from My Claims.

Generate a shareable poster image for your event straight from the app, ready to post to your own social channels, with your event's key details and a QR/link back to the Happa event page.

Beyond ticket revenue, your event's analytics view shows engagement over time - views, joins, poll participation - so you can see what's landing with your audience across events, not just a single one.

The Plugins marketplace lets you install third-party tools built on the Happa Plugin Platform - automations, analytics dashboards, CRM sync, and ticketing add-ons built by outside developers. Every plugin in the marketplace has been through Happa's review process before listing.

• Installing a plugin gives it a scoped, revocable connection to your event data (only the specific permissions it requests - e.g. reading attendees, not your wallet).
• You can uninstall any plugin at any time from the Plugins screen.
• Plugins that touch payments or other regulated financial workflows go through additional, invite-only review before they can be listed.

If you're a developer wanting to build a plugin, see the Plugin Platform documentation.

To keep the platform fair for organizers and attendees:

• QR check-in validation, per-day scan locks, and per-person ticket limits are enforced on Happa's servers, not just in the app - they can't be bypassed by a modified client.
• Fraudulent verification documents, payment fraud, or chargebacks are grounds for account termination and forfeiture of pending payouts to the extent permitted by law.
• Escalated disputes (a claim over event ownership, a rejected verification, a disputed refund) are reviewed by Happa's admin team, who may request more evidence from either side before deciding.

Questions about anything in this guide? Reach out to support@happa.site.