A shared asset library people can use

Logos, photographs, copy and templates often end up spread across chats and folders. A small, well-organised library can remove much of the uncertainty around which version to use.

Organise by the job

Group assets around practical uses such as website headers, social posts and documents. Give files clear names and record where an approved version belongs. Keep source files and ready-to-use exports connected, so someone can request a different size without starting again.

Make approval visible

Separate current assets from archived concepts. Record useful constraints such as a logo’s proportions or an image’s permitted uses. Do not rely on memory or the date of the last chat message to communicate approval.

Keep ownership clear

Choose a person to maintain the library and decide how changes are reviewed. When an asset is replaced, update the places that depend on it and keep enough history to understand the change.

A shared library is useful when it supports ordinary work. The aim is a clear route to the right file, not a complicated filing system.