Licensing

Where Licensing fits in the Collab workflow

Use the Licensing tab in a Collab project to centralize how you define who may use your content, where it can appear, and under what commercial terms.

From the app, follow this path:

• /collabs → select a project
• /collab/{id} → Distribution
• Licensing tab

Today this tab shows a Coming Soon placeholder. The planned experience will add a guided license-generation flow so you can capture license terms consistently alongside your compliance records and shared files.

What you see today in Licensing

The current Licensing tab shows a static Coming Soon message:

"Manage content licensing agreements, territories, and usage rights."

There are no interactive fields or actions yet:

• No buttons to add or edit licenses
• No way to upload existing contracts
• No PDF or document generation
• No reporting or exports

Treat the tab as a preview of where licensing controls will live once the feature ships, not as a replacement for your existing legal workflows yet.

What Licensing is planned to cover

Licensing is designed to sit alongside File Sharing and Compliance so that each Collab project keeps:

• Compliance artifacts (IDs, releases, age verification) in the Compliance tab
• Deliverables and source files in the File Sharing tab
• Usage rights and commercial terms in the Licensing tab

The planned Licensing experience will revolve around a guided wizard (LicenseGenerationForm) that captures:

• Who is licensed (licensee details)
• Where they may publish (authorized platforms)
• When and how they may use the content (dates and usage rights)
• How they pay you (fees and revenue share)
• What kind of license applies (license type)
• A generated PDF summary and a stored license record

Planned license types

The license wizard is planned to support several license types so you can match terms to your business model:

• non_exclusive — You may license the same content to multiple licensees at the same time.
• exclusive — You grant one licensee exclusive rights under the agreed scope, usually for a defined period or territory.
• commercial — The licensee may use the content in monetized or promotional contexts, subject to the agreed fee and/or revenue share.
• editorial — The licensee may use the content in non-commercial, editorial, or journalistic contexts, typically with stricter usage constraints.

You will choose one of these license types when configuring the license so the generated document reflects the correct framing.

Planned authorized platforms

Authorized platforms define where the licensee may distribute or publish the content. The planned options mirror common creator platforms plus a flexible custom option:

• OnlyFans
• Fansly
• ManyVids
• Clips4Sale
• AVN Stars
• Custom Platform — When selected, the wizard will prompt for a custom platform URL so you can capture destinations outside the predefined list.

Use these as a reference when drafting your own contracts so your platform list stays aligned with what Licensing will support.

Planned usage rights

Usage rights describe what the licensee is allowed to do with the content. The planned wizard uses named switches for each right:

• distribution — Distribution Rights: right to distribute content on authorized platforms.
• modification — Modification Rights: right to edit or modify the content.
• sublicensing — Sublicensing: right to sublicense to third parties.
• commercial_use — Commercial Use: right to use for commercial purposes.
• derivative_works — Derivative Works: right to create derivative works.

Expect these to appear as individual toggles so the license PDF and record can show which rights you granted.

Planned license generation flow

The LicenseGenerationForm is designed as a four-step wizard. This section outlines the expected flow so you can anticipate the data you will need when the feature becomes available.

Planned fields and options

The following fields are implemented in the LicenseGenerationForm component but not yet exposed in the Licensing tab UI. Use them as a checklist when preparing your own contracts today.

1. Licensee information

2. Authorized platforms

3. Dates and usage rights

4. Commercial terms and summary

How to prepare now using existing tabs

Until Licensing is active, use a combination of Compliance and File Sharing to support your licensing workflows and keep your project distribution-ready.

1. Capture all compliance artifacts

Use the Compliance tab on /collab/{id} to store legal documentation that underpins any license you grant:

• Identity documents and model releases for performers
• Age verification records for all required parties
• Location-specific disclosures and consents where relevant

This gives you a compliance anchor for any external licensee who receives content from the project.

2. Organize deliverables in File Sharing

Use the File Sharing tab to keep all licensed assets clearly organized:

• Group files by shoot, set, or deliverable batch
• Use folder naming that aligns with how you describe content in your contracts
• Keep master exports and derivative files together for easier auditing

You can then reference these folders and file names in your external license agreements so both parties know exactly which assets are covered.

3. Mirror the planned Licensing fields in your contracts

Even before the Licensing tab becomes interactive, you can mirror the planned structure in your own templates:

• Add clear licensee details sections (name and contact email)
• Spell out platforms, including any custom destinations with URLs
• Define start date and duration in months, plus renewal conditions
• List usage rights aligned with distribution, modification, sublicensing, commercial use, and derivative works
• Separate license fees in currency from revenue sharing percentages
• Specify the license type (for example, non_exclusive or commercial)

Aligning your templates with this structure will make it easier to migrate into the built-in Licensing experience when it launches.

FAQs about Licensing in Collabs

Where to go next

Use these related pages to complete the rest of your Collab distribution setup.