Skip to main content
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.
For how these pieces connect, with the full hierarchy in one place, see the data model.

​
The glossary

​
Governance model
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.
​
Field
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.
​
Picklist
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.
​
Taxonomy
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.
​
Workspace
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.
​
Submission
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.
​
Record
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.
​
Short URL
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.
​
QR code
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.

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

​
Choose your path

Building governance models

Start with the tutorial, then dig into the field reference or grab a recipe.

Submitting data

Learn fill modes and how submissions move to approval.

Integrating via the API

See the API reference and authentication.

Quickstart

Go from sign-up to your first short URL.

Data model

See how all of these concepts fit together.