What you’ll learn: the difference between governance definitions and operational data, and where each one lives.What you’ll build: the
Marketing governance model and the 2026 Campaigns workspace, the empty shells everything else slots into.Prerequisites: Part 1: What you’ll build. Admin access on the account.Why this matters
Terminus Hub keeps a schema (what your data should look like) separate from the data itself (the rows people actually enter). That split is why one company can have a single governance model feeding several workspaces, and why renaming or restructuring in one place doesn’t disturb the others. Before you add a single field, you need both sides in place: the governance model that holds the definitions, and the workspace that holds the data. This part creates both, empty, so the next parts have somewhere to land.Concepts first
Governance model
A governance model is a container for definitions: fields, picklists, and taxonomies. It holds no campaign rows, no submissions, and no records. Think of it as the schema for one business domain. Most companies have one model for everything; some keep two or three when the domains genuinely share nothing (Marketing versus Finance versus HR). In the UI the model is labeled “Model.”Workspace
A workspace is the operational partition. This is where submissions and records live. A workspace has one or more of a model’s taxonomies connected to it. Two teams working from the same model can use separate workspaces so each sees only its own data, even though the field definitions are shared. The rule of thumb: definitions live in the model; data lives in the workspace. When you are troubleshooting, ask “is this a definition problem or a data problem?” The answer tells you which one to open.Step by step
Open the new-model flow
In the navigation, open Models and start a new model. Choose Create from scratch (a blank model) rather than the template gallery.
Name it Marketing
In the Name field, enter
Marketing. Leave the description blank for now. You can add one later from the model’s Settings page.Save the model
Save. You land on the model’s pages. The Fields, Picklists, and Taxonomies areas are all empty, which is expected.
Screenshot coming soon: Part 2 end state.
Check your work
- A governance model named
Marketingexists and appears in the model list. - A workspace named
2026 Campaignsexists and appears in the workspace list. - The
Marketingmodel has no fields, picklists, or taxonomies yet. That is intentional. The next parts add them. - The
2026 Campaignsworkspace has no taxonomies connected yet. Also intentional. You connect them in Part 8 once the taxonomies exist.
What you just built
You now have the two empty containers the rest of the tutorial fills. The model holds every definition you add in Parts 3 through 7. The workspace holds every submission and record you create in Part 8.Gotchas
- Model names are unique per account. If a model named
Marketingalready exists on your account, pick a different name for the tutorial (for exampleMarketing Tutorial) and use it throughout the rest of the parts. - Workspace names are unique per account too, not per model. Same rule: if
2026 Campaignsis taken, pick a tutorial-specific name. - Deleting a model removes everything inside it. Deleting
Marketingcascades to its fields, picklists, taxonomies, and revisions, and it cannot be undone. Only an admin can create or delete a model, so this is hard to trigger by accident, but treat delete as permanent.
Next up
Part 3: Fields basics. Add your first three user-input fields:campaign_name, launch_date, and destination_url. See the governance models reference and the workspaces reference for the full picture.