Todos os artigos

Projects and where your files live

There is no save button anywhere in Sunra Creative, and nothing lives only in your browser. Every file you make appears in two places at once — the project that made it, and one wall of everything — and which you reach for depends on whether you remember the project or only the picture.

Your work saves itself

Everything is kept on your account, on Sunra's side: your projects, their chats, the pages you lay out and every file you generate or upload. That is why your work follows you to another browser or machine, why a render carries on when you close the tab, and why a finished generation is in its project the moment it lands — nothing to accept, export or file.

Nor is a file copied when you use it: dropping the same image on the Design page, the Timeline and a Flow node leaves one file with three references to it.

The project's Assets tab

Every project opens with an Assets tab, the one place its contents are all listed — files and pages together, newest first.

  • A page gets a card like anything else, tagged Open while a tab is on it. Closing a tab never removes the page; you reopen it from its card.
  • A file's card says Used in and a number when a page references it.
  • The top bar's Filter narrows the grid along four axes — Show (all, pages only, files only), Type, Models and Source. The controls beside it resize the tiles and Upload files of your own.
  • Drag a card onto a tab to carry the file into that surface; hovering a tab chip on the way brings it forward.

Select tiles by clicking them, by dragging a box across several, or with Cmd to add one and Shift for a range. A bar appears under the selection with Favourite, Download and Delete.

Assets: every file from every project

The Assets row in the left rail is the same idea one level up: your folders along the top, and under them every file in the workspace, whichever project it came from. Each tile is one file, labelled with the model that generated it, and names the project it belongs to — click through and that project opens.

A filter column down the right narrows the wall, and ticks combine rather than replace one another: Liked, Type (images, videos, audio, 3D, PDF), Source (generated or uploaded) and Models, listing only the ones you have used. Clear filters puts it back to everything.

The Projects row below it lists the projects themselves, with a search box for finding one by name.

Folders and your Library

Folders are yours, not a project's — a way to collect the good results out of a dozen projects into one place.

Save to Library on a file opens a list of folders to save it into, and makes a New folder if you need one. Folders hold other folders, a file can sit in several at once, and Move to… rearranges them. Taking a file out of a folder leaves it in its project; deleting a folder deletes everything inside it, subfolders included.

A folder also has Reference in chat, which drops the whole folder into the prompt box on Home as one chip, so the agent can work from that set of references.

Getting files out

A single file downloads from its card or its lightbox, and you can ask for a different file type on the way out. Select several, press Download, and a panel takes the file type and builds one archive. A Design page exports page by page or stacked into one tall image; the Timeline has its own Export dialog.

To hand over a whole project rather than files, use Share. It makes a link, and anyone who opens it can look at the project and press Remix this project to fork a copy into their own account — their copy, not yours, and your later edits do not reach it.

Deleting, and what it removes

Deleting a file from the Assets grid removes it from the project for good, and if a page still references it, Sunra names those pages first. Deleting a generation node on the Flow canvas is smaller: it clears the node, but does not cancel a job already accepted and does not refund anything. Deleting a project removes it and its chats, permanently.

Working in a team workspace

In a team workspace the projects and the files published into them belong to the team, so any member can open a project, see its Assets and keep working on it. Four boundaries matter:

  • Your chat with the agent stays yours. Files are shared; the conversation is per member, and an Admin cannot read another member's chats.
  • One person edits at a time. The project's edit lease covers all of its documents, so if another client holds it — including another of your own tabs — you are offered a takeover rather than put in read-only. Which tab you have open, and your zoom and selection, stay your own view.
  • Generating draws on the team's pool, not a personal wallet. A member's quota caps how much of that pool they can spend.
  • Your personal Library is separate. Bringing one of your own files in copies it and publishes it as a team asset; team assets cannot be filed back into your Library, and a team's folders are the workspace's own.

Team workspaces covers seats, roles and invitations.

Artigos relacionados