How the features work, in plain language, for the people who run them
Chapter 1
An event on Eventure is a date, a place, and a way for people to sign up. From that spine you can sell tickets, cap the crowd, collect answers to your own questions, and check people in at the door - or keep it as simple as a time and a title.
You manage your events at My Events. This chapter walks the event form top to bottom - it is one screen, built from cards you open only when you need them - and explains the choices that trip people up most: how people register, what a ticket can be, and when your instructions reach attendees.
The top of the form is the part every event needs: a title, a short description for cards and listings, and a full description written in blocks - headings, images, lists, whatever the event deserves. Set the date and time (an event can run to a second date, or become a whole series of linked dates), pick a location (a venue, an online link, or both), and add a featured image. Everything below that is optional - reach for it when the event calls for it.
The Registration card decides who can find the event and how they sign up. Four settings inside it are worth a closer look - each carries its own help icon on the form.
Who can reach the event page at all. Public is listed on your profile and in search. Unlisted is reachable only by the exact link - handy for a soft launch or a members-only date you share by email. Private asks every visitor for a password you set, so even someone with the link cannot look in without it.
What happens the moment someone clicks Register. The two that surprise people: Requires approval holds each sign-up until you say yes, which is right for a vetted group but means nobody is confirmed automatically; and External link hands the visitor off to another site entirely and switches the built-in ticket flow off, so use it only when registration truly lives elsewhere.
| Registration type | What happens |
|---|---|
| Open | Instant confirmation - the attendee is in the moment they finish. |
| Requires approval | You review each request and approve or decline it. |
| Invite only | Only people you invite can register. |
| External link | Register sends people to another site; the built-in ticket flow is skipped. |
The most it will take. Zero means unlimited - a blank or 0 capacity does not close the event, it opens it wide. Set a real number only when the room, the boat, or the licence says so; once it fills, new sign-ups are turned away unless the waitlist below is on.
What happens after capacity is reached. With the waitlist on, a full event still takes names into a queue instead of a flat "sold out", and when someone cancels the next person in line can be promoted into the freed spot. With it off, full simply means closed.
A ticket is a way to attend. An event can have several - an early-bird and a full price, a member and a guest tier - each with its own name, quantity, and sales window. If your event is free with no tiers, you can skip this card entirely; registration alone is enough. The price model of a ticket is where Eventure is more flexible than most:
| Ticket kind | What the attendee pays |
|---|---|
| Free | No charge. Registration only. |
| Fixed price | A set amount you choose, paid at checkout. |
| Donation | Pay what you wish - the attendee names the amount, above any minimum you set. |
| Energy exchange | Something other than money - a skill, a contribution - described in words, arranged between you. |
Instructions are the private note only registered attendees see - the door code, the exact meeting point, what to bring.
When that note becomes visible. Immediately shows it the moment someone registers; 24 hours before holds it back until the day is close, which suits a location you would rather not publish weeks ahead; at check-in keeps it hidden until they are at the door. Sensitive details stay sensitive until they need to be known.
Any event can grow a set of linked dates - each its own bookable occurrence with its own attendees - which is how a one-off becomes a weekly series without duplicating the whole event. On the day, the check-in screen scans each attendee's QR code so you can see who has arrived, and attendees can add the event to their own calendar from an ICS link.
An event you are still shaping is a draft: only you can see it. When it is ready, Save & Publish puts it live at its public address; Save as Draft keeps it private while you keep working. You can unpublish at any time - it drops back to a draft, and the page goes quiet until you publish again.
Publish early, then keep editing. A published event updates the moment you save, so there is no penalty for putting a rough version live to claim its address and refining it after. Nobody sees a draft, so a draft nobody sees helps nobody.
Chapter 2
Activities are the recurring things your organization does - a weekly class, a monthly meetup - that individual events belong to.
An activity is the recurring thing; an event is one occurrence of it. "Tuesday yoga" is an activity; the specific class on the 14th is an event. You create activities so individual events have a home to hang under - a visitor who lands on one can see the whole series and the group behind it.
An activity is a description, not a booking. It gathers events, tells the story of the offering, and points people at the next date. When you want a signup, a capacity, or tickets, that lives on the event linked to it, not on the activity itself.
On any event form, the Link to Activities picker ties that event to one or more of your activities. It is how an event joins the umbrella, and how visitors discover related events and the group that runs them.
Chapter 3
An organization is your presence on Eventure: its profile, its members, its events and shop, and its own public website.
An organization is your account's public face and the owner of everything you make - events, articles, shop, community, website. Almost every "Create" begins by asking which organization it belongs to. You can run more than one; a person can wear several hats.
You invite people by email, and each member holds a role that decides what they can touch: owner (everything, including billing and deleting the org), admin (manage content and members), member (a lighter hand), and billing (the money, nothing else). Invitations carry an expiry, so a link left unopened eventually lapses.
Beyond the profile page, an organization can have a full public website of its own - its own address, pages, and look - built in the Website Builder. That is a large enough subject to have its own manual; the Help button inside the builder opens it.
Chapter 4
Content is the flexible writing space - a blog, news, articles, pages, or an FAQ - built from blocks.
Content is the flexible writing space behind your blog, news, articles, standalone pages, and FAQ. They are the same tool wearing different labels: you pick a content type, and the listing, the address, and the feel follow from it.
The body is built from blocks rather than one long box - a heading, a paragraph, a quote, a list, an image, a gallery. You add them with the + button and drag to reorder, so a post is assembled the way a page is, not typed into a single field.
Categories are the folders (each content type keeps its own set); tags are the loose labels shared across everything, with usage counts. Comments can be nested, and you set the moderation stance per type: open to all, guests-need-approval, or off.
Chapter 5
Prize games are raffles, spin-the-wheel, scratch cards, and quizzes that hand out tickets, products, or coupons.
A prize game is a giveaway with a mechanic. Pick the one that fits the moment: a raffle draws winners after the fact; a spin the wheel and a scratch card reveal a result on the spot; a quiz awards a win for a good enough score.
A prize can be an event ticket, a shop product, a discount coupon, or something custom you fulfil yourself. For the first three the win is wired through: the platform can create the registration, the order, or the coupon automatically, so the winner does not wait on you.
Entry can be open, registered-only, action-based (join the newsletter, make a purchase, refer a friend), or by invite code. For a raffle you press Draw winners once entries close and the platform picks against the prize weights; the on-the-spot games decide as each person plays.
Chapter 6
Surveys collect answers - nine question types, anonymous or named, with results and CSV export.
A survey is a set of questions - short text, long text, single choice, multiple choice, dropdown, rating, number, date, and yes/no. You build them in order and mix the types as each question needs.
A survey has a life: draft while you build it, active while it collects answers, closed when you are done - with optional start and end dates so it opens and shuts on its own. You can also cap responses per person.
Decide up front whether answers are tied to a person or anonymous; it changes what you can see, and cannot honestly be undone after the fact. Results come as per-question statistics and completion rates, and the whole set exports to CSV.
Chapter 7
Songs are chord charts that a reader can transpose, capo, and read on guitar, ukulele, or piano.
A song is a chord chart: the words with chord names sitting above them. You write it once in ChordPro - plain text where a chord in square brackets marks exactly where it falls in the line - and the reader is rendered from that.
Whoever opens the song can transpose it a semitone at a time, set a capo, and choose to see the shapes for guitar, ukulele, or piano - the same chord names, drawn for their instrument. Their choices stick for next time.
If you add a melody line, the reader can switch between chords, letter notes, and both, in letters, solfege, or numbers. An autoscroll speed group lets them play hands-free and, if you allow it, the whole chart downloads as a tidy PDF.
Chapter 8
Songbooks are ordered collections of songs, each parked in its own key, printable as one PDF.
A songbook is a collection of your songs in a deliberate order - a worship set, a lesson plan, a gig list. You search your library and drag songs into the sequence you mean to play them in.
The point of a book is that every song in it carries its own settings without changing the source: a per-song transpose and capo, a personal note, and a section label (say "Warm-up" or "Encore"). A singer can hold a song in their key inside their book while the original stays exactly as written.
The book downloads as a single PDF - an optional cover, a table of contents grouped by section, then each song already transposed and capoed the way you parked it. Toggles let you drop the cover or the contents when you want only the songs.
Chapter 9
Courses are classrooms: modules and lessons, self-paced or drip-fed, with learner progress.
A course is a curriculum: modules that hold lessons. How a learner moves through them is the unlock mode - self-paced (all open), sequential (finish one to reach the next), drip (lessons release days after enrolling), challenge (a fixed cohort on shared dates), or library (browse freely by tag).
A lesson can be written in blocks, a PDF, an embedded video (YouTube or Vimeo), an uploaded video or audio, or a live class linked to an event. You build the shape once; the learner sees a clean classroom.
Access can be free self-enrolment, a one-time purchase (buying auto-enrols them), or a manual invite. Once in, learners work a sidebar of modules with a progress bar, mark lessons complete, and pick up where they left off - notes they type are saved as they go.
Chapter 10
Galleries show photos and videos in four layouts, with optional albums and lightbox.
A gallery shows images and video in the layout that suits them: a tidy grid, a masonry wall that respects each image's shape, a carousel that advances one at a time, or a lightbox that opens each full-size on click.
Alongside uploaded photos, a gallery can hold YouTube and Vimeo videos by their link, so a highlight reel sits next to the stills without re-hosting anything.
When one wall would be too much, group items into albums - by trip, by year, by theme - and the gallery shows the covers first, opening a set on click.
Chapter 11
Offers are your shop: physical, digital, and service products with variants, stock, and coupons.
The shop sells physical goods (they ship), digital goods (they download), and services (a session or a slot). Which one you pick decides what the rest of the form asks for - a shipping weight, a file, or neither.
A single product can carry variants - size, colour, an option of your own - each with its own price and stock. Inventory tracks levels, warns you when they run low, and can allow backorders when you want to keep selling past zero.
A digital product delivers a secure download with limits you set - how many times, for how long. Coupons take off a percentage, a fixed amount, or the shipping, so a campaign or a member perk is a code rather than a changed price.
Chapter 12
Bookings are appointments against a schedule - a service, its availability, and confirmed slots.
A booking is an appointment against a service you define - its length, its price (fixed, hourly, free, or donation), how many can attend at once. The service carries a weekly availability schedule; exceptions layer holidays, closures, and special hours on top of it.
A request moves pending → confirmed → completed (or cancelled, or no-show). A cancellation policy - flexible, moderate, strict, or none - sets how late someone may back out, and a booking can be rescheduled to a new slot rather than lost.
A service can be physical, online (with a meeting link), or both. On the day a QR check-in marks arrivals, a calendar file drops the slot into the attendee's own calendar, and afterwards you can gather a rating.
Chapter 13
Communities are discussion spaces - threads, replies, and members - grouped under your organization.
A community is a discussion space your organization hosts. Its type sets the door: public (anyone reads and joins), private (visible, but join to take part), or secret (invisible until invited).
A post can be a plain discussion, a question, an announcement, a poll, or a file share - each shaped for its job. Replies, likes, and reactions hang off them, and members can message one another directly.
Roles run from owner through admin and moderator to member. The tools let you pin or lock a post, hide content, and mute or ban a member - enough to keep a busy space civil without heavy machinery.
Chapter 14
Subscribers are your newsletter list, verified by email and syncable to your email marketing tool.
Subscribers are the people who asked to hear from you. A signup is not trusted until it is verified: the person clicks a link in a confirmation email, which keeps the list clean and the addresses real.
Names arrive from the newsletter box on your pages and profile. Each one remembers where it came from, so you can tell a homepage signup from one gathered at an event.
If you run campaigns in Mailchimp, MailerLite, or a compatible tool, subscribers can sync outward automatically, tagged by source, so your list lives in one place while it grows here.
Chapter 15
Orders are the record of what was bought - status, payment, and fulfilment.
An order is what remains after someone buys - the line items, the total, the buyer, and the moment. Orders are created for you at checkout, whether the sale came from the shop or a paid ticket; you rarely make one by hand.
An order moves through a lifecycle - pending → confirmed → processing → shipped → delivered - and you nudge it along as you fulfil it. A digital order skips the shipping steps; a service order completes when the session does.
Each order records how it was paid and whether it cleared, and a paid order can set the rest in motion on its own - a ticket, a course enrolment, a download, a CRM contact - so marking it paid is often the only action you take.
Chapter 16
Build requests are website jobs an operator picks up and builds for you.
A build request is a job: someone wants a website built and an operator picks it up. It is the queue that sits between "I would like a site" and a finished build.
Each request holds the brief - who it is for, what they want, and any material they supplied - so whoever takes it has enough to begin without a meeting.
This section is for platform operators rather than everyday organizers; most people will never see it. If you are one, it is where you claim a request and track it through to done.