← Encyclopedia
Skill
Introduction
One design file may combine a purchased typeface, licensed photograph, open-license icon, and marketplace template, then be delivered as though every component were a single team-owned original. Rights documentation matters before a dispute arises. This article explains how an asset register separates internally created material from specifically permitted uses, and how review questions change when a poster becomes a website, application, or resold product.
Ethical or rights principle
A visual asset downloadable from the internet is not automatically licensed for reuse.
Font licenses may distinguish desktop, web, app, and broadcast use and should be read directly.
Buying a stock image grants a defined license and does not necessarily transfer underlying copyright.
Icons and templates may require attribution or restrict resale or embedding.
Documenting assets and licenses reduces risk during handoff and scaling.
An asset needs an identifiable description rather than a vague name such as “background photo.” Record source, used version, and governing document, linked to the project file. Replacing a photograph should not leave its entry attached to the previous version's license. A purchase receipt may also be insufficient if it does not establish usage limits; relevant terms should accompany acquisition evidence. The objective is not collecting paperwork, but enabling another person to determine what was used, on what basis, and in which delivered version.
Responsible practice
Step 1: Create an asset register with source, license, and date.
Step 2: Do not use a commercial font in an app before checking embedding rights.
Step 3: Separate licensed files from original assets created by the team.
Step 4: Review template terms before selling designs derived from them.
For a typeface, distinguish producing a static image from embedding it in a product that renders or operates it elsewhere. Permission for the latter should not be inferred from the designer's access to the former. Read the actual license categories and conditions and seek clarification where necessary. Raw font files should likewise not be sent to clients or suppliers without checking whether transfer is permitted. Depending on terms, another party may need its own license or a different delivery method. These are specific contractual questions, not one rule for all commercial or free fonts.
Legal and professional context
Copyright, trademarks, and industrial design are different legal tools that may apply to different elements.
Open licenses such as Creative Commons have varied conditions and do not all mean unrestricted free use.
Digital asset marketplaces impose their own contracts in addition to general law.
For stock photographs, resizing or recoloring differs from acquiring original copyright. Review presentation, audience, new purpose, and possible inclusion in redistributed products. “We bought the photograph” does not settle every later use. Crediting the photographer does not replace permission, and absence of a credit requirement does not remove other conditions. An asset may also raise issues concerning depicted material or visible marks, so review the particular use rather than generalizing approval from one earlier project to every subsequent advertisement.
Limits and risks
Crediting a source does not replace permission when permission is required.
Changing color or cropping does not erase rights in a protected image.
Actual legal rules depend on jurisdiction, contract, and specific use.
Templates and icons require distinguishing use within a design from redistribution of source files or sale of derivatives. A template may be an internal working aid while individual components retain separate conditions. Original drawings added by the team can be recorded as new contributions without erasing the template's origin. Delivery statements should not claim that everything was drawn from scratch when some elements were externally licensed. Accurate description helps clients understand what they can modify and what needs further review when use expands.
Open-license assets require reading the named conditions rather than relying on the word “open.” Attribution, modification, and redistribution requirements may differ, and the licensing statement must be connected to the actual asset. A page collecting unidentified files should not be assumed entitled to license them. An undocumented item should remain unresolved and, where necessary, be replaced with traceable material rather than receive a random link making the register appear complete without a genuine basis.
At project completion, review the assets in the final version rather than only the initial list. A last-minute image may be the sole item that bypassed checks. Match records to actual files and document medium, duration, or transfer limits according to the governing documents. Keep this review separate from visual quality: a licensed asset may be aesthetically unsuitable, and an attractive one may have unclear rights. The register is not a comprehensive legal judgment; it organizes decisions and identifies questions requiring qualified review where contracts or law are disputed.
Delivery can explain which files clients may circulate internally and which require separate review before transfer to another supplier, based on verified terms. A generic statement from a previous project should not be copied because the asset set may differ. Unclear restrictions should remain explicit questions rather than vague footnotes. Clients can then plan expansion before discovering that a core file lacks permission for the new medium after implementation is complete.
Conclusion
Asset management preserves each file's connection to source, terms, and actual use, preventing confusion between purchase and ownership, attribution and permission, or design delivery and unrestricted redistribution of every component.