This document provides an overview of the precedence structure for managing recording configurations within our system. It explains how various configuration levels interact and prioritize settings. The recording configuration can be defined at three different levels:
- Start recording a meeting API
- Create a meeting API and
- Organization level specified via developer portal
Understand Recording Configuration Precedence
To comprehend the precedence of recording configurations, it is important to delve into the following details. This understanding becomes crucial when dealing with multiple configurations set through APIs and the developer portal.
|1||Start recording API configs||Highest priority in the system. Any settings defined here will take precedence over other configurations.|
|2||Create a meeting API configs||Second level of priority in the system. Settings here will supersede Org level config but not Start recording a meeting API configs.|
|3||Organization level specified via developer portal||Lowest priority in the system. Settings defined here will be overridden by both Start recording a meeting API config and Create a meeting API config.|
To illustrate the precedence order in action, consider the following scenario for the same meeting:
Org Level Config specifies that recordings to be stored in the AWS bucket.
Create a Meeting API sets recordings to be stored in the GCP storage bucket using the H264 codec.
Start recording a meeting API is configured to store recordings in the DigitalOcean's Spaces bucket using the VP8 codec.
In this scenario, the Start recording a meeting API takes precedence over the Create a Meeting API Config and Org Level Config. As a result, the meeting's recording will be stored in the DigitalOcean's Spaces bucket using VP8 codec, regardless of the defaults set at other levels.