A scenario, told by a marketing lead in a twelve person team. The steps are the app’s own, as the BearingBridge help center describes them on October 27, 2026.
The job, and why it hurt
A distributor asked for the packshot from our spring launch. I knew it existed. I didn’t know where. Maybe a designer’s laptop, maybe a shared drive folder called “final_v2”, maybe a chat thread from April or the image tool we made it in.
So I asked around, which meant pulling two colleagues off their own work to hunt for one picture.
I wanted every file to land in one place on its own, and one search box that reads all of it.
What I did in BearingBridge
Let the library fill itself
The Assets Library sits in the Studio pillar of the left menu. Uploads land there. So does everything the app makes: every article, copy piece, social post, image and video made in Brand Content or Social is saved the moment it’s made, with the engine, the prompt or its first lines, and what the run cost.
Make a piece again and its library copy is replaced. Rewrite a post ten times and you still have one asset, the latest.
One tree for the whole team
I clicked New folder and set up a short tree: a folder per campaign, plus one for brand basics. Folders belong to the whole organization, so everyone sees the same tree. The only things kept out of sight are a colleague’s unshared No brand drafts.
Filing is a drag. Drop a row onto a folder, or tick several rows and drag them together.
Tags in our own words
A folder holds a file in one place. Tags let the same file turn up under several words. In an asset’s Actions menu I pick Tags, type a word, press Enter and click Save. For a whole batch, I tick the rows and use Add tag in the bar that appears.
Everyone who sees the asset sees its tags. The most used ones are listed under In use, which is how the team ended up reusing “packshot” instead of inventing “product shot”. An asset takes up to 20 tags, and “#Launch” and “launch” count as the same one.
Search the whole library, not the open folder
Press / anywhere on the page and the cursor jumps to the search field. It reads names, prompts, the opening lines of texts written in the app, engines, brands, tags and who added the asset. Type several words and an asset has to match all of them.
The search covers the whole library no matter which folder is open. Each result shows where it’s filed, and clicking that path opens the folder.
Six filters narrow the list:
| Filter | What it narrows |
|---|---|
| Type | Images, videos, texts, documents, other; made in the app or uploaded |
| Date | Today, the last 7, 30 or 90 days, this year, or between two days |
| Tags | Any of the ticked tags, or all of them |
| Brand | The whole organization or one brand |
| Campaign | One campaign, or assets in none |
| Added by | One person |
Before you pick a choice, it shows how many assets it would find.
The result
The next time a request came in, I pressed /, typed “packshot spring” and ticked Images. The file came up with its folder path and the name of whoever added it. I didn’t have to message anyone.
There’s one limit to plan around. The search doesn’t read inside uploaded documents, so a PDF or a deck turns up only by its name and its tags. We now name and tag those the day they arrive.
The video below walks through the same routine in the app.







