Files in the console¶

Files lists everything your organisation stores as a file, in one table: uploads, the artefacts a tool made during a turn, and the documents in your knowledge collections. Use it to find a file, download it, rename it, or decide whether it is kept, and to open a stored HTML file, share it or publish it as a page.

The section has two tabs: Files, with every stored file, and Pages, with the pages published over HTML files (Pages).

The section is in the Library group, below Datastores. The navigation shows it only when Upload and attach files is switched on for the organisation (organisation settings). Which kinds of file it shows follows the other switches: artefacts need Store artefacts the model produced, and knowledge documents need Index and search knowledge sources.

You need an administrator account of the organisation. Uploading and downloading with a key is in Files and artifacts through the API.

Upload a file¶

Upload files above the table stores one or more files as files of your organisation. Each chosen file gets a line saying whether it was added, and appears in the table at once. A file uploaded here belongs to no knowledge collection and is not indexed; a document you upload into a collection under Knowledge is a knowledge document instead. That difference matters for HTML: Open, Share and Publish are offered only for a file Core says can be opened as a page, which an HTML file uploaded here is and one in a collection is not. Uploads through the API and the files tools produce appear by themselves.

Find a file¶

Two filters and a switch sit above the table:

An API key's own collection is named after the key's id, here and in the Collection column.

Folders¶

A folder is a path on a file, such as policy/2026; it is not something you create on its own. Choose one collection in the Collection filter and, once that collection holds a folder, a tree appears beside the table with a count on every folder: the number of files in it and everything below it. Root is the top of the collection, for files in no folder. Select a folder to list its own files; switch on Include subfolders to list what is below it too. Folders belong to one collection, so with All collections there is no tree.

New folder, above the table, adds an empty folder to the tree on this page. It exists for real only once a file is in it: the next upload goes into the folder you selected, and a line next to Upload files says which. This is offered for your API keys' own collections and for the organisation's uploads collection; a knowledge collection has its own upload box under Knowledge.

The pen on a folder in the tree renames it or moves it under another folder: enter the whole new path, from the collection's root, in New path. Every file in the folder and below moves with it, in one step: all of them or none. A folder of more than 500 files is refused, and so is a folder moved into itself; the dialog shows Core's own sentence under the field. A file that may not change, such as a synced document, stops the move and the sentence names its id, so you know which file to look at.

The table has one row per file:

When nothing matches the filters, the table is replaced by No files.

Open a file¶

Select a row to open the file's drawer. Properties shows the file as it is stored: its Kind, Media type, Size, Collection (with Open collection as a link), Folder (Root when it is in none), whether it is Searchable, its Labels (one badge per value, which rules about Stored files read), Created by, Created and its SHA-256 digest. Compare the digest with the hash of your own copy to check that the two are the same file.

An artefact also has a Provenance card with the Tool that made it, the Response id of the turn and the Call id of the tool call.

A PNG, JPEG, GIF or WebP image has a Preview card. An HTML file opens on a screen of its own (Open an HTML file). Other files are not shown in the console; download them to look at them.

Open an HTML file¶

An HTML file is an upload or an artefact with the media type text/html, such as a report a model wrote. Such a file has Open in the table's Open column and at the bottom of its drawer. Any other file, a knowledge document in HTML included, has no such button: the console shows it only for a file Core says can be opened as a page.

The Open column and the Open, Publish and Share buttons exist only when your deployment is set up to show HTML files. If no HTML file has them, ask your operator.

Open takes you to a screen of its own, with the filename as its title and the content in a frame below it. While Core prepares the content it says Preparing the view…. Five buttons sit at the right of the bar:

Files in the breadcrumb takes you back to the table.

An HTML file is content a model wrote or somebody uploaded, and nobody has checked it. The console therefore shows it confined: scripts in the file itself work, so a chart moves, but the content cannot fetch anything from outside, cannot store anything, and cannot read anything of the console or of your sign-in. A file that expects a font or an image from a web address does not show it. What exactly the content can do is on What an opened file can do.

