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

# Organizations and Theme Overrides in Livry

> Each Organization is a brand holding overrides on your default theme. Learn how override resolution works and why Organizations don't move between environments.

Livry resolves a theme in two layers: your **default theme**, and the **overrides** held by an Organization.

## Why a default theme

Most brands differ from your baseline in a handful of values — a primary colour, a logo, maybe a font. Storing a complete theme per brand means every future addition to your design system has to be backfilled across every brand you serve.

With a default theme, an Organization stores only its differences. Add a new token to the default and every brand inherits it immediately; brands that need something else override it.

## Resolution

When your application requests a theme for an Organization, Livry returns the default theme with that Organization's overrides applied on top. Your frontend receives one resolved document — it doesn't have to merge anything itself.

## Environment boundaries

<Warning>
  Organizations do not move between Tenants. An Organization created in sandbox stays in sandbox; there is no promotion step that copies it to live.
</Warning>

This keeps environments genuinely independent — a sandbox experiment can never partially leak into production. If you need to mirror brand configuration from sandbox to live, script it against the Management API as part of your own release process, where you control exactly what gets copied and when.