Sign-in required — organizer scopes.
Changes what this night is called — everywhere it is read: the event page, the listing, passes and the door list. It does not change the event's link, so anything already shared keeps working. Confirmations already emailed keep the name they were sent with.
Where the night is. The address is what the map link is built from — a venue name alone is not enough, because it resolves to whichever one the map provider prefers.
What the app files this night under. It is what a guest who has told ATLAS what they listen to is matched against, and it is what heads a section on Explore. Leaving it empty is a real answer — the night is listed as unclassified rather than filed under a genre nobody stated. ATLAS never guesses one.
Typing is not restricted to the list. A genre nobody has used yet is not an invalid genre, so a new one can always be saved — the panel above just says, before you save, what the one you typed will actually do.
Every change saves against this event only. Each row shows what it is currently set to; open one to read what it actually does.
Prints the finish time on the event page beside the start. Leave it off for a night with no fixed end — a stated finish time is a promise guests plan their travel around.
Puts the count of confirmed guests on the public page. It reads as momentum on a night that is selling and as a warning on one that is not, so it is a choice per event rather than a house style.
Lets a guest pass their ticket to someone else from their pass. The original ticket is voided as the new one is issued, so the door list stays exactly as long as the guest list — and the person at the door is the person holding the pass, which is the point.
Once a tier sells out, guests can join a queue for it instead of hitting a dead end. Offers go out in order as capacity frees up, each with an expiry — never a broadcast to everyone at once.
Every request waits for you rather than being admitted on payment. Pending requests appear under Run; nobody holds a valid ticket until you approve them, and a declined request is told so.
One line under the title on the event page — the sentence that sells the night to somebody who has not heard of it. Left empty, the page shows the title alone.
Restricts this night to members of a private club. ATLAS does the checking itself: a guest signs in, and only a membership the club has confirmed opens the door. A membership a guest has merely claimed does not — they are told what would have to happen and cannot check out until it does, so a gate you set casually comes back as questions and refund requests. Tick nothing and the night is open to everybody.
Loading the club gate…
You are choosing club names from a registry ATLAS curates. Ticking one changes nothing on its own — the night is gated when you press Save, and not before.
Loading the club registry…
ATLAS never asks anyone — you or a guest — for a club login, a password or a membership number, and this panel never tells you who belongs to what. Each guest is told their own answer and nobody else's.
Saving takes effect immediately. On a night that is already selling, from that moment nobody without a confirmed membership can check out. Tickets already sold are untouched and still scan at the door.
Paste the address of a site you already run. ATLAS reads its public page and suggests colours, a logo and a hero image — nothing is saved until you pick from them and press Save in the form below.
Loading…
Saving replaces the entire brand package atomically. The form is pre-filled from the current version so editing one field keeps the rest — clearing a field removes that piece from the package.
Live preview — a mini mock of the event pass, driven by this form.
Serve this event's site from a domain you own. Binding here only tells ATLAS which event the domain means — the mapping and DNS happen at the infrastructure level.
Loading…
Runs this event again as a new edition in the same series. The clone is born a draft — never live by side effect — and anything it does NOT carry (date-anchored settings) is listed with the result, out loud.
Publish, take down and cancel now live in the header beside the event, because they are things you reach for while looking at the event rather than things you go hunting for. What is left here is the one act you should have to go looking for. ATLAS refuses any of them that would leave a guest holding a dead link.
Cancel — for a night with guests. Stops selling and drops off the listing, but the event page stays up saying it is cancelled. It does not refund anyone; do that from the Orders view.
Delete — drafts with no orders only. For clearing out a test event.
Loading…
Price is entered in dollars and stored as integer cents. An RSVP event admits free, so every tier on one must be zero — the same rule Publish enforces, said here before you get there.
Kind — Admission admits one person per ticket. Table is priced per table: one purchase takes a whole table and admits up to that table's capacity; zone/floor narrow which of the venue's tables it sells, blank sells every table. Add-on is an extra sold alongside a ticket; it admits nobody by itself.
Leaving capacity blank sells without a cap. A tier can only be removed while nothing references it — once an order, ticket, waitlist entry or resale listing points at it, ATLAS refuses rather than orphaning the row. Price, fee and capacity cannot be edited after creation; kind and table scope can (kind only while nothing references the tier).
Each link carries a code stamped onto orders at the click. An order with no code reports as its own honest Unattributed line — never redistributed.
Loading…
Guests join per tier once it sells out. Promotion is an idempotent queue tick — the button runs the same tick the scheduler runs, immediately. Every status here is the server's word, with expiry applied as of this load — a lapsed offer reads "expired" here even before the queue's next tick settles it in storage.
Loading…
Loading…
Saving replaces the entire content block atomically — lineup, FAQ, policies and safety together. The form is pre-filled from the current version so a partial edit carries the rest along; anything you clear here is removed on save.
Announcements are service messages to ticket holders — they appear on every guest's pass once published. Scheduled ones stay hidden until their time.
Operator view — includes scheduled announcements guests cannot see yet. The published/scheduled state is the server's word, never computed here.
Loading…
Photos and video guests uploaded through the pass. Takedown deletes the file from storage permanently; the row stays behind as the audit trail.
Loading…
Paste a guest list, or choose a CSV exported from wherever you keep one. ATLAS reads it and shows you what it could and could not make sense of. Reading writes nothing: the rows are saved when you tick them and press Save, and not before.
Nothing read yet.
Every contact lands unreachable and is asked to confirm for themselves. Most of a list asked this way never answers — that is the ordinary outcome and not a fault in the list or in the asking, so expect to keep a book you can recognise a guest from rather than one you can write to.
Every contact lands reachable and nobody on the list is asked anything. You are the only check there is, so ATLAS writes down who made the claim, when, and what they said it rests on.
Importing is not permission to message anyone. Every contact you save here arrives with consent never_asked, and ATLAS will not send them an announcement, an email or an SMS on that basis — not once, not as a one-off, and not to tell them they have been imported. They become reachable only by confirming for themselves, which they do by finding this event rather than by being sent to it. What you are saving is a list you can recognise a guest from at the door, not a list you can write to. That costs you the send: if you imported these people in order to announce something to them, this import will not do it, and nothing further down this page will.
Vouching is a statement you are making, and ATLAS records that you made it. Every contact you save this way arrives with consent attested and is reachable from that moment — an announcement, an email or an SMS can go to them, and not one of them will have been asked first. Nobody on this list gets the chance to say no before the first message lands. What is written against this import is your name, the date, the basis you picked and the note you wrote, kept as you wrote it; that note is what is read back to a contact who asks why they were messaged, and to anybody asking on their behalf. ATLAS cannot check whether the permission exists — it can only record that you said it does, and who said it. If you are not certain it covers these people, Ask each person is a line above this one, and what it costs you is the answers you do not get.
Loading…
Loading…
The arrival curve draws only hours in which someone actually scanned — the future is never drawn.
Loading…
Loading…
What this event owes you, from the server's own sums. Fees are the platform's and never part of the payout; pending orders sit beside the totals, never inside them. A negative balance is an advance already paid — shown plainly.
Loading…
Owed is computed only where terms exist — an unknown is named, never rendered as $0. Attributed orders that predate a promoter's terms owe nothing and are counted out loud. Unattributed revenue stays unattributed — never redistributed.
Loading…
These belong to your venue, not to the event selected above — the picker does not apply here. A listing is a night you are running that ATLAS does not sell tickets for: it shows in the app’s feed alongside your ticketed nights and sends people to wherever the tickets actually are.
Loading…
“Who is selling them” is shown to the guest beside the link, so they know what they are about to leave to. It is typed rather than guessed from the address — a URL is not a brand name.
“City” is what a guest who has told ATLAS where they live is matched against. Leave it empty and the listing still shows in the app — but as a night whose city ATLAS does not know, never as one in the city somebody asked for.
“Genres” is what the app files the night under and what a guest’s taste is matched against. Leave it empty and the listing is unclassified — an answer, not a gap. The panel above says what each one you type will actually do before you save it; some words ATLAS treats as a kind of night rather than a genre, and a few it treats as no answer at all.
A new listing starts as a draft. Nothing appears in the app until you publish it.
build atlas-00436-rdf