Skip to content

Sharing with Collaborators

The Library separates collaborator roster and track assignment from the transfer-first sharing flow. This guide covers those two related workflows. Public link delivery is covered in the sharing guides.


A collaborator is a person assigned to a track group. The central roster is reusable contact data; assignment creates the track-specific collaborator record. A public link is a separate, token-gated delivery mechanism.


Add a collaborator to the selected track group or groups, then set master, publishing, and writer split values. The service validates the projected total for each target track group before it persists the assignment.

Adding a collaborator record does not itself grant a completed share. The separate invitation and sharing flow determines when a registered recipient can accept and when shared content is imported.


The Library tracks three independent allocation values:

  • Master split
  • Publishing split
  • Writer split

The collaborator service rejects an add or update that would make a split dimension exceed 100% for a target track group.

The app can suggest an even split constrained by the remaining allocation. Review and adjust the values for the track before saving.

Instead of manually adjusting each percentage, click Auto-allocate to evenly distribute splits across everyone on the track. This is useful when you’ve just added multiple collaborators and want a quick, fair starting point.

The app divides master and publishing splits evenly and rounds to practical precision. Review writer values separately.

The split panel shows your current totals in real-time. You’ll see:

  • Green when total equals 100%
  • Amber or red with a warning when total exceeds 100%

You cannot save changes that would cause any split dimension to exceed 100%. The app blocks the save and shows a message explaining the issue.


Owners can update collaborator data and split values for their track groups. Only the owner can remove a collaborator; removal reconciles the person’s direct, member, and bucket access paths before the collaborator row is deleted.


Use a public share link for selected-content delivery, subject to its file allowlist, permissions, expiry, and Dropbox connection. Do not treat that link as a collaborator assignment. See Creating Share Links for the delivery contract.


When someone invites you to collaborate on their track, you’ll see a notification badge in the app header. Clicking it opens the Collaboration Invites modal.

  1. Click the notification badge (shows the number of pending invites)
  2. Review the track details — you’ll see the song name, artwork, and who sent the invite
  3. Click Accept next to the track you want to join

After accepting, the collaboration enters the asynchronous share/import workflow. File availability depends on the sender’s shared-folder path being synchronized; use the invitation guidance if the transfer is still pending.

For a recipient using The Library, acceptance completes the Shares row and starts asynchronous import processing. A missing sender folder path is a sender repair condition.


If you regularly work with the same people, save them in your central collaborator roster. It is reusable contact data; assign people explicitly to each track group that needs them.