Files and chat outputs

Files keeps documents and Era outputs together. Teams use it to find files, link them to records and download within their access. A chat card or computer path alone is not a cloud-saved file.

File guide

Folders, attachments, upload links and retention.

Save from terminal

Upload a local file and inspect its identity.

Where to find it

Web: Files, /files; desktop: Business → Files. Upload links are under /files/links, storage under /files/storage. Chat file cards provide preview/open controls.

Add the file

Upload in Files or attach context through + in the chat composer. Explain how the file should be used.

Save the output

Ask “Save the result to Era Files.” In a local-engine terminal, the following command saves the file; finish the returned one-time upload step for large files.

era file save "./demo-report.csv"

Use its identity

Inspect the saved ID and outcome. file_get/era file get returns a temporary download URL or command. Execute the returned command to actually download bytes.

With suitable access, create folders, preview files, attach to records or detach them. Controlled upload links collect files; inspect expiry, allowed types and target in the full guide. Published files are public; that differs from a temporary private download.

Local copies do not exist on every device

Old local-cache links can resolve only to copies saved to Era. Name lookup can choose the newest same-name file; use file IDs for important sharing.

Access and limits

files.read governs reads, files.write uploads/changes, files.delete permitted removal and files.manage management. Linked-record access also applies. There is no standalone Files module Settings page; storage and links have their own screens.

Ask Era

Export my selected records to CSV and save it to Era Files.
Distinguish a first page from the whole dataset; show the file ID.

Continue with file issues, chat attachments and CLI file commands.