Project Hierarchy

In The Library, projects are more than just containers — they form a hierarchy. Think of it like folders within folders on your computer, but purpose-built for managing your music workflow. A parent project can gather tracks from itself and all its child projects, giving you flexible ways to organize your songs by album, client, release wave, or creative phase.

This guide explains parent relationships, parent aggregation, and multi-project assignment.

How Projects Form a Hierarchy

Projects in The Library can be nested. Any project can serve as a parent to other projects, creating a tree structure that mirrors how you naturally think about your music.

For example, you might have:

2025 Releases (parent)
- Q1 Singles (child)
- Q2 EPs (child)
  - Summer Vibes EP (grandchild)

When you select a parent project, the app automatically collects tracks from the parent and every descendant beneath it. This means you can view all your Q1 work by selecting “2025 Releases,” or drill down to just the Summer Vibes EP by selecting its bucket directly.

System Buckets

Some buckets are system-created and protected. The Archived bucket, for instance, stores tracks you’ve finished or shelved. You can assign tracks to it alongside other projects — archiving doesn’t remove a track from its active buckets.

Selecting Projects

Selecting a parent includes tracks assigned to that project and all descendant projects. Selecting a child includes the child only, not its parent or siblings. Cmd/Ctrl-click can combine bucket IDs in a union selection.

Assigning Tracks to Projects

Use bucket-selection controls to manage which projects a selected track group belongs to.

Single Track Assignment

The control shows available buckets and current assignments. It supports toggle assignment and marks shared assignments that the current user cannot manage as locked/read-only.

Multiple Track Assignment

For multiple tracks, the service normalizes assignment sets and preserves multiple existing bucket memberships unless the selected operation removes them.

The Unassigned Option

At the top of the bucket list sits an Unassigned checkbox. Selecting this removes the track(s) from all projects entirely. This is useful for clearing old assignments or starting fresh with a new organization scheme.

How Parent Aggregation Works

Understanding parent aggregation helps you navigate efficiently. Here’s the behavior at a glance:

Selection	Tracks Shown
Parent project	Parent + all descendants
Child project	Child only (no siblings, no parent)
No bucket filter	All tracks across all projects
”Unassigned” filter	Tracks not in any project

This design means you can always widen or narrow your view. Start broad with a parent, then drill down when you’re ready to focus on a specific release or group.

Deadline Cascading

When you update a project’s deadline, The Library automatically cascades it to tracks in that project that do not already have an individual due date.

Tips

Use parent projects for broad views — Select a parent when reviewing all tracks for an album or quarter, then switch to children when working on specific releases.
Tracks can live in multiple buckets — Don’t feel pressured to pick one home for each song. A track can belong to a client project and an album project simultaneously.
Archive doesn’t erase — Moving a track to Archived keeps it there alongside its original project assignments. It’s not a move — it’s an additional label.

Creating Projects — Set up your first project and organize your workspace.
Assigning Songs — Assign individual and multiple tracks to projects using the Activity Panel.
Project Due Dates — Set deadlines and cascade dates across your project hierarchy.
Multi-Project Selection — Select and filter by multiple projects at once for batch operations.