DISTROBOLT

DISTROBOLT ARTIST GUIDES

Who can approve distribution of a co-owned master?

Distribution of a co-owned master requires an authority review against the relevant agreements and law. An account owner, performer credit or royalty percentage does not by itself establish authority to approve every use of the recording.

Separate the ownership and access records

List the master, claimed owners, agreements, authorised representatives and current distributor account. Identify the exact proposed use and territories. Distinguish a recording-income allocation from the ownership position. A collaborator can receive income without being the person authorised to grant the distribution licence.

Review the applicable approval rule

Joint-ownership rules and contractual authority can differ by jurisdiction. UK government guidance, for example, describes agreement by joint owners for uses of jointly owned work; do not apply that as a universal rule for every master everywhere. Have a qualified adviser resolve uncertainty in the actual documents before submission.

Prepare evidence for the intended grant

Record who can approve distribution, what uses are covered, duration, territories and any conditions. Keep the signed authority or permission tied to the exact master. Do not rely on a casual message approving a preview as proof of permission for a broader commercial release. Record missing or disputed authority explicitly.

Confirm the distributor process

Ask DistroBolt what evidence and account route are required for the case. Do not upload while presenting unresolved consent as settled, or claim that delivery acceptance establishes ownership. Preserve the source documents and approved metadata snapshot. This checklist neither grants authority nor changes accepted splits or rights.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

Continue your release planning

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.