No. Every Expression files itself by context. Where it goes is the workspace it was briefed from.
Every Expression files itself by context and names itself properly, and shares as a read-only, on-brand link you can revoke.
Learn next: Workspaces · Expressions · Governance
What happens to a piece of work once it exists: where it goes, what it is called, and how it reaches someone outside the product. The place it goes is a workspace; this is the machinery that puts it there and gets it out again.
Filing is the work nobody does and everybody needs. The outdated copy on somebody's drive should stop mattering, and a governed link should replace the attachment nobody can find six months later.
Filing. When an Expression is made it lands in the workspace it was briefed from: its project first, then its campaign, then its customer. You are told where it will land before you save, and where it went afterwards, so filing is never something you discover later. Anything with no workspace sits in Unfiled, which is a place, and not nowhere.
Naming. A file is named the way a careful person would name it every single time: the client, the context, the phase, the type, the title and the version, in that order. It still says what it is on somebody's desktop a year later, which is where most naming conventions go to die.
Sharing. A public share is a read-only, branded copy at an unguessable address, revocable at any time and with a lifetime you set, from a day to a year. Revoking takes effect at once: the files are served so that no cache keeps handing out a link you have withdrawn. One view lists every file with a live link, so you can see what is out there and pull any of it back. Publishing a page, a document or a deck waits for the sign-off; taking one down never does.
No. Every Expression files itself by context. Where it goes is the workspace it was briefed from.
They are read-only, branded and revocable at any time, with a lifetime you set when the link is made, from a day to a year. They are unguessable, and they are not password-protected: anyone with the address can read it until you revoke it.
Yes. Connect it to a second workspace. Nothing is copied; there is still one of it.
Per-workspace access control is roadmap. A share link cannot be given a password or tied to a named reader; revoking is the control. Refreshing a shared file when the knowledge beneath it changes is roadmap. Republishing is how a change reaches a link today.
Bring the team and partners along
Documents, research, presentations, your website. The material you already work from.
Who they are, what they do, and the expertise the work can draw on.
Where the work lives, so it files itself.
Foundation, collection, customer, project or campaign, and how to tell which.
A PDF of a deck or a document, a Word file of a document, and the images of a social post.
Everyone gets the part of the business that is theirs, and no more.
Send it to the person it is actually about.
A record you can read, and reverse.
A workspace is one initiative: a project, a customer or a campaign, with everything made for it gathering there on its own.
The work you actually ship. An Expression is a rendered view of your intelligence, in your brand.
One source of truth. Sourced, isolated, approved, versioned, exportable, and owned by the customer.
The pilot takes a small number of organizations at a time. Bring what you already have.