Assets and visibility
Everything you upload or generate becomes an asset — private to you until you decide otherwise.
An asset is any piece of media the workspace holds: a file you uploaded, an image or video Endless generated, an audio file, a document, a piece of text, a transcript. They all land in one place — Assets, described in the product as "Everything you've made and uploaded, in one place." — where you can filter them by project, type, who made them, date, source and model.
The rule that governs all of them is short:
Assets are private by default. A file you upload or a thing you generate is visible to you and nobody else, until you share it or put it somewhere shared.
Who can see an asset
Someone in your workspace can open an asset if any one of these is true. They are alternatives, not steps — one is enough.
They made it
The person who uploaded or generated it always sees it.
It's shared
You set it to "Shared with workspace" — "Everyone in the workspace can view". That is the only sharing tier there is: an asset is either private or open to the whole workspace, never open to the internet.
It's in a chat they can open
An asset attached to or generated in a chat is visible to anyone who can read that chat.
It's on a canvas they can open
Same for a canvas: if they can open the canvas, they can see what's on it.
It's linked to a project they can open
An asset linked to a project is visible to that project's members in their own Assets library — and it is listed on the project's own Assets tab for anyone who can open that project.
Those are the rules that grant access, and none of them is a role. Access follows what you made, what you shared, and what you were let into — not how senior you are.
Being an admin is not a way in. Running the workspace does not come with the right to read a member's private assets: no role grants it, and there is no setting that turns it on. Someone's Assets library shows an admin exactly what it shows anyone else. If you need to see a person's work, ask them to share it.
The consequence people miss
Sharing a container shares what's in it. Share a chat with your workspace and every private asset attached to it becomes readable by the workspace, without those assets changing at all. Same for a canvas. That's usually what you want — it's what makes collaboration work — but it's worth a thought before sharing a long chat you generated a lot in.
Linking an asset into a project is a form of sharing, so mind the project's reach. A project set to Workspace reach can be opened by everyone, and its Assets tab lists what has been linked in to whoever opens it. Project membership is the narrower thing: it's what makes those assets turn up in someone's own Assets library. See Projects.
Only the creator can change an asset
Access and control are separate. Someone who can see your asset still cannot rename it, edit it, change who it's shared with, or delete it — that stays with whoever created it, whatever role anyone else holds.
Sharing makes something readable, never editable.
Sharing and un-sharing
Open the asset and use its share control
The pill reads "Private" or "Shared". Private is explained as "Only you, plus anyone on a chat, canvas, or project it's in"; shared as "Everyone in the workspace can view".
Check why it's visible
Under "General access" the panel lists who currently has access and why — "Everyone in the workspace", "Project members", "Linked from chat", "On this canvas". If an asset is reachable for a reason you didn't intend, this is where you'll see it.
Un-share to take it back
Switching an asset back to Private removes workspace-wide access straight away. Access is worked out live every time someone looks, never copied or frozen — so it can always be undone, and a container link that goes away takes its access with it.
Trash: 30 days, then gone
Deleting an asset doesn't destroy it immediately. It goes to Settings → Trash, described there as "Items in the trash are automatically deleted after 30 days. Restore them before then to keep them."
30 days to change your mind
The empty state says it plainly: "Deleted items show up here for 30 days before they're removed for good." Restore anything within that window and it comes back untouched.
Then it's permanent
After 30 days the item and its underlying file are deleted for good. You can also delete something permanently yourself from the trash, which skips the wait — that can't be undone.
Trashed items stay yours while they're in the trash. The same visibility rules apply — a teammate can't go rummaging through your deleted work.