Who owns your nonprofit's records, documents, and content?

A nonprofit can possess a record without owning every right needed to license it. Before making an offer to share documents, identify who created the material, what agreements govern it, and what separate privacy or confidentiality obligations apply. Access to a shared drive is not evidence of all those permissions.

The review is often easier when it begins with a specific collection: a set of manuals, research reports, or organization-written materials. Trying to declare ownership of “all our data” combines many different questions into one answer. This guide provides an inventory method for U.S. nonprofits considering a licensing discussion.

Distinguish a file from the rights connected to it

The U.S. Copyright Office's Copyright Basics distinguishes ownership of a copy from ownership of copyright. It also explains that copyright owners can authorize others to exercise certain rights, subject to legal limitations.

For a nonprofit, the practical task is to identify the rights relevant to the proposed use. A document may combine original text, a licensed photograph, a donor quotation, and confidential details. The fact that the organization can use the finished document internally does not necessarily answer whether another organization can use all its elements commercially.

Keep four questions on separate lines in your review:

• Who created the relevant material, and who holds the rights now?
• What uses has the nonprofit been authorized to make?
• What privacy, confidentiality, grant, or contractual conditions also apply?
• Who within the nonprofit can approve the proposed transaction?

If one answer is unknown, record the gap. Do not turn an assumption into a warranty simply because a proposed agreement asks the nonprofit to make one.

Start with how each collection was created

Employee work and commissioned work need different factual review. The Copyright Office's Works Made for Hire circular explains the employee scope-of-employment rule and the narrower conditions for specially commissioned work. Paying a contractor does not automatically establish work-made-for-hire ownership.

Use this original collection worksheet before asking counsel to review a proposed license:

The worksheet identifies evidence; it does not resolve ownership by checking a box. For a larger project, keep a separate entry for components whose rights differ from the main document.

Keep the rights chain visible

Materials can arrive through mergers, program transfers, staff departures, or old partnerships. A current employee may know where the files are stored but not how the nonprofit obtained them. Locate the documents that connect the original creator to the organization's present claim.

Use three internal labels: documented, needs review, and exclude from this proposal. “Documented” should mean that evidence has been found and reviewed for the intended use, not merely that a contract exists somewhere. Record the document's location and the person responsible for the conclusion.

Avoid recreating history from memory when the agreement matters. If the evidence cannot be found, discuss a narrower collection. A smaller set with clearer rights can be easier to assess than a large mixed archive, although clearer rights do not guarantee buyer demand or an offer.

Look inside documents and attachments

A report assembled by your organization can include material supplied by others. Review embedded images, quotations, case studies, survey responses, appendices, and copied resources. If the proposed use includes attachments, review those as part of the scope rather than treating them as incidental.

Create an exceptions list for items needing separate permission. Give each item enough detail for staff to locate it without copying sensitive contents into the inventory. Assign a next step: verify an existing license, seek advice about permission, remove the component from the proposed set, or stop considering that collection.

For mailbox collections, this becomes especially important. A thread can include text from several senders and an attachment created by another organization. The guide to email and employee records explains how to scope that review.

Review grant and collaboration agreements

Funding a project does not tell you everything about rights in its outputs. Read the actual award, research, service, or collaboration terms. Ask whether the agreement addresses publication, commercial use, attribution, licensing, data sharing, approvals, or confidentiality.

Keep use of proceeds separate from use of the underlying material. An organization may have a question about whether it can license a report and another question about how it may use any resulting revenue. Answering one does not answer the other.

Where a federal award, research participant agreement, or government contract is involved, identify the specific arrangement for the adviser reviewing it. Do not rely on a generic statement that “grant-funded work belongs to us” or “anything publicly funded is public domain.”

Copyright ownership does not settle privacy

Even when ownership is clear, a document may contain information about people who expected confidentiality. The proposed use still needs the review described in nonprofit data licensing and privacy.

For example, an employee may have written a program report as part of their job. That fact does not establish that the organization can disclose the client's identifiable story in the report to an unrelated commercial recipient. Likewise, permission to publish a testimonial in an annual report should not automatically be treated as permission for every later use.

List rights and privacy conclusions separately in the review record. This prevents a statement such as “we own the document” from ending the discussion too early.

Confirm who can approve the agreement

Identify the relevant decision-maker under your organization's bylaws, policies, and delegated authority. The National Council of Nonprofits' board guidance connects oversight with prudent asset use, mission, and conflicts of interest. It does not establish that every licensing agreement requires the same approval route.

Make sure the approver sees the actual scope, unresolved exceptions, and promises the organization would make. Ask counsel to explain warranties or indemnities that seem broader than the evidence supports. The licensing agreement checklist can organize those questions.

A hypothetical decision with a useful boundary

Consider a fictional arts nonprofit with twenty years of workshop materials. Some were written by staff, others by visiting artists, and others contain licensed photographs. The organization begins by describing the collections rather than offering the entire archive.

Staff locate agreements for certain materials and flag others for review. They build a proposed subset with an accompanying exceptions list. No one assumes that age, possession, or past publication resolves the remaining rights questions.

The outcome might be a narrower proposal or a decision not to proceed. Either is more useful than promising rights the nonprofit has not established. For an initial Datifide conversation, a high-level description of the collection is enough to begin; the intake does not request the files themselves.