Licensing enterprise documentation and code
Internal manuals, ticket histories and repositories are attractive because they show real work being done. They are also where ownership is most tangled.
Step 1 — Rights inventory by asset class
- Product documentation
Typical ownership questionWritten by staff or contractors?
Blocking issueContractor IP assignment missing
- Support tickets
Typical ownership questionCustomer content embedded
Blocking issueCustomer contract confidentiality; personal data
- Source code
Typical ownership questionFirst-party vs. vendored
Blocking issueOpen-source licences with copyleft or attribution terms
- Internal wikis
Typical ownership questionMixed authorship
Blocking issueThird-party material pasted in
Step 2 — Personal data review
Tickets and emails can contain personal data. Where GDPR applies, assess the lawful basis and any purpose-compatibility requirements for the proposed processing; special-category data can require additional conditions. Assess applicable California privacy obligations separately. Document de-identification and its limits rather than assuming it removes all obligations.
Step 3 — Code-specific checks
- Run a licence scanner and keep its report as a delivery artefact.
- Separate first-party code from vendored or generated dependencies.
- Strip secrets, keys and internal hostnames before any sample is shared.
Have a dataset worth discussing?
Tell us what you own, which rights you can license and the commercial scope you have in mind.