Personas
A persona is the role you look at TIDE as: the head of platform, the finance owner, the security and compliance officer, and so on. It decides what the console leads with and who the chat answers for. It is a lens, never access: choosing a persona does not grant or remove anything you may do (that is your role on the instance, under Admin). It is also not the TIDE puppy, which is the brand persona.
Settings › Personas is on the platform console only. Each persona is a card with a plain description, what it decides, what it asks of TIDE, the pages it opens first, the regulations it answers for, and where it opens.
The seven personas
| Persona | Looks at TIDE to answer | Opens on |
|---|---|---|
| Platform and infrastructure lead | Is anything unhealthy, did the last commit ship, which agents and runners stopped reporting | DevEx › Clusters |
| Data platform lead | What the estate holds, which connections fail a control, where the data comes from | DataEx › Estate |
| Finance owner, Capex and Opex | What each initiative consumes, whether spend is ready for Capex or Opex | Intelligence › Overview › CFO |
| Security and compliance officer | Who has access, whether keys or personal data are exposed, whether the audit chain is intact | DataEx › Agents › Trust |
| AI and machine-learning lead | Which models and agents run, how much autonomy they have, what the judge found | DataEx › Agents |
| Executive sponsor | The overall verdict, which dimension is weakest, what waits for a decision | Intelligence › Overview |
| Analyst | Which findings and exceptions are open, which rule fails and on which data | Intelligence › Overview › Analyst |
The Analyst and CFO views are the bodies of those two personas. A persona with no dashboard of its own does not get one drawn with figures: the Overview says it has none (not measured here) and lists the pages where its figures are measured. No figure appears in a persona’s description.
A card names the regulations a persona answers for (for example GDPR, PIPEDA, Law 25, CCPA/CPRA, SOC 2, ISO/IEC 27001, 27701, 31000 and 42001, the EU AI Act and NIS2) from the platform’s compliance catalog. This says which regulations the persona asks about. It does not say that any obligation is met or that the platform is certified.
Who changes what
- An administrator (a session admin) turns each persona on or off for the organisation and chooses the default. At least one persona stays on.
- Everyone sees the cards read-only and uses Use this persona to choose their own, or Use the organisation default to clear it. With no choice you get the organisation default; with neither, the console is the generalist view.
- A persona the organisation turns off stops applying to the people who chose it. The card says so and the default applies.
- Every change is recorded in the audit chain.
Until an administrator saves, the page says nobody has configured the personas: every persona is on and none is the default. If the stored settings cannot be read, the page says so with the reason; that is not shown as “no personas”.
Where a persona shows
- Intelligence › Overview has a persona switch under the title. The strip opens on the
persona’s own view (the Analyst or CFO view first for those two) and a persona that opens
elsewhere offers a button to go there. Links such as
?tab=cfoDashboardstill open the view they name. - Ask TIDE has a persona picker above the field, with a Generalist option. It starts on your persona (else the organisation default, else Generalist). The pick goes with the question, so the answer is framed for that role and points to its pages, and the suggestions lead with the persona’s own. The FORGE chat does not carry a persona yet.