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.
Before applying guidance from another version
Check your selected version before applying recording instructions. These rebuilt tasks were checked against 0.9.17-patch2 and the reviewed Next source; that does not establish behavior in older releases.
A runtime control and a persistent storage policy need separate scope and permission checks.