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

# Assigning contracts to tracks and releases

## Overview

Qlero allows contracts to be attached to individual tracks or releases to control how income from sales and costs are divided. Each piece of repertoire — a track or a release — can have one or more contracts attached.

## Track-level vs release-level assignments

An important distinction exists between these two approaches:

* **Track-level**: Applied to specific recordings when the financial split varies by individual recording
* **Release-level**: Applied to the entire release, typically for income reported at the release level (such as physical sales)

Critically, these assignment types operate independently—attaching a contract to a release does NOT automatically apply it to its individual tracks, and vice versa.

## Assignment components

Each contract assignment consists of three elements:

1. **Contract** — The specific contract participating in income or costs
2. **Connection type** — Determines participation scope:
   * Sales (income from sales)
   * Costs (allocated costs)
3. **Participation rate** — The percentage of relevant amounts the contract receives

Note that participation rates need not total 100%, allowing partial coverage scenarios.

## Configuration overrides

Both tracks and releases support overrides that modify contract assignments based on specific dimensions:

* Sale type (e.g., streaming vs. physical)
* Source (e.g., specific distributors)
* Store (e.g., particular retailers)

Overrides replace standard assignments when conditions match and can be cleared to restore regular assignments.