TrialStack logo
Browse docs
On this page

Foundations

Getting Started

How new customers should approach TrialStack documentation and product onboarding.

Getting Started

TrialStack works best when teams learn the product in workflow order instead of jumping directly into isolated records or API contracts.

Who this page is for

This page is for teams that are:

  • Setting up a new customer workspace.
  • Orienting a mixed team of operations, quality, and technical users.
  • Deciding where to start inside the docs site.

What to do first

  1. Identify a workspace administrator.
  2. Decide which users primarily work in the product and which users primarily integrate with it.
  3. Review the core operating model in Platform overview.
  4. Review Entity views and forms so the team understands the shared page and field model before diving into entity-specific pages.
  5. Use Roles and workflows to assign the right reading path to each team.
  6. Complete the first-run checklist in Onboarding.

For most teams

  1. Platform overview
  2. Entity views and forms
  3. Roles and workflows
  4. Onboarding
  5. Trials
  6. Relevant workflow pages for the records your integration will touch.
  7. Evidence Packs

For administrators

  1. Onboarding
  2. Admin and workspace management
  3. Entity views and forms
  4. Organizations and sites
  5. Governance and compliance

For integration owners

  1. Platform overview
  2. Integrations and API
  3. Entity views and forms
  4. relevant workflow pages for the records your integration will touch

What a new team should complete in the first week

  • Confirm who owns workspace administration and permissions.
  • Confirm which records will be managed first: trials, documents, or evidence packs.
  • Align on how review, approvals, and restoration should be handled internally.
  • Identify whether AI-assisted drafting or analysis is in scope from day one.
  • Decide which users need API access and which only need product training.

Common mistakes to avoid

  • Starting with API contracts before the team understands the product workflow.
  • Treating approvals, revisions, and history as edge cases instead of normal operational tools.
  • Assuming AI-assisted output can bypass human review.
  • Spreading admin ownership too broadly too early in the rollout.

When to use the API reference

Move to TrialStack API reference when you need:

  • Exact request and response schemas.
  • Operation-by-operation behavior.
  • Integration detail that is too low-level for customer workflow docs.