Creating Projects

Projects are the backbone of your workflow in The Library. Think of them as folders or playlists where you group related tracks together — whether that’s all the songs for an album, tracks for a specific client, or songs at a particular stage of production.

What Are Projects?

Projects act as containers that hold your tracks. They help you stay organized by letting you group songs based on whatever makes sense for your workflow. A project can be a release, a client’s folder, a playlist for sync licensing, or simply a way to categorize your work-in-progress tracks.

Each project has:

A name to identify it
A color to visually distinguish it in the sidebar
A deadline to track due dates
A track count showing how many songs it contains
Optional description and deadline information

You own every project you create, which means you control who can access it and what they can do with the tracks inside.

Creating a New Project

Create a project with a non-empty name. You can also provide an optional description and deadline. The service trims the name and description, creates the record for the authenticated owner, and returns the created project.

Project Settings After Creation

After creating a project, you can refine it further by selecting the project in the sidebar and opening its settings panel. Here you can:

Update the name or description — Keep things current as your project evolves
Change the color — Adjust it if your branding changes
Set or adjust the deadline — Update due dates as timelines shift
Use your saved collaborator roster — Roster entries are reusable contact data; assign a person explicitly to each track that needs them

System Buckets

Your workspace includes a special system bucket called Archived. This bucket is created automatically and serves as a holding area for completed or inactive tracks. You can rename and reorganize all your own projects, but the Archived bucket is protected — it exists to keep your workspace tidy and can’t be deleted or renamed.

Organizing Tracks Within Projects

Once you have projects, use bucket-selection controls to assign tracks to them.

Assigning Tracks

The bucket-selection control supports multi-select and reflects current assignments. Shared-bucket assignments that the current user cannot manage appear locked, and optimistic changes roll back if persistence fails.

Project Hierarchy

Projects can have a parent-child relationship, which means you can create sub-projects under larger ones. This is useful for:

Album releases — A parent project for “Summer EP” with children for each song
Client work — A parent for a client’s entire account, with child projects for each job
Stage grouping — Organize tracks by production stage while maintaining category groupings

When you select a parent project in the sidebar, you see tracks from that project and all its children. Selecting a child shows only that child’s tracks.

Deleting Projects

If you no longer need a project, you can delete it. Select the project in the sidebar, open its settings, and choose Delete Project.

Deleting a project removes the project and its associations. It does not delete the tracks themselves.

Tips

Use consistent naming — Establishing a naming convention (artist name, release type, date) makes it easier to find projects later
Set deadlines early — Even if the date changes, having a target helps prioritize your work
Use colors strategically — Assign colors based on genre, client, or status so you can spot projects at a glance
Add descriptions — A quick note about what’s in the project saves confusion later, especially for clients or collaborators
Use your saved collaborator roster — Save regular collaborators once, then explicitly assign them to the tracks where they are contributing

Project Hierarchy — Learn about organizing projects in parent-child structures
Assigning Songs — Master the different ways to add tracks to projects
Project Due Dates — Track deadlines and cascade dates across tracks
Multi-Project Selection — Work with multiple projects simultaneously