Onboarding Center¶

The one place that answers "where am I, what's left, and what's new" — reached from your own user menu, not a wizard you complete once and never see again.

An administrator whose organisation still needs configuring sees a short setup checklist, and once it is done, a read-only summary of what was set up. Everyone else sees their own role's track: a steward's loop of authoring and reviewing, or a path to finding and trusting what is already governed. Another tab keeps everyone caught up on what changed, and a Decisions tab records what was decided, for administrators and anyone who can read the audit log.

Reached fromUser menu → Onboarding center

TabsSet up · Learn · What's new · Decisions

Required setup steps5

Setup visible toAdministrators only

Who sees what¶

An admin, first run

Set up your organisation — the five required steps, plus recommended and optional ones, until everything needed to go live is decided and recorded.
An admin, already live

The same five steps, pre-filled with what already works — confirming records a sign-off, it doesn't change anything.
A data steward

Govern the work — author a term, classify an asset, file it into a domain, and take a task through approval.
Everyone else

Find and use what's governed — find an asset, read its contract, ask HERC, and subscribe to what changes.

Organisation setup is admin-only, always

The setup checklist only ever renders for the onboarding administrator role — in first-run and confirm mode alike. Everyone else goes straight to their own track. Once the organisation is fully set up, everyone's Set up tab shows "Your organisation is set up" instead — a short, read-only summary of what's configured and when it was completed.

What you see¶

Tab	What it shows
Set up	Your organisation's setup checklist (admins) or your persona's track (everyone else) — each step a row with an obligation badge, a status, and one clear action.
Learn	The tours and documentation pages your roles and active modules actually give you. It doesn't teach anything new — it routes you to what's already built.
What's new	Recent platform announcements, unread ones first. Opening the tab marks them all read.
Decisions	Who decided each setup step, what they decided and when, plus the recommended defaults that were accepted and whether they still hold. Shown to administrators, to anyone holding the audit-log read role (every Platform tier includes it), and to people who hold the role for a setup decision. Nobody else could ever see anything in it, so they don't get the tab.

A badge on the Onboarding center entry in your user menu (top right, above Profile) carries a live count — incomplete required steps if you're the admin who owns setup, plus any unread announcements for everyone.

A line above the tabs tracks progress the same way throughout, for example "2 of 5 required steps done · 6 recommended remaining." Required and recommended are always counted separately, never folded into one blended percentage — so you can tell at a glance whether you're actually ready to go live, not just "busy."

Every step carries an obligation badge:

Badge	Meaning
Required	The organisation isn't considered ready until every one of these is done. Always shown, never collapsed away.
Recommended	Worth doing, can be put off with a reminder date.
Optional	No badge, muted text. Collapsed out of sight once the required steps are done.

At most five steps show above the fold — the rest collapse behind an "Everything else" toggle, so the page never turns into a long list to scroll through.

How it works¶

The first-run redirect¶

The first time an administrator lands on a bare / after signing in, Datahub opens the center for them automatically — once. Nobody else is redirected automatically: every other signed-in person reaches the center the same way as before, through the user menu.

flowchart LR
    A["Bare entry to /"] --> B{"First visit\nfor you, ever?"}
    B -- "No" --> Z["Nothing happens"]
    B -- "Yes" --> C{"Are you an\nadministrator?"}
    C -- "No" --> Z
    C -- "Yes" --> D{"Dismissed or\nsnoozed?"}
    D -- "Yes" --> Z
    D -- "No" --> R(["Opens the Onboarding Center"])
    classDef accent fill:#ff8400,stroke:#e67700,color:#ffffff,font-weight:600;
    class R accent

Figure 2 — the automatic redirect checks first-visit, then administrator, then dismissed/snoozed, in that order. A "no" or "dismissed" answer at any step means you land exactly where you asked to go, nothing more.

It never happens twice for the same person, never blocks the page you asked for while it decides, and never redirects you away from a link someone sent you — a deep link always goes straight through, and your very next bare / visit is still your first one for this purpose.

Three ways a step gets done¶

Some setup steps you confirm, and some complete themselves. The steps on your own role's track you mark done yourself.

	Decision steps	Observed setup steps	Your role's track
Examples	Set language and formats · Decide where data may go · Decide who gets access · Review domains and stewards	Connect a data source	Author a glossary term · Find an asset · Ask HERC
What you see	The live values that would be recorded — e.g. AI assistants off, spreadsheet recipients unrestricted	A button that takes you to where you actually do the thing	A button that takes you there, and Mark as done
How it's completed	You press Confirm. The step itself never changes a setting — it only records that you reviewed what's shown. Change opens the real settings page.	Automatically, once Datahub observes you've done it. There's nothing to mark "done" by hand.	You press Mark as done once you have done it. Datahub does not detect these for you yet, so a step you never mark stays open.

If the values changed while your page was open

Confirm sends exactly what was on screen. If someone else changed that setting in the meantime, Confirm is refused, the step refreshes to the current values, and you confirm again — it never silently accepts a stale read.

A step's lifecycle¶

