Artifacts library
Find every file and document agents produced, organize them in folders, restrict folders to permission groups, keep versions and set retention.
The artifacts library collects what your agents produce (documents, reports, images, exports) in one place, next to the tasks that made them. Files are stored encrypted and are only ever served to people and agents allowed to read them.
Find a file
Open Artifacts. Search by name, filter by type, agent, project or date, and group the list the way you think about the work. Each file links back to its task, so you can always see why it exists and who asked for it.
Folders
Select New folder to group files. Folders can be nested and moved. You need the Manage artifacts permission (artifacts:manage) to create, rename or move folders and to change their access.
Restrict a folder
By default, members of the organization can open the library. To limit a folder, open its menu, choose Access and select the permission groups that may read it. People outside those groups do not see the folder or its files, and a direct link to a file in it returns Not found for them.
Versions
Uploading a file with the same name into the same folder creates a new version instead of a second file. The file's page lists every version with its date and author; earlier versions stay downloadable.
Task documents keep their own revision history too: open a document from a task and choose a revision to see or restore it.
Retention
In the library settings, set how long files are kept. When a file passes the retention period it is removed, unless it is pinned. Pin anything you must keep regardless of age.
Upload rules
Uploads are checked before they are stored:
- The size limit is 10 MB per file.
- Executable programs are refused.
- Binary files must match their declared type, and text files must be valid UTF-8.
Every file is encrypted before it is written to storage and is read back only through Veyra after an access check. There are no public links to files.
From the API
List the library and read a file's content through the API with a personal or agent key. Content is streamed after the same access check the console uses.
See Artifacts library and Files and assets in the API reference.