AI and automation
Muin Agents Workflow Automation Muin Assistant AI Support Widget Document Intelligence Intelligent Intake ReconciliationEngage and get paid
Smart Payments Giving Pages Smart Forms Kiosks + QuickPay Muin Go Mobile Communications Hub Self-Service Portals E-SignaturesBusiness modules
Nonprofit Finance HR Compliance Spend Education Volunteers Aid All Business ModulesAnswers on running events in Muin — publishing a public event page, taking registrations and tickets, checking attendees in, and seeing who came.
10 questions
1. Go to **Non-Profits** → **Events** and click **New Event**. 2. Pick the kind of event, or describe it in plain language and let Muin draft it. 3. Fill in **Details** (name, public link, location) and **Schedule & recurrence** (date, start and end time). 4. Under **Capabilities**, turn on what people can do, **RSVP to attend**, **Sell tickets**, **Recruit volunteers**, **Distribute aid**. Any combination is allowed on one event; the ones typical for the type you picked are marked **Recommended**. 5. Set visibility to **Public (anyone with the link)**. 6. Click **Create**, then **Publish**, or **Submit for approval** if your organization has an approval rule covering events. Only a **Published** event accepts registrations. Draft, awaiting-approval and cancelled events do not.
Yes. There is one event and one editor, and the capabilities are independent switches, **RSVP to attend**, **Sell tickets** and **Recruit volunteers** can all be on for the same event. A gala can sell tickets and recruit volunteers; a distribution day can track recipients and volunteers. Attendees and volunteers are counted separately. **Max attendees** covers RSVPs, and anyone who would push the event past it goes on the waitlist with their position. Volunteer spots are set per shift and role, and each one has its own waitlist. The event's **Waitlist when full** setting (Unlimited by default, Up to a number, or Off) applies to the attendee waitlist and to each shift and role's waitlist.
1. Open the event and expand **Ticketing**. 2. Under **Discount codes**, click **Add code**. 3. Enter the code, choose **Percentage off each ticket** or **Amount off each ticket**, and set the value. 100 percent makes the ticket free. 4. Optionally set a **Ticket limit** (how many tickets the code may discount in total) and an **Expires** date. Buyers type the code on the payment step and the total updates before they pay. A code that makes every selected ticket free skips payment, and the buyer confirms the free tickets instead. A use is counted only when a ticket is paid for or claimed, so an abandoned checkout does not spend the limit. For a ticket that includes goods or services, the tax-deductible part is worked out from the discounted price. You can turn a code off at any time; tickets already bought keep their price.
Three common reasons, and the editor tells you which one: - **A ticketed event with no ticket types.** *"You'll add at least one ticket type after saving, required before you publish."* Add one and Publish unlocks. - **A distribution event with no recording method.** Choose per recipient or headcount batch first. - **The event is awaiting approval.** *"This event is with its approvers. You can keep editing it, publishing unlocks as soon as they decide."* If you see *"The approval rule that covers events cannot be run as written"*, the rule itself is misconfigured, an administrator can repair it under **Settings** → **Approvals**.
Yes, but only use it when you need to. The built-in registration form already collects name, email, phone and party size. Bind your own form to the event, from the sign-up form panel in the event editor, when you need something extra like dietary requirements, a t-shirt size or an accessibility note. An event that takes both RSVPs and volunteers has two separate sets of questions: **RSVP questions** for attendees and **Volunteer sign-up questions** for volunteers. Each group only sees its own, so a volunteer is never asked an RSVP question like "What are you bringing?". The editor flags any problem with the form you picked before a visitor hits it. Responses to a bound form are reachable from the event's **Analytics** screen via **Form responses**.
Open the event and choose **Analytics**. Four cards answer it directly: **Registered** (with cancellations beneath), **Total guests** (including party members), **Capacity used**, and **Checked in**. Below the cards, a funnel shows how many people viewed the public page against how many registered, and a **Sign-ups over time** chart plots the registration curve day by day. Until someone registers it reads **"No sign-ups yet"**.
Yes. On the event's **Day-of** check-in board, use **+ Walk-in**. It creates the person and an attended registration in one step, asking only for a name and a contact detail, so they land in your directory alongside everyone who registered in advance. For a paid event you can take the money at the door too: in Muin Go, open **Pay** → **Event Ticket**, pick the event, enter the attendee's name and email, and let them tap their card.
Yes. Day-of check-in is its own permission rather than a tenant-admin role, so you can give a door steward exactly that and nothing else: the **Door Check-In Steward** role. On the web they open **Events**, then **Check-in**, and pick the event. In Muin Go they open **Events** and tap **Check In**. If the board will not open at all, that permission is missing, ask your owner or admin to grant it.
Yes. Check-in, check-out and no-show are all reversible from the same row on the day-of board, so a mistaken tap is not permanent. If a card or badge tap does nothing, the credential is not recognized, use **Find a volunteer (no scanner)** to search the roster by name or email and check the person in from their row. A badge that reads as revoked needs a new one issued to the attendee.
In your People directory. Every RSVP creates or updates a person with the **attendee** role and a label recording which event captured them, so you can follow up, invite them to the next event, or include them in a campaign. To message everyone who came, build an audience from **Directory** → **Audiences** and use **Email this audience**. RSVPs are attendance intent, not a volunteer commitment, volunteer signups are tracked separately.
Our support team is happy to help with any questions.
Contact Support