Manage asset documents
Review, preview, verify, download, and manage the files attached to a live asset from the Documents tab in the Console.
Every regulated asset carries supporting files: a prospectus, a term sheet, a reserve audit, an assay certificate, a compliance report. The Documents tab is where you keep those files on the asset and decide who can open them. From the tab you review what is attached, preview a file without leaving the Console, confirm a file still matches its recorded fingerprint, and, when you hold the right role, upload or remove documents.
Integrations that upload and manage documents from code use the token document API, which exposes the same operations.
Prerequisites
- A deployed asset and access to its asset detail workspace.
- For reviewing and downloading documents: the right to open the asset, plus access to the visibility tier of the files you need. See who can see each document.
- For uploading or deleting documents: the token governance role on the asset. Without it, the tab is read-only and shows no upload or delete control.
- Wallet verification for the connected wallet when the active authentication flow requires it.
Open the Documents tab
Open the asset detail workspace for the asset, then select the Documents tab. The tab shows the latest version of each document attached to the asset as a gallery of preview tiles.
Each tile shows a preview of the file, its title or file name, its file type, its version number, its visibility tier, and its upload date. PDFs show a first-page preview and images show their own preview. A Word document, an Excel spreadsheet, a CSV file, or any file without a preview shows a file-type icon instead. Hover or focus a tile to reach its menu, where you can download the file or, when you hold the right role, delete it.
The gallery is paginated, so a long set of documents spans several pages. Use the toolbar to export the current view or, when you hold the right role, to upload a new document. Move between pages to reach older documents.
Preview a document
Select a tile to open the file in a viewer that slides in from the right, without leaving the tab. The viewer opens these formats directly:
- Word documents (DOCX)
- Excel spreadsheets (XLSX)
- CSV files
- Images (JPEG, PNG, WebP)
Each format loads only when you open a file of that type, so the tab stays fast even for large documents. A file type with no in-place viewer opens as a download instead.
Use the Previous and Next controls in the viewer to move through the documents on the current page without closing and reopening the viewer. The controls stop at the first and last document on the page; to reach documents on another page, close the viewer and change pages in the gallery.
Confirm file integrity
When a document was stored with a content fingerprint, the preview runs an integrity check while it opens. The Console reads the file back and computes its fingerprint. It then compares that value against the fingerprint recorded when the file was confirmed.
The preview shows the result:
- Verifying while the check runs.
- Verified when the recomputed fingerprint matches the recorded value, so the file you are viewing is the exact file that was stored.
- Failed when the values do not match or the check could not finish. Treat a failed result as a signal to re-confirm the file with the team that uploaded it before relying on it.
A hash-verification badge in the viewer header shows the same result at a glance: green when the file hash matches the recorded fingerprint, a spinner while the check runs, and red when verification fails. Wait for the green verified state before you download, so the local copy you save is the exact file that was stored.
Use the Download control in the viewer, or Download on a tile, to save a local copy after the hash-verification badge shows verified.
Who can see each document
Every document carries a visibility tier that controls who can open it. The tier appears in the Documents tab and on each tile:
| Visibility tier | Who can open the file |
|---|---|
| Public | Anyone who can reach the asset's document surface. |
| Holders | A caller with an operational role on the asset, or an investor who holds the token, confirmed from a non-zero balance. |
| Restricted | Only a caller with the governance or admin role on the asset. |
An investor who holds the token sees public and holders documents on the asset's Documents tab, read-only. Holding the token means the connected wallet has a confirmed, non-zero balance of the asset. A balance-only holder reads holder-tier documents but gains no rights to upload, change, or remove them.
The balance check applies only to the balance-based path: a caller who already holds an asset role keeps holder-tier access regardless of balance. If the balance lookup cannot complete, that path closes rather than opening, so a transient lookup problem never widens access by mistake.
Choose the narrowest tier that fits the file's operating and regulatory basis. When in doubt, restrict access and widen it later.
Upload a document
The upload control appears only when you hold the token governance role on the asset.
- On the Documents tab, choose Upload.
- Select the file, then set its document type and visibility tier. The Console limits the document types to those that fit the asset's profile: a stablecoin shows reserve and attestation types; a precious metal shows assay, storage, custody-chain, and insurance types.
- Confirm the upload. The Console sends the file to document storage and records it against the asset. It also records the file's content fingerprint, so later previews can verify integrity.
The new document appears in the gallery as the latest version once the upload completes. For the supported file size and types and the field-by-field upload contract, see the token document API.
Delete a document
The delete control appears only when you hold the token governance role on the asset.
- Find the document in the gallery, then hover or focus its tile to reveal its menu.
- Open the menu, choose Delete, then confirm.
Deleting removes the file from the asset's document surface. Keep your own deletion reasoning and approval records in your institution's review and audit process; removing the file clears it from the Console and API surface but does not replace your regulated record-keeping.