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

# Understand the Layarva Object Model

> Understand how Workspaces, Locations, Channels, Screens, content, publishing, and Queue Units relate.

## What you'll accomplish

You will learn which Layarva object owns each configuration, how content reaches a television, and which timezone controls an operation.

## Core hierarchy

```text theme={null}
Workspace
├── Locations
├── Channels ── Screens
├── Library ── Assets and Fonts
├── Studio Designs
├── Playlists ── immutable Playlist Versions
├── Publications ── Playlist Version → Channel
├── Schedules ── timed Publication rules
├── Campaigns ── Placements → generated Schedules
└── Queue Units
    ├── Categories
    ├── Counters and Operators
    ├── Kiosks
    └── Queue Displays → Channels → Screens
```

## Distribution chain

The most important chain is:

```text theme={null}
Design or media → Playlist draft → Ready Playlist Version
→ Publication → Channel → one or more Screens
```

<Note>
  A **Channel** is the distribution unit. A Screen follows one Channel; publishing directly to an individual Screen is not the normal delivery model. Ten televisions showing the same content can share one Channel and remain ten separate Screens.
</Note>

## Mutable and immutable boundaries

| Object           | Mutable? | Purpose                                          |
| ---------------- | -------- | ------------------------------------------------ |
| Design           | Yes      | Editable Canvas document.                        |
| Playlist draft   | Yes      | Editable item sequence.                          |
| Playlist Version | No       | Exact sequence used for delivery and reporting.  |
| Publication      | No       | Exact Playlist Version assigned to a Channel.    |
| Schedule         | Yes      | Timing rule that activates an immutable version. |
| Campaign Draft   | Yes      | Commercial plan containing Placements.           |

Players never resolve a mutable Playlist draft at runtime. Publishing first pins the exact Ready version.

## Workspace and Location timezones

Layarva uses two timezone concepts:

* **Workspace timezone** controls how dashboard readers interpret and display dates and times.
* **Location timezone** represents where the Screen physically operates. It controls local playback-day boundaries and reporting dates.

For example, an Admin in Jakarta can read the dashboard in `Asia/Jakarta` while a Screen in Makassar uses its Location timezone for the day on which a playback event is counted.

## Queue isolation

A Queue Unit is an isolated branch operation. Its Categories, Counters, Operators, Kiosks, Displays, API credentials, and ticket sequence cannot be mixed with another Queue Unit.

Queue content has additional structural rules:

* One Queue Design belongs to one Queue Unit.
* A Queue Playlist contains exactly one Queue Design with a 24-hour duration.
* Queue Channels and Displays must remain inside the same Queue Unit chain.

## Related guides

* [Understand Publishing](/studio/publishing)
* [Manage Screens, Channels, and Locations](/screens/overview)
* [Queue Management Overview](/queue/overview)