Every team has a handful of files it can never find. The current brand guidelines. The price list that changed last month. The proposal template, the org’s logo pack, the link to the shared drive folder nobody can remember. Assets in Clarion are a single library for those things, so “where’s the latest version?” has one answer.
Files and links, side by side
An asset is either a file you upload or a link to something that lives elsewhere — a design file, a shared drive folder, a dashboard, a public page. Both sit in the same list with a title, an optional description, a category and tags, so people find them the same way regardless of where they live.
Upload by dragging a file in or picking one; anything up to 100 MB is fine. Images show a thumbnail, so a logo or a product shot is recognisable at a glance.
Stored privately
Uploaded files are never sitting at a public address. They’re kept in private storage, and every download goes through a link that Clarion generates on request and that expires within the hour. A link pasted into an email or a chat will stop working, so the file stays with the people who have access to Clarion.
Versions without the “final_v3” filenames
When a file changes, don’t upload a second copy — upload a new version of the same asset. Add a note to say what changed (“Updated Q3 pricing”, “New logo lockup”). The asset keeps its title, category and place in the list, and everyone gets the latest version by default.
Open version history to see every earlier version, who uploaded it, when, and the note that came with it — and download any of them. When someone asks what last quarter’s price list said, the answer is two clicks away.
Organised your way
Two ways to organise, used together:
- Categories are the main folders. Owners and admins define them for the company under Settings → Categories, so everyone sorts the same way.
- Tags are free-form labels added on each asset — a client name, a campaign, a product line.
The Assets page searches titles, descriptions and file names as you type, and filters by category, by type (files or links) and by team.
Company-wide or team-only
Every asset can belong to a team, or to nobody in particular. Company-wide assets appear in the main Assets library for everyone. Mark an asset private (team-only) and it’s kept out of the company library and shown only in that team’s Hub.
That makes the Hub the natural place for a team’s working files. It shows the team’s assets grouped by category, next to its feed of updates and its knowledgebase articles, and you can add an asset straight from there.
Where assets fit
Assets hold the things; the knowledgebase holds the how. A process article in the knowledgebase can tell people which template to use, and the template itself lives in assets, versioned. If you’re onboarding someone, the combination of the team Hub, its assets and its articles is most of what they need on day one — see onboarding a new team member.
For step-by-step instructions, see uploading and versioning assets.