Recordings and storage
Separate the task of using recordings from configuring their storage and interpreting their output.
Find the right instructions
| Your task | Start here |
|---|---|
| Choose app outputs, including transcript-only storage | Choose what a call recording retains |
| Set the team's bucket, access and retention responsibilities | Configure team recording storage |
| Investigate missing files, frequency or playback | Diagnose recording storage and processing |
| Review a recorded conversation | Conversations |
For common recording file and JSON fields, use the recording output reference. Recording is a shared capability; this reference is publicly readable. Integration-specific metadata has its own contract. Documentation access is separate from permission to read product recordings.
Match the documentation version to your release
Check the documentation version selector before applying recording instructions. Each version describes the recording behavior of that release; older releases can differ.
A runtime control and a persistent storage policy need separate scope and permission checks.
Related
- Choose what a call recording retains — to change which outputs a flow keeps
- Configure team recording storage — to set the shared destination for recording uploads
- Recording output reference — to read the files and JSON fields a call produces