Skip to content
Rival Docs

Digital Assets

Digital Assets is Rival’s built-in cloud storage for tool-related files: reference data, datasets, topic files for Storm tools, images, PDFs, or any other content you want to keep alongside your tool ecosystem without embedding it in code.

You can work with assets in two places:

  • Per-tool assets - files attached to a specific tool from the Tool Editor. They live with the tool and are referenced from the handler by path.
  • Workspace library at /digital-assets - a shared store for assets used across multiple tools or kept available for direct download.

The Digital Assets library

Open Digital Assets from the sidebar (or go to /digital-assets) to manage assets for your whole workspace. The library is organized into categories:

  • Images
  • PDFs
  • Documents
  • Other

You can switch between grid and list view, search by name, and filter by category. Each asset has a name and an optional description.

Uploading

Click Upload and pick one or more files. Each file can be up to 500 MB. When you upload, you also set visibility:

  • Public - accessible to anyone with the URL. Use for shared reference files. Public assets cannot be changed back to private.
  • Private - accessible only inside your organization. Private assets can be flipped to public at any time.

Actions

For any asset, you can:

  • Copy URL - copies a direct link to the file for use in tool code or event payloads.
  • Search - find assets by name.
  • Download - pull the file down for review or sharing.
  • Delete - remove the asset permanently.

Per-tool assets

When an asset only matters for a single tool, attach it inside that tool’s editor instead of cluttering the workspace library. Per-tool assets live with the tool, follow the tool’s version snapshots, and are referenced from your handler code by path.

Using an asset in tool code

Once an asset exists (per-tool or in the library), copy its URL or reference path and use it from your handler.

In a typical flow:

  1. Upload the asset.
  2. Click Copy URL (library) or copy the reference path (per-tool) from the asset list.
  3. Paste the path into your handler code, or include it as a field in the event payload your tool reads at runtime.

Your tool reads the file at that path during execution. Private assets remain accessible to your tools regardless of who triggered the run - visibility controls external access, not internal tool access.

Storm tools and topic files

Storm is Rival’s content tagging engine. Storm tools operate on topic files - structured files that describe the categories and concepts the tool should identify.

A typical Storm workflow:

  1. Upload your topic file to Digital Assets as a private asset.
  2. Copy its reference path.
  3. Include the path in the event payload when running the Storm tool.

This keeps topic files versioned in one place and reusable across multiple Storm tools.

Managing assets

Workspace assets are shared at the organization level - every member can see and use what’s in /digital-assets, subject to their role permissions. Private assets are not visible outside the org but are accessible to everyone inside it.