TrialStack logo
Browse docs
On this page

Connections

Media

How files and media assets support records across TrialStack and how those assets are connected back to governed entities.

Media

Media records let teams attach supporting assets to documents, evidence packs, personas, contacts, interventions, and other connected records.

Who this is for

This page is for teams that manage supporting files and need those assets to stay connected to the records they support.

What teams need to understand

  • media is shared supporting context, not just raw upload storage
  • a media item can have multiple entity connections
  • signed download behavior exists to support controlled access patterns
  • media should be understood in relation to the record it supports

Operational expectations

  • A media item should stay connected to the records it supports.
  • Teams should be able to review where a media item is linked before relying on it in evidence or operational work.
  • Media access should follow controlled download patterns where signed access is required.
  • Teams should treat media as supporting context, not as a substitute for the governed record it belongs to.

What data users actually maintain on the media form

Media pages are simpler than trial or contact pages, but they still use the same structured entity model.

Users should expect media data to include:

  • information fields such as display name, original filename, media type, category, detected MIME type, file size, description, and tags
  • analysis-result context where the product surfaces extraction or analysis status for the uploaded asset

Several of these fields are intentionally read-only because they describe what the system detected about the uploaded file rather than what the user is free to rewrite.

Typical workflow

  1. Add the media item.
  2. Link it to the relevant record or records.
  3. Review where it is connected.
  4. Use those connections to support evidence, review, or operational context.

What matters most

  • attaching media to an entity
  • reviewing where a media item is connected
  • understanding how media supports evidence and review workflows

Common mistakes to avoid

  • uploading media without linking it back to the governed record it supports
  • assuming a media item belongs to only one entity when it may support several
  • treating raw files as self-explanatory without the surrounding record context
  • bypassing controlled download expectations for sensitive assets

Acceptance checks

  • A user can create a media record and attach it to one or more supported entities.
  • A user can review the set of entity connections for a media item.
  • A user can use media as supporting context in evidence and review workflows.
  • A user can retrieve media through the controlled access pattern used by the product.

API reference

Use TrialStack API reference for exact media upload, linking, retrieval, signed access, and relationship contract details.