Events & tours

What it is

Events, tours, and writers camps are the three live-activity surfaces in Aden, covering everything that happens off the recording console.

• Events are individual shows, gigs, or performances. They carry a date, venue, set times, a ticket link, and an optional cover image. An event can belong to a team (the performing artist) or to an organisation (the promoter / management company that hosts the show).
• Tours group a run of events into a named series with its own dates and cover. Teams and organisations both manage tours; each tour can contain any number of individual events.
• Writers camps are organisation-hosted creative retreats where a label or management company gathers songwriters. Participants apply via a public signup link; the org accepts or declines them and, once the camp runs, pitches tracks for review.

Using it

Creating and managing events (team)

1. Go to Events in your team sidebar.
2. Click New event, fill in date, venue, start/end times, ticket URL, and optional cover image. The date picker accepts a typed phrase (next Friday 8pm): confirm the result, and times fill start/end when the phrase includes them.
3. Save. The event appears on your public profile page at /@yourslug/events and on any tour it belongs to.
4. To mark a show as sold out or cancelled, edit the event and toggle the relevant flag. Sold-out events show a waitlist signup form publicly.

Right-click an event (a card in the list, a card on the board, or a row in the sidebar's Events tab) for the same actions as the card's … menu: full edit, the public and ticket pages, a post or an email or SMS campaign about it, and Delete with Undo. Deleting the event whose page is open takes you back to the list.

Hosting or playing

The create form opens with one switch: Playing or Hosting. Playing is a show you perform at: the form stays the booking (fee, set time, contract) and your own guest names for the promoter. Hosting is a show you organise: it adds a Guests section (the guest list, reservations and a spot limit), and the event page gets the guest list, the door scanner and the door link under People. Switch it on the event's Details tab later; the guest list keeps its people either way. ⌘K "Host an event" opens the form with Hosting on. Events an organisation creates are always hosted.

Playing a show that's already on Aden? In Playing, Find it searches the upcoming public shows on Aden by name, venue or city. Pick one, choose your role and Ask to play: the host gets an email and accepts or declines from the event's lineup, and the show is in your events right away, marked Requested until they answer.

Your guest list (hosts)

Under People, Add guests takes people from your contacts (Add from your contacts) and one new person per line: Jo Smith +1, ana@example.com, Ana Lopez <ana@example.com> +2. Pick tags for them (VIP, Press, Crew or your own) and leave Email their tickets on to send each guest with an email their QR ticket. Everyone joins your contacts; guests without an email are checked in by name, or get their ticket from Copy ticket link in their row. Typing names in the Guests section of the create form does the same once the event is saved.

The list holds everyone with a spot: people you added, people who reserved from your public page and people who bought a ticket. Search it, filter by tag, change someone's +1s and tags, email a ticket again, or remove them (Undo in the toast). The … menu sends every unsent ticket at once, or opens a campaign to everyone on the list (Email everyone saves the list as a contact group, kept in step, and opens the composer on it).

A ticket opens on the event's public page, or on its own page (/ticket/<id>) when the show has none (a private party, an organisation show with no public lineup yet).

Selling tickets (hosts)

Not open yet: ticket sales are switched off while we test them with Polar. Free reservations and guest lists work as usual.

Tickets sell through your own Polar store, the one you connect in Settings → Shop → Polar, so the money goes straight to you. In the guest list's … menu, Sell tickets takes a price and a currency; Aden makes the ticket a private product in your store. The public event page then shows Buy ticket · €15 instead of the free reservation. Buyers pay on Polar, come back to the event page and get their QR ticket there and by email; a second purchase by the same person adds a +1. The spot limit counts bought tickets too. Sync ticket sales pulls in anyone who paid but closed the tab before coming back. Change the price or Stop selling from the same dialog. Organisations sell through a team for now.

Importing bookings from an agency calendar

Shows booked through an agency tool reach the events board by linking that tool's calendar link: Add → Booking calendars. Holds arrive as pending bookings, confirmed dates as confirmed ones, and the profile publishes only what you allow. The full flow, what a title is read for, and what the feed overwrites are in the calendar spec.

Your shows page

Your profile has one Events tab with every show, upcoming first and past below, one line each. Group by tour switches to /@yourslug/tours, the same shows under their tour. /event, /tour, /shows and /gigs redirect to these pages, on aden.space and on your own domain.

Search engines and AI assistants read your shows too: each one is listed as structured data (venue, city, date, tickets) on your profile, in your sitemap, in the shows page description, and in llms.txt on your custom domain. Private "busy" holds never appear in any of these.

Public event & tour pages

Every event and tour with a confirmed public booking gets its own detail page (/@yourslug/events/<slug> and /@yourslug/tours/<slug>). The cover art opens the page as a poster running the full width of the column, with the way back and the artist over it and the date, title and location reading off its bottom edge. Under it: the ticket, waitlist and info actions, then the description, lineup, tour link and gallery, each a plain block separated by a hairline rule rather than a card. Events or tours without their own cover fall back to the artist's logo/avatar so the page always looks finished.

A tour page lists its dates as an itinerary: one row per show with the date, city, venue and its action, upcoming first and past below, dimmed.

Past shows stay reachable. The public Events tab lists Upcoming first, then a Past archive; the Tours tab and each tour page split shows into Upcoming and Past the same way. Anything that has already happened is dimmed and tagged Past, and its ticket button is hidden, but the page and its details remain viewable.

The create form is split into icon-labelled tabs (Details, Location, Booking, Day-of timing, Tickets & extras). The active tab is kept in the URL (?tab=), and the in-progress draft is saved to your browser so a refresh never wipes what you typed (the draft is cleared once you save or leave).

The Booking tab is two columns: the deal on the left (status, fee + currency, offer/follow-up dates, private notes) and how it shows publicly on the right (visibility, a Preview public page link, and the contract card with its Contract signed toggle). Status, currency and tour are searchable comboboxes. Visibility only takes effect once the booking is confirmed.

The team-side event detail page is organised into sections (Details, People, Setlist, Tasks, Contracts: host-only, Media, Fan feed, Live, Domains), listed in a rail like the account settings (SettingsShell with the shared SettingsNav). Below the lg breakpoint, where the rail is hidden, the same sections are a tab strip. The active section is kept in the URL (?tab=), set shallowly, so a refresh or shared link lands on it and a switch never re-renders the page; a section mounts on first open and stays mounted. Live holds going live and the show's cameras (see live streaming); its rail entry carries a red dot while this browser streams the show, and an organisation's hosted show page shows the same studio as its Live section (#live). The Details section is a read view: event name with the booking status icon, date and venue, the day as a schedule (load-in, your soundcheck, doors, your set with its length, end) and the deal as one value per row (status, role, fee, contract, tour, profile visibility), plus invoice, contracts and hotels nearby. Every value appears once. Clicking one opens the form that edits it on that field; Edit details opens the forms without a field. The forms then show a switch between Event (shared with the lineup) and Your booking (only your team), and Done folds them again. Both panels stay mounted, so unsaved edits survive folding and switching, and each keeps its own save button. The hosting team edits the event in a two-column form; a team booked on someone else's event sees a read-only reference and starts on its booking. The lineup follows below. Booking day-of-timing and offer/follow-up fields use the shared date/time pickers (InputCalendar / InputTime), not native inputs. Booking contacts are picked through a searchable combobox that can also create a new team contact inline.

Browsing the events pipeline

The events list has a toolbar with Preview public page (opens the public profile Events or Tours page in a new tab), Filters, Display and Add on the top right (all the same size), a search box and status tabs below. Status tabs and badges are color-coded with an icon per status (pending/confirmed/lost/declined/cancelled). Display switches between four view modes:

• Recent: events grouped by date.
• List: a flat list.
• Board: a kanban of the booking statuses (drag a card to change status).
• Calendar: a month grid with status-colored chips; click a chip to edit, click a day to create an event on that date.

Filters narrow by status, date range, year, city, country, venue, role and tour; the search box matches name/venue/city/country/tour. All of it lives in the URL, so a filtered view is shareable and survives a refresh.

The Tours tab uses the same toolbar: Preview public page, Filters (year, city, country, venue: matched against the tour's events) and Add on the top right, a search box (tour name, venue, city, country) and All / Active / Ended status tabs below. Tour rows look like event rows. Cover, start date, status badge, event count, and the event chips of that tour. Tour filters use tr* URL params so they never clash with the event (ev*) ones; the status tab uses the shared ?status= param.

Which show to post about

The camera on the Events and Tours toolbars, and on a tour's Events, asks Aden which coming show is most worth making content at. It names the show with its reasons; go with it and Plan the content adds the prep to that show's Tasks. See the decision helper.

Shows to go after

Inquiries has a Suggested tab before New: the shows and money you could go after, beside the ones that came to you. It lists showcase festivals taking applications (ESNS first, for European acts: every act that plays it joins the European Talent Exchange, whose partner festivals book from it), then the live and touring grants of your team's country. Set the country in team settings to get grants.

Add puts it on your team's tasks with its link and, when the call has one, its closing date. Skip hides it, with Undo. ⌘K: "suggested shows", "showcase", "esns".

Attaching the booking contract

The Booking tab of the event create form takes the signed (or unsigned) booking contract straight away. Drop a PDF/DOC/DOCX (up to five files) next to the Contract signed toggle. The files are held in the browser while you finish the form and are uploaded once the event is saved, so a failed save never leaves orphaned paperwork. They land in the shared documents store attached to the event, and stay retrievable from the event afterwards.

Creating a contract from a template, signing it, and sending it to the promoter by link or email is the next step on this surface; the storage side already matches what the signature-request flow expects.

Grouping events into a tour

1. Open Tours in your team sidebar and click New tour.
2. Give the tour a name, optional date range, and cover image.
3. When creating or editing any event, pick this tour from the tour selector. Events in the same tour appear together on the tour's public page.

Inviting another artist to the lineup

On any event you own, open the Lineup panel and search for the other team by its @slug. Aden sends them a booking invite. If you are an admin of both teams the invite auto-confirms.

Taking reservations (team or organisation)

For a free show, a listening night or anything where people should tell you they're coming: open the event, go to Tickets & extras and switch on Reservations. Organisations find the same switch when they create or edit a hosted event. Add a spot limit if the room is small; leave it empty for no limit. The public event page then shows Reserve a spot, with the spots left when there's a limit. Once every spot is taken the page offers the waiting list instead.

Everyone who reserved shows under People → Reservations (on an organisation's hosted event page, under the lineup), with the spots taken against the limit. They're added to your contacts. Remove someone with the × on their row (Undo in the toast). Turning reservations off hides the button; the people who reserved keep their spot until you remove them.

Reserving a spot (fans)

On an event page that takes reservations, tap Reserve a spot and enter your name and email. No account required. Show ticket opens your ticket right away, and a confirmation email follows with the same link.

Your ticket looks like a paper ticket: the event's artwork on top, and a stub with the QR code and its short code. Drag the stub to tear it off for fun, and Put the stub back when you're done. Once the door checks you in, the stub shows as torn and the artwork turns grey. Add it to Apple Wallet or Google Wallet to have it ready at the door, or show it from the email link. Can't make it? Cancel reservation on the ticket frees your spot for someone else.

At the door (hosts)

Open the guest list and tap Scan tickets (⌘K "scan tickets" works too). Point a webcam or your phone's camera at a guest's QR code: they're checked in at once. A ticket with +1s lets in one person per scan until the whole party is in ("Jo is in (2 of 3)"). Scan a used ticket and the scanner says when it was first used and how many times it has been scanned, and the list marks it. No camera, or a code that won't scan? Type the code under the QR. Each row in the list also has its own Check in button (the whole party), and a check-in can be undone.

Door staff on their own phones. In the guest list's … menu, open Door link: scan its QR with a phone, or copy the link and send it to the people at the door. Whoever opens it gets the scanner, the headcount and a name search for guests without a ticket, with no Aden account. Anyone with the link can check guests in, so turn it off when the night is over (⌘K "Scan tickets from a phone").

Signing up to a waitlist (fans)

When an event is marked as sold out, or all its reservable spots are taken, its public page shows a waitlist form. Enter your name and email (and opt in to marketing if you like) to be notified if tickets become available. No account required.

Hosts see the waiting list under People. Email everyone opens a campaign to the people on it (as a contact group), about this event. Give spot moves someone onto the guest list and emails them their ticket.

Org-hosted events

Organisation admins create events at the org level: for shows the org promotes rather than performs. The same event fields apply; the lineup is built by inviting teams through the booking system.

The lineup invite dialog has two modes:

• On Aden: look up the artist team by slug, exactly like the team-side flow. Team admins are notified by email and accept/decline from their own events pipeline.
• By email: for artists not on Aden yet. The org enters a display name + email; a placeholder booking (team_id null, external_artist_name, invited_email) is created with a single-use claim_token (30-day expiry) and the artist receives a claim email. Opening /invite?type=event-booking&token=… walks them through signup, then they link an existing admin team or create a new one (claimEventBooking). The booking stays pending after claiming. Accepting the gig is a separate, explicit step from their team. This is also a signup entry point, like session invites.

Both modes capture an optional fee (amount + currency) on the invite.

Writers camps (organisations)

1. Open Camps in your org sidebar and click New camp.
2. Set dates, location, and a description.
3. Enable the public signup page. Share the signup link with writers.
4. Review applicants in the Participants panel and accept or decline each one. Accepted participants receive an invite email.
5. During the camp, participants pitch tracks; the org team votes to keep or pass on each pitch.

Importing events from Bandsintown

In your team's Events settings connect your Bandsintown profile (paste your Bandsintown URL or API app ID). Once connected, use Import from Bandsintown to pull your upcoming tour dates in one step.