Opening an HTML file from the console is always allowed, also when the organisation's keys may not download artefacts. Core records each time it is shown in the organisation's audit trail.

When it says It could not be opened., reload. When it says Core answered an address this console is not set to show, so nothing was loaded., your deployment's settings do not match; report it to your operator.

Share an HTML file¶

A share link hands an HTML file to somebody without an account. Anyone who holds the address opens the file, with no sign-in, until the link expires or you revoke it. Hand the address only to people who may read the content, and treat it like a password.

A link on a file keeps showing that one file. When you expect new versions, publish the file as a page and share the page (Pages).

Sharing is off by default: it needs a rule in the organisation's policy that permits it. An administrator adds it under Settings, on the Access & policy tab:

1. In the This organisation's policy card, select Edit to open the document in its drawer.
2. Select Add rule. The rule drawer opens.
3. Choose Permit and, under About, Share stored HTML files and pages through a link.
4. Select Apply. The rule drawer closes and the rule is in the list.
5. Select Save document. The rule applies only once the document is saved.

When the organisation has no document yet, the card offers Write a document in place of Edit, and the drawer opens with the organisation default: every kind permitted whole, except Destinations and sharing through a link. Saving it gives the organisation a policy document of its own; every key is held to those rules as well as to its own. Read Policy before you save.

The Settings card of the document drawer, not of the rule drawer, holds Longest a share link lives (days).

While no rule permits sharing, Create link is refused, and the dialog then shows the notice Share links are off above the form and the list: This organisation’s policy does not allow share links. Add a rule that permits sharing by link in the organisation’s policy, on the Access & policy tab. Its link Open the organisation’s policy takes you to that tab. The notice is not there when the dialog opens: the list loads as usual, and you can still Revoke a link that was made earlier.

To make a link:

1. Choose Share, at the bottom of the file's drawer or in the bar of the screen the file is open on. The Share this file dialog opens.
2. Enter in Lives for (days) how many days the link should work. Leave the field empty for the longest the policy allows; a longer time is refused.
3. Choose Create link. The console confirms with Link created and the link is in the list below.
4. Choose Copy address on the link's row and paste the address where you want to send it. The dialog never shows the address itself.

The list shows every link of this file, oldest first, with Created and under it what became of the link:

Revoke a link with Revoke and confirm in Revoke link. Whoever holds the address can no longer open the file, at once, and the console confirms with Link revoked. A revoked link does not come back; make a new one to share again.

A link also closes without being revoked: when the file is deleted or the retention window removes it, when the organisation's policy stops permitting it, and for as long as the organisation is suspended. Set Retention to Keep until deleted on a file you share (Rename a file or keep it). The full list is on What closes a link.

Each time somebody opens the file through a share link, its size counts towards the organisation's usage and it is recorded in the audit trail.

Pages¶

A page is a stable name over the versions of a stored HTML file. A report that is refined is a new file each time, and an address on a file keeps showing the old one. Publish the new version on the page and every address of the page shows it, the share links you already sent included.

The Pages tab, beside Files at the top of the section, lists your organisation's pages:

While there are no pages yet it says No pages.

Publish a file¶

1. On the Files tab, open an HTML file and choose Publish, at the bottom of the drawer or in the bar of the screen the file is open on. The Publish as a page dialog opens.
2. Under Publish as, choose what you want:
   • A new page: enter a Name. It is lower-case letters, digits and hyphens, 1 to 64 characters, and unique in the organisation.
   • A new version of a page: choose the Page that gets this version. When the organisation has no page yet it says There is no page to add a version to yet.
3. Choose Publish. The console confirms with Published.

The page shows a new version at once. The versions of one page are all uploads or all artefacts; a file of the other kind is refused.

When the page has a share link that still works, a new version is also published to the outside. Whoever publishes therefore has to be allowed to share: for you in the console that means the organisation's policy permits sharing through a link (Share an HTML file). Otherwise publishing is refused. The same holds for Make current.

