> For the complete documentation index, see [llms.txt](https://developer.perculus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.perculus.com/v2-en/policies/recording-enforcement-policy.md).

# Recording Enforcement Policy

### Overview

Recording Enforcement Policy allows organizations to control recording behavior across all sessions. When enabled, this policy overrides individual session recording preferences to ensure compliance with organizational requirements.

### How It Works

#### Hierarchy

1. **Account Level** (Highest Priority)
2. **Session Level** (Only applies if account level is None)
3. **User Preference** (Only applies if both above are None)

#### Enforcement Modes

**None (0)**

No enforcement applied. Users and sessions can control their own recording settings.

**On (1)**

Recording is enforced to be **enabled**:

* Recording automatically starts when session begins
* Users cannot disable recording
* Applies to all sessions under the account

**Off (2)**

Recording is enforced to be **disabled**:

* Recording cannot be started
* Users cannot enable recording
* Applies to all sessions under the account

### Configuration

#### Account Level

Set via Panel → Settings → Policy Management

#### Session Level

Set via `enforce_recording` parameter when creating/updating sessions (only effective when account level is None)

### Important Notes

#### For API Integration

* Recording parameters sent via API are accepted and stored
* If enforcement policy is active, values will be overridden when the first participant joins
* No API errors will occur, but the enforced policy takes precedence

#### For Rooms

* Rooms do not support session-level enforcement
* `enforce_recording` is always None for rooms
* Only account-level enforcement applies to rooms