Share unreleased music for review without sharing the whole project

Choose the review task and recipient first

A listening review, a mastering handover and a press preview need different materials. State the decision you want: arrangement feedback, approval of the final master, a visual edit check or consideration by a journalist. Send the smallest useful package for that task rather than the whole project archive.

Identify the recording version, intended recipient, allowed purpose and requested response date. If the music or visuals involve collaborators, check who may authorise the proposed sharing. A restricted link controls access in a service; it does not settle ownership or replace an agreement about confidentiality.

Separate restricted access from an unlisted link

In Google Drive, Restricted access limits opening to people who have been given access. Anyone with the link is a different choice. Viewer, Commenter and Editor permissions differ, and folder permissions can affect the files inside. Review the actual sharing panel for the item and its containing folder before sending it.

An unlisted YouTube video can be watched and reshared by people with its link. It may also be exposed through a public playlist. Private video sharing is a separate option for selected viewers, with different interaction limits. Neither setting is a promise that the material cannot be copied or disclosed.

Choose a method that fits the recipient and sensitivity. A private reviewer who needs to hear a master is different from an outlet asking for a publicly shareable premiere. If the intended use changes, review the permission and materials again instead of treating the first link as permanent approval.

Build a small advance-listening record

Use the following fields in your own private project notes. This is a suggested worksheet, not a DistroBolt upload form or a request to submit private details here.

• Purpose: the decision or coverage being requested.
• Version: recording title, version, date and approved filename.
• Recipient: the verified reviewer and their agreed role.
• Materials: listening file or video, short context and only necessary credits.
• Access: selected people or link access, permission level and whether downloads are intended.
• Timing: response date, any agreed embargo and access-review date.
• Outcome: feedback received, decision made and where the approved version is stored.

For instance, a fictional artist sends one named engineer a reference and current mix for mastering feedback. The public press folder contains different, approved images. The artist checks both links separately and avoids exposing the private agreement through the press folder. This is an original workflow example, not a customer story.

Test the exact sharing experience

Use a non-owner view or an intended authorised reviewer to confirm what opens. Check the link you will actually send, not an earlier copy in your notes. Confirm that the right file plays, the name identifies the version, the reviewer can perform the intended task and unrelated folders are not exposed. Do not widen access automatically just because someone encounters an error.

• The reviewer and purpose are verified.
• The file is the intended version and includes no unrelated private material.
• The actual item and parent-folder access have been reviewed.
• The intended recipient can open and use the material as agreed.
• Any agreed embargo and follow-up are recorded separately from link settings.

Working checklist only. Ticks are not saved or sent to DistroBolt.

After the review, keep the feedback with the version it refers to. Review whether the access is still needed and retain your own approved files. Use the release-archive guide for long-term retention and the engineer-handover guide for production deliverables.

Common questions