Letting Asteria file its own work
Deliverables saved back into a collection, revised in place, and kept as one copy rather than three.
Collections are not only somewhere to put things. Asteria can put things in them too.
Saving a result into a collection
Ask, and the deliverable is filed rather than left in the conversation:
Save that summary into the Board Packs collection.
Work out the regional totals and put the resulting spreadsheet in FY24 Planning.
The document appears in the collection like any other, and from then on it is available in every conversation, to you and to anyone the collection is shared with.
This matters more than it sounds. The alternative is the thing everyone does today: download the file, rename it, upload it somewhere, and lose track of which of the four copies is current.
Revising something already in a collection
Asteria can open a document it wrote into a collection, change it, and save it back onto the same document as a new version.
Open the Q3 summary in Board Packs and add the October figures.
The point is that you end up with one document that has been revised, not a second document called Q3 summary (final v2). Anyone who had the first one now has the current one.
What it will not do
Asteria can only remove documents it added itself. It will not delete something you uploaded.
That restriction is deliberate. Revising a document keeps the old content in its history, so a mistake is recoverable. Deleting destroys the only copy the collection has, and for a file you uploaded, possibly the only copy anywhere. If you want something gone, delete it yourself.
Where the file actually lands
If the collection is an ordinary one, the document is saved into it directly.
If the collection is a connected folder, the deliverable is written into the Drive or SharePoint folder instead, and arrives back in the collection on the next sync. That is usually what you want: the file ends up where your colleagues already look for it, under that folder's sharing and retention rules, rather than somewhere only Asteria Cloud knows about.
If that write cannot be completed, Asteria falls back to saving into the collection normally rather than losing your work.
A caution about ownership
A document written into a connected Drive or SharePoint folder is created using your connected account, so it belongs to you in that system. If you leave the organisation, it goes with your account unless the folder is on a shared drive.
If that matters for the work in question, use a shared drive folder rather than one in your personal space, and ask your administrator if you are unsure which you are pointing at.