Administer
How the CID222 dashboard is organised — the sidebar groups, the roles that see them, licence gating, and the in-product help assistant.
- Version: 0.4
- Role: admin_user
Everything you do after the appliance is in service. This guide is organised to match the dashboard: each page you can open has exactly one documentation page, linked by the same page identifier the product uses internally, so the in-product help panel always resolves to the page you are standing on.
The sidebar
The left navigation has eight groups. Which entries you see depends on your role and on the installed licence, so a given appliance shows a subset of this list.
| Group | Pages |
|---|---|
| (no heading) | Dashboard, AI Analyst, My team |
| AI Inventory | Models, MCP Servers |
| Detection & Filtering | Security Filters, All Detections, AI Usage, Claude Code, Browser Inspection, File Redaction |
| Security & Compliance | Risk Analysis, Compliance, Compliance Reports, Event Logs |
| Governance | Governance Overview, Governance Inventory, Risk Classification, Ownership |
| Administration | Tenant Management, Access Control, Tenant Groups, Credentials, API Keys, Endpoint Agent, Browser Extension, Repository Tracking, Tenant Analytics, Token Cost & Savings |
| Testing | Playground, Filter Testing, OCR Benchmark, API Key Testing, ML Engine |
| Settings | Profile, License, System Updates, License Management |
Four entries appear conditionally rather than by role:
- My team appears only for somebody who leads at least one tenant group.
- Playground is hidden from a
viewer, which is the one entry a viewer does not see. - Endpoint Agent and the whole Testing group are lab surfaces, hidden on every licensed
deployment. They render on an unlicensed development box, on the issuer hub, or where
CID_ENABLE_LABistrue. - License Management is the owner console. It renders only on the licence-issuing hub and is inert on a customer appliance, so it has no page in this guide.
The sidebar is not the security boundary — the API is. Entries are filtered from the gateway's own page manifest, which is why the menu can settle a fraction of a second after a page loads rather than blanking itself on a slow request.
Roles
CID222 has five fixed roles. An operator cannot create a sixth.
| Role | Reaches |
|---|---|
superadmin | Everything, including account management and the access matrix. Can never be denied a page |
admin_user | Day-to-day administration: policy, detections, compliance, governance, channels, reporting. Not account management |
normal_user | The chat, its own settings, and My team where it leads a group. No administrative page |
viewer | Every page except the chat, read only. Mutating requests are refused globally with READ_ONLY_ROLE |
auditor | Compliance and governance evidence across every account, the audit trail, and its own settings. Never message content, and never the chat |
Three pages are superadmin-only even for an admin_user: Tenant Management, Access
Control and Endpoint Agent. The reasoning, the matrix that narrows the rest, and the honest state of the capability
model are on Access control.
Licence gating
Roles decide who. The licence decides whether this appliance has the module at all. A page whose licence key the installed licence lacks is removed from the sidebar, refused by the route guard, and shown dimmed in the access matrix so a policy you configured survives a lapsed renewal.
That axis applies to the superadmin too — a superadmin of a Starter appliance is still on a Starter appliance. The deliberate exception is License itself, which carries no key, so the page that installs a renewal can never be hidden by the lack of one.
Which page each licence key switches off is generated from the code in licence tiers and feature keys.
The help panel
A floating help button sits on every page. It answers in one of two ways:
- From the built-in product catalog when no language model is configured. The panel says Answering from the built-in product catalog — accurate, but not conversational.
- From the configured AI model when a provider credential exists. The panel names the model that answered and states that your question and a summary of this screen's configuration were sent to it; What is sent to the AI provider explains exactly what.
The assistant is page-aware and reads live configuration, so it can name the actual misconfiguration rather than describe the feature in general. Some answers offer an Apply button that makes the change for you; only administrators see it act, and it refuses if the setting has moved since the card was written.
Help questions are deliberately outside the tenant content policy: by default they are not inspected at all, and a help question is never rejected however inspection is configured — the strictest outcome is that values are masked before the question is sent. That behaviour is configured under Settings.
To hide the button, use the panel's own menu; Settings → Appearance brings it back.
Conventions on these pages
Every administration task page states the licence tier and role it requires before the first step, ends with a Verify section you can actually observe, and lists the messages the product shows when the procedure fails. Where a control exists in the interface but changes nothing, the page says so plainly rather than implying protection or behaviour you do not have.
Where to start
- Read the dashboard — what the landing page is telling you.
- Manage users — create the accounts everything else is scoped to.
- Manage provider credentials — without one, no model answers.
- Access control — decide which roles are offered which pages.
Last updated on