stateDiagram-v2
    direction LR
    [*] --> NotStarted
    NotStarted --> Locked: role missing
    Locked --> NotStarted: role granted
    NotStarted --> Snoozed: Remind me, recommended only
    Snoozed --> NotStarted: date arrives, or Undo
    NotStarted --> InProgress: signal observed, or decision opened
    InProgress --> Done: signal completes itself, or Confirm recorded
    NotStarted --> Done: Mark as done, your role's track only
    Done --> NotStarted: something it depended on changed
    Done --> [*]
    classDef accent fill:#ff8400,stroke:#e67700,color:#ffffff,font-weight:600;
    class Done accent

Figure 1 — A step's path from not started to done. Required steps skip the Snoozed branch entirely: only Recommended steps can be put off, always to a date you can see and undo. A step you lack the role for shows locked and names the role group that would unlock it, rather than disappearing. A done step can reopen if something it depended on changes underneath it — the row then explains why.

Why a deferred step always shows a date

A snooze with no visible end date reads as a dismissal, and a checklist that reappears after being dismissed reads as nagging. So a deferred step always shows the date it comes back, and an undo if you change your mind.

Already fully set up before this release¶

If your organisation was live and working before the onboarding center existed, the Set up tab opens on the same five steps, but the line under the title reads "Review what is already configured — confirming changes nothing" instead of the first-run wording. Nothing that already works reads as missing — a connected data source shows as connected, a domain with a steward names that steward — and confirming only records that someone looked; it changes nothing.

Putting the whole thing off¶

An admin can dismiss the checklist for a while with Skip for now, in the header. It returns after about a week — nothing already confirmed is lost or reset.

Don't show me this again, next to it, is permanent instead of dated: the automatic redirect never fires for you again, and the badge on your user-menu entry stops counting incomplete steps. The center itself doesn't go anywhere — open user menu → Onboarding center any time you want it, and nothing already confirmed is lost or reset there either.

Accepting recommended defaults¶

The language-and-formats step can also offer Review recommended defaults — a preview of a small set of safe, reversible settings (date and number formats, an acknowledgement of the neutral branding, the seeded sensitivity/SLA policies and workflows, and versioning defaults) you can accept in one go instead of confirming them one at a time. It never touches access, domains, AI-assistant settings, or where data may go — those stay decisions you make deliberately, on their own steps.

Each set you accept creates a task to check later that it still fits. The task opens the Decisions tab, where each set shows what was accepted and what it is today:

Mark verified closes the task, even one somebody has already started, and who verified it is recorded in the task's history. If a setting has changed since, marking the set verified keeps today's value as the new baseline, so it stops showing as changed. A setting that no longer exists is removed from the record. If the values change while you are looking at them, the verify is refused and the tab shows the new values first.
Change settings appears on a set that changed, for anyone allowed to open the page where those settings live.

Permissions¶

Action	Who
See and act on the organisation setup checklist	The onboarding administrator role (granted to Administrator by default)
See your own persona's track, Learn, and What's new	Every signed-in user
Confirm or Change a specific decision	The onboarding administrator role, and whatever role that particular setting itself requires
See the Decisions tab	The onboarding administrator role, the audit-log read role, or the role for any setup decision (which then shows only that decision)
Mark accepted defaults verified	The onboarding administrator role only. An auditor can read what changed but cannot reset the baseline

Limitations¶

Limitation	Why	What to do
The automatic first-run redirect is administrator-only, for now	The first release scopes it to the persona with something to configure; stewards and other roles get their own automatic first run in a later release	Open user menu → Onboarding center after signing in — the center itself, and your own track, are there either way
In-app only	There is no email or chat digest of what's left or what's new	Check the badge on the user-menu entry — it counts incomplete required steps (admins) and unread announcements
"Skip for now" and "Remind me" are time-based, not indefinite	An end date is what keeps a snooze from reading as a dismissal	—
Recommended defaults never cover access, domains, AI-assistant settings, or where data may go	Those are treated as decisions you make deliberately, never something a default makes for you	Confirm or Change those specific steps yourself

Audit & compliance¶

Question a CISO might ask	Where to look
"Who confirmed this, and when?"	Every recorded decision keeps who confirmed it and when. A holder of the audit-log read role can see every recorded decision across the organisation, not only their own.
"Can a non-admin see or touch organisation setup?"	No. The setup checklist only renders for the onboarding administrator role, in first-run and confirm mode alike.
"Does confirming a step change a setting?"	No. A decision step only records that the live values were reviewed. The setting itself only ever changes on its own page, under its own role and its own confirmation.
"What can 'recommended defaults' change?"	Only the safe, reversible settings listed above — never access, domains, AI-assistant settings, or where data may go.
"What has changed since the defaults were accepted?"	The Decisions tab shows the accepted value and today's value for every setting that moved. Marking a set verified is recorded in the audit log with who and when, and the before and after values are stored with that event, so the original acceptance stays on record. The audit-log page does not display those values yet.

Troubleshooting¶

Symptom	Likely cause	Fix
Confirm fails, or values look different right after	Someone else changed that exact setting after your page loaded	Refresh the step — it re-shows the current values — then confirm again
A step shows locked	You don't hold the role group it names	Ask an admin for that role group, or ask a colleague who has it to take the step
No Remind me offered on a step	Required steps can't be deferred — only Recommended ones can	Complete it, or ask an admin whether it belongs on your track at all
The Set up tab looks empty	Nothing on your track currently needs attention	Check Learn or What's new, or come back later
The organisation checklist doesn't appear for you	You don't hold the onboarding administrator role, or your organisation is already fully set up	Ask an admin for status — or look for the read-only setup summary in its place