Skip to content

Recording voice consent

Keeping a record of who agreed to have their voice cloned, for what, and where the evidence is held, plus what happens the moment consent is withdrawn.

Updated

A cloned voice cannot exist in Social Studio without a consent record behind it. This page is that record.

It does not ask anyone for consent. Consent is given between people, offline. What you record here is what was agreed, by whom, to which named purposes, and where the signed form or recorded confirmation is kept, so the claim can be checked later rather than taken on trust.

Withdrawing consent is immediate and final. Every cloned voice resting on it is disabled at once, and it cannot be re-enabled. If the person agrees again later, that is a new record, not a reversal of the old one.

BEFORE YOU START

  • The "administer" permission to record a consent or add a voice, and "generate" or "administer" to withdraw one. Withdrawing is deliberately easier than recording.
  • The "view" or "generate" permission to read the page.
  • Consent actually obtained, offline, and a note of where the evidence lives.

STEPS

  1. Open Voice consent, or go to /app/voice-consent.
  2. Record the consent: whose voice it is, their email if you have it, and which uses they agreed to. At least one use is required.
  3. Say where the evidence is kept. This is a reference to the signed form or recorded confirmation, not the recording itself.
  4. Choose "Record this consent".
  5. Add a cloned voice: name it and choose which current consent covers it.
  6. To withdraw, open the consent, give a reason, and choose "Withdraw this consent".

WHAT YOU SHOULD SEE

The consent listed with its standing, the uses it covers, and the voices resting on it. A voice can only be added while a consent is still current.

WHAT THIS WILL NOT DO

  • It will not obtain consent. There is no way to send a request to the person from here.
  • It will not cover a use nobody agreed to. Consent covers named purposes only.
  • It will not let you undo a withdrawal.
  • It will not restore an expired consent. Ask the person again and record a new one.

IF IT DOES NOT WORK

  • "Consent has expired. Ask the person again before using this voice." means the record has aged out.
  • "Consent was withdrawn. This voice cannot be used, and cannot be re-enabled without a new consent record."
  • "A cloned voice requires a consent record." means you tried to add a voice with none.
  • "That consent could not be recorded. Recording consent needs an administrator."
  • "That voice could not be created. A cloned voice needs a consent that is still current."
  • "The consent records could not be read, so they are not shown. That is not the same as there being none - reload the page before assuming no consent is on file." Take that literally.
  • Where the page says no voice can be added right now, it tells you how many records have expired and can be renewed, and how many were withdrawn and cannot.

COMMON QUESTIONS

Someone has asked to be erased. What happens?

There is a separate control that erases the person's identity from the record while keeping the consent history itself. The record then shows the subject as erased.

Does recording consent switch anything on?

No. It permits a cloned voice to exist. Whether voice generation itself runs depends on a provider being active in your deployment.

  • Setting your brand voice

    Reusable steers for generation - tone, length, reading level, audience, words to avoid and words to include.

  • Running a creator collaboration

    Recording a piece of work a creator has been engaged for, moving it through its lifecycle, tracking deliverables and reviewing what they submit.

  • Managing your media library

    Registering assets with their rights and consent, organising them into folders, and what "ready" means when a post publishes.