A Tour of the App
Classifyre’s left-hand navigation is organised around one journey: connect systems, scan them, review what was found, and investigate what matters. This page walks through every screen in that order — what it shows, what you do there, and where the deeper documentation lives.
Workspaces
The screen before every other screen. Classifyre opens on the workspace directory: a card for each isolated workspace on this instance, with its name, description, any links you have pinned to it, and a live count of sources and failing sources. Cards are grouped under category headings, so a directory of sixty stays readable. Pick one to enter it — everything documented below happens inside the workspace you opened.
Use New workspace to add one, the gear on a card for its settings (Settings → General inside the workspace), categories, links and URL slug, Categories to manage the shelves themselves, and All workspaces at the top of the sidebar to come back and switch. Inside a workspace, the line under its name in the sidebar names the category it is filed under and links to everything filed alongside it.
Learn more: Workspaces — what is isolated, how addressing works, how categories and links are organised, and what governance the enterprise offering adds.
Dashboard
Where your work starts. The Dashboard is the page a workspace opens on. It is about the data you answer for, not about findings or scans. Mine shows the assets you own or steward, All the whole workspace; pick 7, 30 or 90 days and a source. It has three cards across the top:
- Governance brief — how many assets are governed, out of how many, and one bar that splits them by lifecycle (certified, draft, deprecated, retired) and the ungoverned rest.
- Quality — the quality score and each dimension’s score, and how many governed assets fail a quality rule. The card takes the colour of the most severe failing rule, the same scale findings use; it turns green when every rule passes.
- Incoming — access requests waiting for you right now (whatever the period or source), and how often your data was read today and over the period.
Below them: usage over the period, with the assets read most or whose use grew most; what waits on you (access requests to approve or decline in place, failing quality, unfinished governance, and the unowned assets read most, each shown only when there is something in it); and quality results per day.
Every count of assets opens those assets on the Assets page, with the same filter: each part of the governance bar, the failing assets, the assets to govern first. The Incoming request count leads to the requests to decide, on the same page.
Findings and scans have their own summaries: the Findings page opens on counts by priority and a trend over time, the Scans page on counts by status. Both are in the sidebar.
Explore
What an asset, a source or a glossary term is connected to, and why. Every source and every asset has a Connections tab, every glossary term opens on Where it is connected, and duplicate review has an Explore section that draws its pairs, filtered by pattern, kind, score, review state and source: a canvas of what it is connected to, by lineage, links, duplicates, shared values and meaning, each line saying why. A source’s opens on its most connected assets. Keep every connection, only those inside the source, or only those leaving it for other sources; double-click an asset to dive in, and follow the trail back out. Trace lineage upstream, downstream or both, as far as it goes; badges show what is already in a case or answers a watch. Send what you found to a case, and draw the links the data does not know about (they survive every re-scan).
The Explore tab of the Assets page opens the same canvas as a map of its own, starting from a search, your saved views, or a table of the assets worth starting from; a view there can be saved with a name and the layout you gave it.
Learn more: Explore: Following Connections.
Sources
The systems you’ve connected. Each source is a connection to something you already run — SharePoint, Confluence, Jira, a database, a file share, a local folder. Here you add new sources, test their connection, choose which detectors run on them, and set scan schedules. A source’s page has its findings, its assets, and its Connections: what its assets are connected to, inside the source and in others (Explore).
Learn more: Sources — including the full catalog of source types and configuration fields.
Scans
Every run, past and present. A scan is one pass over a source. This screen shows run history and live progress, counts by status (running, queued, completed, failed), and trends over time. You can also start a scan manually with the scan wizard.
Learn more: Scans — the journey of a scan, its phases, and what repeat scans do.
Assets
Everything your scans have found. Every document, page, file, or record a scan registers becomes an asset with metadata — owner, location, when it last changed. The Assets screen has four tabs, each a card with its count, and each the same asset list, showing the columns and filters that matter there:
- Raw assets — everything your scans registered: filter by status, source, detector or governance, and see which assets carry the most findings and which sources hold the most assets.
- Governed assets — every asset someone owns, scanned or shared: how often they were read over the last 30 days and which were read most (for your own assets and one source, when the list is narrowed to them). Narrow the list to a lifecycle, to failing quality, or to your own.
- Shared assets — saved queries shared as governed datasets: how often they were read, and where they stand (their lifecycle, and whether they can be read now). Each row carries its dataset labels: promoted, blocked, or locked for you. Filter the list by lifecycle, by whether a dataset can be read now, or to the promoted ones; the status card’s counts set those filters too.
- Explore — a map of what is connected, starting from the most connected assets, and under it the assets worth starting from: most lineage, most critical, duplicates, drawn links. A row’s compass draws it on the map. See Explore on the Assets page.
The Dashboard’s numbers open these lists already filtered. The tab you pick stays in the address, so a link or a refresh opens it again. Each asset’s page has its findings and a Connections tab: Explore’s canvas starting from that asset, with its lineage, duplicates, shared values and concepts.
Learn more: Assets & Metadata.
Query data
The rows themselves, with SQL. The Query data page queries the tables you may read, and joins tables of different sources in one query: the editor, and beside it your tables, history and saved queries. A query can be saved, or shared with a group as a governed dataset. Connect a tool, at the top right, lets Power BI, Excel or DBeaver read the same tables.
Learn more: Query data with SQL.
Findings
The signals worth acting on. Whenever a detector spots something — a leaked secret, personal data, a tagged term, a value out of range — it raises a finding with a priority and a confidence. This screen is where you triage: filter by priority, source, or status, and resolve, ignore, or mark false positive in bulk. Your decisions stick across future scans.
Learn more: Findings & Results and Detectors.
Duplicate review
The same thing, seen everywhere. Assets that share concrete values — an email address, an ID, a name — or that read as near-duplicate text are matched into pairs and clusters.
The screen is a queue, not a graph: matches are grouped by why they matched, patterns are ranked by how much work one decision settles, and you work through pairs with the keyboard until it’s empty. What you confirm can go straight into a case or an inquiry.
Learn more: Duplicate Review and the plain-English Connections & Duplicates.
Investigations
Where findings become answers. Two tools live here: inquiries — saved questions that keep watching for matching findings — and cases — structured case files where you collect evidence, weigh hypotheses, build a timeline, and write a conclusion.
Learn more: Investigations, Inquiry, and Cases.
Glossary
Your shared vocabulary. The glossary holds the people, organisations, locations, and terms that matter to your organisation, with their aliases. It keeps humans and AI agents talking about the same entities — and when the autopilot proposes a new term or alias, you review and verify it here.
The page opens on the meaning map: every concept grouped by scheme, sized by the evidence behind it, with what turns up together. Select a concept to watch it, bring it into a case or go to its evidence; add, edit and relate concepts right on the map. The lists (concepts, entities, schemes, unbound vocabulary, proposals) are the tabs next to it.
Learn more: Glossary & Shared Vocabulary.
Harness
Mission control for the AI autopilot. The harness shows everything the autopilot does: a live activity timeline, per-run flight recordings with the reasoning behind each decision, token usage, the agents and tools available, and what the system has learned. Its Configuration tab also manages AI providers and the independent Assistant/Harness assignments, along with the Harness’s external MCP tools.
Learn more: Autopilot and its flight recorder and steering pages, plus the AI Providers guide.
Sandbox
A safe place to experiment. Sandbox runs scans in isolation, without touching your real findings — useful for trying out a new source configuration or detector before turning it on for real.
Notifications
The events worth telling you about. Failed scans, sudden spikes or drops in findings, recoveries, and first-scan completions land here (and in the bell at the top right). Filter by priority or type, mark items important, and jump straight to the affected scan or finding.
Learn more: Notifications.
Settings
Workspace-wide configuration. Software version, scan limits, SQL limits, language and timezone, and the MCP server that lets your own tools query Classifyre.
Learn more: Settings, MCP Server.
Where to next
- Follow the data end to end in From Documents to Findings.
- See how the results get worked in Investigations.
- Ready to connect something? Start with the source catalog.