Skip to content
The Library

Default Project Collaborators

The supported workflow is a reusable central collaborator roster, followed by a separate track-level assignment step. A roster entry is not an automatic project template: saving someone to your roster does not add them to existing or future tracks by itself.

Build Your Collaborator Roster

Section titled “Build Your Collaborator Roster”

During onboarding, you can save the people you regularly work with by entering their name and email address. The Library stores those people as central collaborator records owned by your account.

Use this roster to avoid repeatedly entering the same contact details when you later assign collaborators to tracks.

What Happens When You Add Someone

Section titled “What Happens When You Add Someone”
  • Email addresses are normalized before duplicate checks and saving.
  • Repeated entries with the same normalized email are de-duplicated.
  • A newly created roster entry can trigger a managed signup invite when the person does not already have a Library account.
  • Existing Library users continue through the normal collaboration invite and share workflow.

Invitation delivery is asynchronous. A temporary email-delivery problem does not prevent the roster entry from being saved.

Assign Collaborators to Tracks Separately

Section titled “Assign Collaborators to Tracks Separately”

After track groups exist, use the track-level collaborator workflow to assign people from your saved roster. This assignment is a separate action from roster creation and is the point at which track-specific collaboration details belong.

You can assign a saved collaborator to one or more track groups. For a bulk track assignment, The Library sends at most one managed signup invite for that request, even when the person is added to several track groups.

Keeping the Roster Useful

Section titled “Keeping the Roster Useful”
  • Add people you expect to work with again.
  • Check spelling and email addresses before saving.
  • Use the track-level collaborator workflow whenever a person needs access to a particular track group.
  • Review the related sharing and invitation guidance before expecting a recipient to have shared-folder access.
Section titled “Related”