> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orriven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Speakers

> A speaker is an attendee with a profile — invite them like any guest, mark them as a speaker, then assign their sessions from one place.

A speaker is not a separate kind of person in Orriven — it is a **profile layered on top of an attendee's registration**. The person first registers for the event like anyone else; you then mark that registration as a speaker and give it a public profile: name, title, bio, and a schedule of sessions.

Find them under **Program & venue → Speakers** in the event navigation.

## Get the speaker registered first

Because a speaker *is* an attendee, the person must have a registration before you can add them. The typical flow for invited speakers:

<Steps>
  <Step title="Create a hidden guest ticket">
    On [Ticket types](/en/ticketing/ticket-types), create a ticket (e.g. "Speaker") and set its visibility to **hidden** — it won't appear on the public event page.
  </Step>

  <Step title="Create a redemption code for it">
    On [Offers & redemptions](/en/ticketing/offers), create a code that unlocks the hidden ticket, and send the share link to your speaker.
  </Step>

  <Step title="They register">
    The speaker follows the link and registers like any guest. Alternatively, you can key them in yourself on the [Attendees](/en/events/attendees) page.
  </Step>
</Steps>

## Add and edit a speaker

Click **Add speaker** and search for the attendee by name or email. If no match comes up, they haven't registered yet — invite them first as above.

On the speaker's page you can edit:

* **Name** — seeded from the registration, but editable on its own. The stage name doesn't have to match the badge.
* **Title** — e.g. "CTO, Acme".
* **Bio** — the public introduction.

## Assign sessions — from the speaker's page

The **Schedule** section on the speaker's page is where you connect a speaker to sessions on the [Agenda](/en/program/agenda). Check the sessions they're on and save — the schedule is edited from the speaker's side, not from the session's.

<Note>
  **Assigning a gated session grants the speaker access to it.** If a session requires perks, adding the speaker to it automatically grants those perks to their registration — so they can enter their own session without any extra ticket work. The grant is **additive**: nothing the person already holds is taken away, and if you later remove the session from their schedule, the granted perks are **not** revoked.
</Note>

## Rules to know

* **One profile per registration.** A registration can be marked as a speaker once; a speaker is always exactly one attendee in this event.
* **The registration comes first.** You cannot create a speaker from thin air — there is no "speaker-only" identity. If they shouldn't hold a visible ticket, use a hidden guest ticket.
* **Removing a speaker keeps everything else.** "Remove speaker" deletes only the profile: the person's registration stays, and any perks granted through session assignments stay too.
* **Name, title and bio are yours to edit** without touching the underlying registration. Use **View attendee** to jump to the registration itself.

<Tip>
  Speaking slots often come with green-room or backstage access. Model those as perks bound to the speakers' guest ticket — see [Perks](/en/ticketing/perks) — rather than handling them ad hoc.
</Tip>