Aden
ProductCollaboration & teams

Writers camps

Org-run songwriting camps that group studio sessions, manage a roster of writers, and let people join either by personal invite (auto-join) or a public open-form signup link (with an optional price to join). Logged-in applicants can review, edit, or opt out of their submission. Camps surface on the in-app calendar, ICS feeds, the MCP server, and mobile, and unfurl with a rich OG image when shared.

What it is

A writers camp is a songwriting event an organisation runs: a roster of writers and producers, a set of studio sessions over a few days, and the tracks that come out of it. The organiser builds the lineup, schedules people into sessions, and afterwards reviews the songs and decides what to do with each one.

People get into a camp in one of two ways:

  • Personal invite — the organiser adds someone by name/email and Aden sends them a private invite link. Opening it (and signing in or creating an account) joins them to the camp automatically — no extra "accept" step.
  • Open signup link — the organiser turns on a public signup page and shares one link. Anyone with it can view the camp and apply without signing in (no account required to apply); the organiser then accepts or rejects each application. If you're already signed in to Aden the form shows your account and lets you pick which of your teams you're attending with.

Using it

Run a camp (organiser).

  1. Create a camp under your organisation and set its dates, location, and branding (logo + banner).
  2. On the People page, add writers from your organisation/teams or invite new people by name and email. While the camp is a draft, invites are queued — hit Publish & send invites to email everyone at once. The page is split into server-side ?tab=lineup|roster|add|applications|responses tabs (each tab's data streams in under its own Suspense boundary so the send-invite actions never wait on the slow lineup query). The Roster tab lists everyone on the camp and lets organisers remove a participant from the camp entirely (removeCampParticipant — also drops them from any sessions).
  3. Optionally open the camp's public signup link in Settings → Public signup, add an intro, and share the link anywhere.
  4. Build the lineup by dragging people into sessions, then send everyone their personal schedule. Each session card on the lineup links out to the full session editor on the team sessions surface (/app/teams/[teamId]/sessions/[sessionId]) for rich editing, and the quick-edit dialog can link a real studio room from the organisation's studios (studio_id) instead of only free-text venue fields.

Join by personal invite. Open the link from your email. If you already have an Aden account you sign in; if not, you create one (no invite code needed). As soon as you're signed in you're dropped straight into the camp. If the invite includes a document to sign, you sign it first, then join.

Join by open signup link. Open the link (no login needed) and fill in your name, what you play, an optional note, and any custom questions the organisers added. The camp's location links straight out to maps. If you're signed in, your account is shown and you can choose which team you're attending with; otherwise you can still apply as yourself. Your application goes to the organisers, who accept or reject it — you'll hear back by email.

Price to join. Organisers can optionally set a price to join a camp (shown on the public signup page as a "… to join" badge). Leave it empty to keep the camp free.

Edit or opt out after signing up. If you're signed in and have already applied or joined, the signup page shows your existing submission with its status instead of a blank form — you can edit your name, roles, note, and answers, or opt out to remove your submission (you can sign up again later if you change your mind).

See your camps everywhere. Camps you're part of show up on your Aden calendar as a multi-day event, in any calendar you've subscribed to via the camp's ICS feed, and in the Aden mobile app under a dedicated Camps screen.

Was this helpful?

On this page