A published file is kept. Publishing sets the file's Retention to Keep until deleted, so the retention window does not remove a file a page shows. While the file is a version of a page you cannot set it back to Temporary and cannot delete it (Delete a file).

Versions, name and deleting¶

Select a row on the Pages tab to open the page's drawer.

The Versions card lists every version, oldest first: Version and its number, the file, and when it was published. The version the page shows now is marked Current. Choose Make current on another version to have the page show that one, an earlier one to roll back or a later one to roll forward. Every address of the page shows that version at once, and the console confirms with Version made current.

Give the page another name in the Name field; choose Save and the console confirms with Page saved. A name that is taken is refused. A new name does not change the page's addresses or share links.

Delete at the bottom of the drawer asks for confirmation in Delete page. The name, the versions and every share link of the page are then gone, and its addresses stop opening at once. The files themselves stay, and stay on Keep until deleted. Find them on the Files tab and delete them there when you do not need them.

Open and share a page¶

Open at the bottom of the page's drawer shows the current version on the same screen an HTML file opens on, with the page's name as its title and Pages in the breadcrumb. The bar holds Reload, Present, Share and Download; Download saves the file of the current version.

Share, in the drawer or in that bar, works as it does for a file (Share an HTML file): the same rule and the same list, in a dialog titled Share this page. The difference is what the address shows. A share link on a page always shows the version that is current at that moment, so the address keeps working when you publish a new version. A page's links are in the page's dialog, not in that of the file it shows.

Open and Share are absent when your deployment is not set up to show HTML files.

Download a file¶

Choose Download at the bottom of the drawer. The browser saves the file under its filename. Download never opens a file in the browser, whatever its type. Look at an HTML file with Open, which shows it confined (Open an HTML file).

Downloading an artefact from the console is always allowed, also when the organisation's keys may not download artefacts. Core records each download in the organisation's audit trail.

Move a file¶

Choose Move at the bottom of the drawer and enter the new Folder; empty is the collection's root. When the file is in one of your API keys' own collections or in uploads, a Collection field also lets you move it to another of those; a file in a knowledge collection moves between folders only. Move is absent for a document a connector synced: its folder is the origin's, and the console shows it read-only. The console confirms with File moved; when Core refuses, the sentence is under the field and nothing changes.

Rename a file or keep it¶

The Name and retention card holds the two things you can change here. A file's content and kind are fixed; its folder and collection change with Move (Move a file).

1. Change Filename. For a file or an artefact (Kind file or artifact) only the last part of a path is kept, so reports/q3.pdf becomes q3.pdf, and a name of which nothing is left is refused. A text, records or connector document keeps its title as you wrote it.
2. Choose a Retention: Temporary puts the file under the organisation's retention window, Keep until deleted keeps it until somebody deletes it.
3. Choose Save. The console confirms with File saved. When Core refuses the name, the card shows why and nothing changes.

Files uploaded through the API with a key, and the files tools produce, are Temporary by default. Set a file you still need to Keep until deleted before the retention window passes.

Delete a file¶

Choose Delete at the bottom of the drawer and confirm in Delete file. The file goes to the trash: it disappears from the console, from every search and from its links at once, and is removed for good 30 days later unless your operator set another number. Until then you can restore it from the trash.

A file that is a published version of a page cannot be deleted. The console then says This file is a published version of the page with the page's name, and Delete the page in the Pages tab first. (Versions, name and deleting).

Trash¶

Switch on Trash above the table to see the files you deleted instead of the files you have. Each row shows the file, its collection, when it was Deleted and Gone for good on, the date the file is removed with its content. Nothing here opens in a drawer: a file in the trash is out of every list, search and link.

A collection's own trash, for the documents in a knowledge collection, is a Trash switch on that collection's sources screen (Delete a collection or source). The same actions are on the API (Delete, restore or purge a file).