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

# Presenters and consent

> The colleagues who appear on screen, how they are invited, and why nothing is produced until each of them agrees.

**Where:** the **Cast** section of a profile

Every recipient sees a person. Which person comes from your list: the colleague named in their row,
usually the sales rep who owns the relationship. Together those colleagues are the profile's
<Tooltip tip="The presenters in a Personalization Profile. Each accepts a casting request and gives consent before production can run."><strong>cast</strong></Tooltip>.

## Nobody appears without agreeing to it

<Warning>
  **No colleague's face or voice is used until they have given <Tooltip tip="A presenter's explicit agreement, given in their own account, to appear in this outreach. Without it, nothing is produced for them."><strong>consent</strong></Tooltip>, from
  their own account, for this specific outreach.** There is no way around this and no administrator
  override. It is a product principle rather than a setting.
</Warning>

This is not only an ethical position, it is a practical one. The person on screen is vouching for
your message to someone who knows them. Their explicit agreement is what makes that credible.

## What happens when you sign off a profile

1. The cast is built from the presenter columns in your recipient list.
2. Each colleague receives a casting request.
3. They set up their presence and grant consent, in their own account.
4. Only then can recipients assigned to them be produced.

The whole of step 3 is theirs, and it is short. Send them
[You have been cast](/docs/guides/presenters/you-have-been-cast), which is written for exactly that
moment.

## Watching for who is holding things up

The profile's cast section shows every presenter and where they are: invited, set up, consented, or
declined. It is also where you resend an invitation.

A recipient whose presenter has not consented cannot be produced. When you later run a batch, the
batch tells you the same thing more loudly: it names the presenters who are blocking it and counts
the recipients affected, with a link straight to the cast.

<Note>
  **A missing account is the most common cause of a stuck cast.** A presenter has to be a LatentCast
  user in your organization, and the email in your recipient list has to be the one they sign in with.
  A typo there looks exactly like someone ignoring their invitation.
</Note>

## What a presenter is agreeing to

Worth knowing, because you will be asked:

* Their avatar and voice may be used to present **this** outreach, not everything forever.
* They choose which avatar and which voice, from their own library.
* Changing that choice later makes the earlier consent stale, and they are asked again.
* Their consent covers the languages their voice set covers.

## Next

<CardGroup cols={2}>
  <Card title="You have been cast" href="/docs/guides/presenters/you-have-been-cast">
    The page to send to a colleague who has just been invited.
  </Card>

  <Card title="Proving it on one recipient" href="/docs/guides/personalization/proving-one-recipient">
    Once someone has consented, produce their first recipient.
  </Card>
</CardGroup>