Check Reuse Permission Before Importing a Third-Party Asset
Use a content reuse permission checklist to record an asset’s origin, applicable terms, intended use and attribution before it reaches the publishing queue.
TL;DR
- Decide not to import a third‑party asset until a content reuse permission checklist shows the original source, specific terms, and an editorial record; route unclear legal questions to the organization’s adviser.
- Use a precise, recorded review method: document original source, governing terms, planned modifications, distribution destinations, and required attribution before importing the asset.
- Treat the checklist outcome as actionable: verify the delivered package in public posts, retain permission evidence under records policy, and recheck terms for any future reuse or modification.
Keep permission evidence with the asset
A content reuse permission checklist should help the editorial team determine whether an external image or other asset is ready for the intended use. Finding a file online or being able to download it does not answer that question.
Begin with the asset's original source and the specific terms or permission record associated with it. Keep those references together so a later publisher does not have to reconstruct the decision.
This is an operational checklist for preparing a review. When the terms are unclear or the proposed use raises a legal question, route the issue to the organization's qualified adviser rather than treating an editorial checkbox as a legal determination.
Describe the proposed use precisely
Record where the asset will appear, whether it will be modified and how it will be distributed. A website illustration, a paid promotion and a downloadable template may require different consideration under the applicable terms.
| Record | Question to answer |
|---|---|
| Original source | Where did this exact asset come from? |
| Terms or permission | What record governs the proposed use? |
| Modifications | Will it be cropped, translated or otherwise changed? |
| Distribution | Which destinations and formats are planned? |
| Attribution | What credit and links must accompany it? |
| Review owner | Who can resolve uncertainty? |
Avoid assuming that a licence attached to one page covers every image visible on that page. Identify the record relevant to the specific asset.
Read the actual conditions
Creative Commons explains that its licences use different combinations of conditions, including attribution, ShareAlike, NonCommercial and NoDerivatives. Its licence overview is a starting point for identifying those differences; the applicable licence and circumstances still need to be checked.
Do not reduce every licence to “free with credit.” A proposed modification or commercial context can matter. If the use does not clearly fit the available permission, seek clarification or choose a different asset.
Record the licence version or permission date where relevant. A generic note saying “licensed image” does not give the publisher enough evidence to inspect the decision.
Prepare attribution before import
Write the required credit and links as part of the asset package. Check where the CMS can display them and whether the chosen placement remains available on each destination.
Keep attribution distinct from an endorsement claim. The credit should identify the source according to the applicable requirements, not imply that the creator recommends your product.
Our content approval workflow can include confirmation that the accepted asset package contains the necessary attribution and review record.
Review changes and reuse separately
An asset accepted for one article may be proposed later for a different use. Recheck the relevant terms instead of assuming the earlier decision covers every future destination or modification.
If a designer changes the asset after review, identify whether the change affects the accepted use or attribution. Keep the revised output linked to its source and permission record.
When uncertainty cannot be resolved in time, use an original illustration or another asset whose proposed use can be verified. Do not allow a publication deadline to convert an unresolved question into an assumed permission.
Verify the delivered package
Inspect the public article to confirm that the intended asset and credit appear together. Check any additional distribution format included in the review.
Retain the permission evidence under the team's records policy so future maintainers can understand the basis of the decision. If the asset is replaced, record the new source rather than leaving the old attribution attached.
A useful checklist makes the origin, proposed use and review outcome traceable. It helps the editorial team prepare an informed decision and prevents important conditions from being lost during import.
Related reading: A Content Distribution Strategy That Starts With One Useful Article.