> ## Documentation Index
> Fetch the complete documentation index at: https://docs.terminus.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Terminus Hub: structured data governance for teams

> Terminus Hub lets teams define a governance model for their campaign data, collect it through a governed workflow, and turn approved records into short URLs, QR codes, and click analytics.

Terminus Hub is where teams agree on the rules for their marketing campaign data and then put those rules to work. You design a **governance model** that says exactly what a campaign should look like: the fields to capture, the dropdown lists that constrain them, and the taxonomies that group fields into a form. People then fill in that form, you approve their entries into clean records, and Terminus turns each record into a short branded link and QR code whose clicks it tracks for you.

The result is campaign metadata that is consistent by construction. Instead of policing UTM tags and naming conventions after the fact, you encode them once in the model. Every submission is validated against the published rules before it can become a record, so the data your reports and integrations read is already correct.

<Info>
  New here? Read [key concepts](/key-concepts) for the vocabulary, then follow the [quickstart](/quickstart) to go from a blank account to your first short URL.
</Info>

## The core flow

Terminus Hub follows one path from rules to results. Five steps:

<Steps>
  <Step title="Define a governance model">
    Create a model and add the [fields](/reference/fields) you need (a campaign name, a source, a destination URL, and so on). Back your dropdowns with [picklists](/reference/picklists), then group the fields into one or more [taxonomies](/reference/taxonomies). A taxonomy is the form people will fill in.
  </Step>

  <Step title="Publish a revision">
    [Publish a revision](/guides/publish-revision) to lock the model into an immutable snapshot. Forms and validation always run against a published revision, so editing the model never breaks a submission that is already in flight.
  </Step>

  <Step title="Submit campaign data">
    In a [workspace](/reference/workspaces) with a taxonomy attached, people enter campaign data in the [submission builder](/concepts/submission-pipeline), one record at a time or many rows at once. Computed fields like tagged URLs fill themselves in as they type.
  </Step>

  <Step title="Approve into records">
    A reviewer approves the submission. Approved rows become [records](/reference/records): structured, validated, read-only, and queryable.
  </Step>

  <Step title="Get short URLs, QR codes, and analytics">
    Each approved record can carry a short branded link (for example `ter.link/aB3xZ`) and a matching QR code. Terminus records every click and scan, then reports them in [analytics](/guides/analytics) broken down by your taxonomy's UTM and campaign fields.
  </Step>
</Steps>

## What you can build

<CardGroup cols={2}>
  <Card title="Governance models" icon="boxes" href="/reference/governance-models">
    The container for your fields, picklists, and taxonomies. Author it once, publish revisions, export or import it as JSON.
  </Card>

  <Card title="Fields and field types" icon="layers" href="/reference/fields">
    Twelve field types, from free text and validated URLs to computed concatenations, tagged URLs, short URLs, and QR codes.
  </Card>

  <Card title="Picklists" icon="list" href="/reference/picklists">
    Static lists, parent-to-child cascading lists, or lists sourced live from another taxonomy's approved records.
  </Card>

  <Card title="Submissions and records" icon="inbox" href="/reference/submissions">
    A governed form (in quick, form, or grid mode) for collecting data, and the approved records it produces.
  </Card>

  <Card title="Short URLs and QR codes" icon="link" href="/recipes/tagged-url-utm">
    Branded short links and QR codes generated from a record's destination URL, with every click and scan counted.
  </Card>

  <Card title="Analytics" icon="chart-area" href="/guides/analytics">
    Click and scan dashboards that group and filter by any field in your taxonomy, so the data you governed is the data you measure.
  </Card>
</CardGroup>

## Templates and the API

You do not have to build a model from scratch. The [templates gallery](/guides/templates-playground) ships ready-made governance models for common cases (a simple UTM starter, B2B demand-gen, ecommerce, agency multi-client, and more). Preview one, then create a model from it in a click and customize from there.

For programmatic access, Terminus exposes a versioned REST API. Authenticate with an [API key](/authentication), then read governance models, records, and workspaces, or create submissions, all under the same rules the UI enforces. See the [API reference](/api-reference/overview) to get started.

## Where to go next

<CardGroup cols={3}>
  <Card title="Key concepts" icon="book-open" href="/key-concepts">
    A short glossary of the core nouns and how they fit together.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    The fastest path from sign-up to your first short URL.
  </Card>

  <Card title="Campaign URL Builder tutorial" icon="graduation-cap" href="/tutorial">
    Build a working governance model end to end, with picklists and computed fields.
  </Card>
</CardGroup>