Where your files end up
The Workshop, your computer, a collection, or straight into Drive or SharePoint.
A finished document can go to four places. Knowing which is which saves the "where did I put it" problem later.
In the Workshop
The default. It stays attached to its conversation and you reopen it from the card in the chat.
Good for work in progress. Bad as a filing system: it is only findable through the conversation that made it, and it dies with that conversation.
On your computer
Download in the panel header. Formats depend on the document type: Word, PDF or Markdown for documents, PowerPoint for decks, Excel for workbooks, PNG, SVG or .excalidraw for diagrams.
Once downloaded, the two copies are independent. Later changes in the Workshop do not reach your download, and your edits do not come back.
In a collection
Ask Asteria to file it:
Save that into the Board Packs collection.
Now it is available from every conversation, searchable, and shareable with colleagues. This is the right home for anything you will want again. See Letting Asteria file its own work.
In Google Drive or SharePoint
If the collection you name is one that mirrors a Drive or SharePoint folder, the file is written into that folder rather than into Asteria Cloud, and it appears in the collection at the next sync.
This is usually the best outcome available. The deliverable lands where your colleagues already look, under that folder's sharing rules, retention and audit, rather than in a product they may not use.
Two things to know:
It needs your account linked. Under Profile then Connections. If it is not, Asteria stops and says so rather than quietly putting the file somewhere else.
The file belongs to you in that system, because it was created with your account. If you leave the organisation it goes with you, unless the folder is on a shared drive. For anything the team depends on, point at a shared drive folder.
Native Google Docs, Sheets and Slides
Where your organisation has enabled the Google connector and you have linked your account, deliverables increasingly land as native Google files rather than as attachments in a folder.
What that means per kind, today:
| Kind | Where it goes |
|---|---|
| Document | A Google Doc, when Google is enabled |
| Workbook | Authored as a spreadsheet in the Workshop. Keep it and it becomes a live Google Sheet, formulas intact |
| Deck | Built directly in Google Slides, on your organisation's own brand deck, when an administrator has pointed at one |
The workbook row is the one to read twice: building and keeping are different steps. You get a spreadsheet in the Workshop to look at, and it becomes a Sheet when you ask for it to be kept.
None of this needs anything from you beyond linking your account under Profile then Connections. Whether the Google connector is enabled at all, and whether decks have a brand template to build on, are decisions your administrator makes.
If a connector write fails for a reason a person has to fix, Asteria stops and tells you rather than quietly falling back, so you never end up with a file in the wrong place believing it went to the right one.