# Public organisation pages
Source: https://docs.aden.space/docs/help/work-together/public-organisation-pages

Themed public profile for an organisation, its artists, and (for labels) releases and catalogue tracks rendered as the same track cards artists use, with per-section visibility controls, custom-domain support, and shared appearance + editing components.
{/* Generated by `bun docs:publish` from docs/features/public-organisation-pages.md: edit the spec, not this file. */}

## What it is [#what-it-is]

Every organisation gets a public page at `aden.space/o/<slug>`: the org's
equivalent of an artist/team public profile. It shows the organisation's name,
logo, description and links, the **artists** that belong to it, and, when the
organisation is a label, its **releases** and **tracks**: laid out with the
same cover cards and brand-coloured social-icon row artists get on their own
profile. Clicking an artist, release or track takes you to that artist's public
page (or their own custom domain if they have one).

You can style the page with the same theme editor teams use (colours, font,
button style, what to show or hide), choose **which sections appear**
(artists, releases, tracks, venues), and point a **custom domain** at it, so the
page can live on your own web address.

## Using it [#using-it]

* **Edit the public page**: go to your organisation's Settings → **Website**.
  Pick a template, set brand colours and the appearance theme, and use
  **Preview** to see your unsaved changes on `/o/<slug>` before saving.
* **See who appears**: the Artists section lists the active, public teams
  linked to your organisation. The Releases and Tracks sections appear for labels
  and list released albums linked to the organisation and released tracks whose
  label is set to your organisation.
* **Choose what shows**: Settings → **Website** → **Profile sections** toggles
  each section (artists, releases, tracks, venues) on or off for the public page.
* **Use your own domain**: Settings → **Domains** → add a domain, create the
  DNS records shown, then click **Verify**. Once verified, the domain serves
  your organisation's public page.
* **Take demo submissions**: turn on the **Demo submissions** toggle in
  Profile sections and a "Submit a demo" button appears on your public page,
  linking to `/o/<slug>/demos` where anyone can send a demo link (name, email,
  link, genres, message, no account needed). Logged-out visitors also see a
  card nudging them to submit with a free account for a faster response and
  follow-up (see the Demo account incentive feature); the quick no-account form
  stays available below it. Signed-in artists submit **as their Aden account**
  their profile identity plus the option to attach a track straight from their
  library. Submissions land in your org's **Demos** inbox. Off by default.
* **Promo pages**: recipients of your promos land on a personal
  `/promo/<token>` page (cover art, audio player, optional download) where
  they rate the release 1–10 and leave a comment for the label.
* **Marketing website**: beyond the profile, every organisation also gets a
  full marketing website at `/o/<slug>/website`: a full-screen hero (banner
  image or YouTube background video, logo, name, description), a fixed nav,
  stacked sections (Artists, and for labels Releases and Tracks, plus a
  Contact form that emails your configured contact addresses) and a footer
  with your social links. Org managers edit it **inline**: open the page,
  click the edit pencil, then reorder sections, show or hide them, and save.
* **Custom blocks**: while editing the website, **Add block** inserts your
  own content between the built-in sections: a **Text** block (eyebrow,
  heading, body: e.g. an "Our story" section) or a **Call to action** block
  (heading, text, and a button linking anywhere). Blocks can be reordered,
  edited, hidden, or removed like any section. The same custom blocks are
  available on team websites (`/@slug/website`).
* **Website on your domain**: when adding a custom domain, tick the website
  checkbox to serve the marketing website at the domain root (instead of the
  profile), with `/contact`, `/terms` and `/privacy` served under it. The
  same website mode team domains have.