> ## 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.

# Key concepts

> A short glossary of the core nouns in Terminus Hub: governance models, taxonomies, fields, picklists, submissions, records, short URLs, QR codes, and workspaces.

Everything in Terminus Hub maps to a small set of nouns. Learn these nine and the rest of the product reads naturally. They nest from the outside in: a **governance model** holds **fields** and **picklists** and groups them into **taxonomies**; people fill in a taxonomy as a **submission** inside a **workspace**; approving a submission produces **records**, and a record can carry a **short URL** and a **QR code**.

<Info>
  For how these pieces connect, with the full hierarchy in one place, see the [data model](/concepts/data-model).
</Info>

## The glossary

<ResponseField name="Governance model" type="container">
  The top-level container for one set of campaign rules: all the fields, picklists, and taxonomies for an account or a brand. You author it, then publish revisions of it. See [governance models](/reference/governance-models).
</ResponseField>

<ResponseField name="Field" type="building block">
  One named piece of data you capture or generate, like `campaign_name`, `utm_source`, or a computed `tagged_url`. Each field has a type that decides how its value is entered or derived. See [fields](/reference/fields).
</ResponseField>

<ResponseField name="Picklist" type="option source">
  A reusable list of allowed values that backs a dropdown field. Lists can be static, parent-to-child (cascading), or sourced live from another taxonomy's approved records. See [picklists](/reference/picklists).
</ResponseField>

<ResponseField name="Taxonomy" type="form shape">
  An ordered selection of fields inside a governance model. A taxonomy is the form people fill in, and it is what you connect to a workspace. See [taxonomies](/reference/taxonomies).
</ResponseField>

<ResponseField name="Workspace" type="scope">
  A scoped environment where a team collects data. You attach one or more taxonomies to a workspace and control who can submit to it. See [workspaces](/reference/workspaces).
</ResponseField>

<ResponseField name="Submission" type="draft batch">
  A batch of one or more draft rows entered against a taxonomy in a workspace. A submission can be saved as a draft, sent for review, or approved. See [submissions](/reference/submissions).
</ResponseField>

<ResponseField name="Record" type="approved row">
  One approved row of campaign data, created by approving a submission. Records are validated, read-only, and have a stable identifier (a `trm0...` Terminus ID). See [records](/reference/records).
</ResponseField>

<ResponseField name="Short URL" type="output">
  A branded short link generated from a record's destination URL, for example `ter.link/aB3xZ`. Each click is counted and attributed to the record. See the [short URL field](/reference/fields/short-url).
</ResponseField>

<ResponseField name="QR code" type="output">
  A QR code generated from a record's link or another field. A scan is counted just like a click and reported separately from link traffic. See the [QR code field](/reference/fields/qr-code).
</ResponseField>

## One more: the revision

A **revision** is an immutable published snapshot of a governance model. Submission forms and validation always run against a published revision, never the live editor, so changing the model never breaks a submission that is already in flight. See [publishing a revision](/guides/publish-revision).

## Choose your path

<CardGroup cols={3}>
  <Card title="Building governance models" icon="wrench" href="/tutorial">
    Start with the [tutorial](/tutorial), then dig into the [field reference](/reference/fields) or grab a [recipe](/recipes/cascading-dropdowns).
  </Card>

  <Card title="Submitting data" icon="users" href="/concepts/form-vs-grid-mode">
    Learn [fill modes](/concepts/form-vs-grid-mode) and how [submissions](/reference/submissions) move to approval.
  </Card>

  <Card title="Integrating via the API" icon="code" href="/api-reference/overview">
    See the [API reference](/api-reference/overview) and [authentication](/api-reference/authentication).
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Go from sign-up to your first short URL.
  </Card>

  <Card title="Data model" icon="sitemap" href="/concepts/data-model">
    See how all of these concepts fit together.
  </Card>
</CardGroup>