Speaker support

Purpose and prerequisites

Use this for Programming or event-operations support of a linked speaker. The speaker portal routes are /speaker, /speaker/profile, and /speaker/sessions; /speaker/brief is separately registered. Do not use an admin account to silently rewrite a speaker profile without approved editorial ownership.

Procedure

1. Confirm the speaker identity and the exact session or material in question.
2. Have the speaker open /speaker first. If the portal is unavailable, follow access troubleshooting and verify the speaker relationship.
3. For biographical changes, use the profile route; for session-specific details, use the sessions route. Preserve approved program copy unless Programming approves a change.
4. For materials, use the speaker material workflow and verify that file visibility matches the intended audience. Do not move files between storage locations manually.
5. If a brief is missing or inaccurate, capture the route/session and escalate it for review; generated output is not a source of truth.

Expected result and recovery

The speaker can see and update only their intended content, and the public/session view reflects only approved material after the normal publish path. If an edit is wrong, restore through the supporting admin/CMS workflow where available. Stop and escalate content-attribution conflicts, unexpected access to another speaker’s material, AI-generated brief quality or safety concerns, and disputed ownership to Programming and Product.