> ## Documentation Index
> Fetch the complete documentation index at: https://confidence.spotify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recording Rules

> Configure policies and rules that control which browser sessions Confidence records.

## Policies and Clients

Configure recording policies under **Recordings > Settings** in the Confidence UI.
Create one recording policy for each client. A policy contains an ordered list of
rules for that client.

Confidence evaluates enabled rules in order. A rule matches when its environment,
targeting, audience allocation, and session sample all pass. The first matching rule
applies. If a rule does not match, Confidence evaluates the next rule.

If no rule matches, the SDK does not record the session. Account capacity can also
prevent capture.

## Required Roles

| Action                                 | Required access                                                                                                      |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Create a policy                        | Account Owner, Admin, Super Admin, Creator, or Recording Policy Creator                                              |
| View a policy                          | Policy owner, Account Owner, Admin, Super Admin, Reader, Editor, Recording Policy Reader, or Recording Policy Editor |
| Edit or delete a policy                | Policy owner, Account Owner, Admin, Super Admin, Editor, or Recording Policy Editor                                  |
| Create, edit, delete, or reorder rules | Edit access to the parent policy                                                                                     |

A user with only Creator or Recording Policy Creator access can manage a policy that
they create because they own it. They cannot edit policies that other users own.

## Rule Types

You can add three types of rules.

### A/B Test Rule

Select an existing A/B test. The rule uses the experiment segment, allocation, and
targeting. The **Limited to** value controls the percentage of matched sessions to record.

### Rollout Rule

Select an existing rollout. The rule uses the rollout segment, allocation, and
targeting. The **Limited to** value controls the percentage of matched sessions to record.

### Conditional Targeting Rule

Define conditions with context attributes and segments.

* **Record** controls the percentage of the matched audience eligible for recording.
* **Of** selects the context field that identifies a user or another targeting entity.
* **Limited to** controls the percentage of sessions recorded for each included target.

For example, you can include 20% of premium users and then record 10% of each included
user's sessions.

<Note>
  Recording rules select who and what to record. They do not change the flag
  variant that a user receives.
</Note>

## Environments

All rule types can apply to selected environments. Environment selection uses the
environments associated with the client secret. It does not use a custom
`context.environment` value unless you also target that value in a condition.

## Manage Rule State and Order

You can create a rule as a draft or create and activate it immediately. You can also:

* Enable or disable a rule
* Edit or delete a rule
* Drag rules to change their evaluation order

Review the complete ordered list after every change. A broader rule near the top can
select sessions before a more specific rule.

## Manual SDK Mode

Manual mode controls when the SDK tries to start recording. Recording rules,
sampling, and account capacity still apply. See
[Troubleshoot recordings](/docs/recordings/troubleshooting) for lifecycle details.