Features — the catalog of what the platform does
The Features screen answers a single question: what can I do here?
It lists every platform capability as a card, grouped by the stage of work it belongs to. Each card carries an icon, a name and one line saying what it is for — and takes you straight to the screen.
It is the sibling of the Sistema (System) screen: that one answers "what can I configure", this one answers "what can I do". Both share the same layout on purpose — learn to skim one and you can skim the other.
Where it lives
Sidebar → Features, just above Documentation and System.
The four categories
| Category | What for | What's inside |
|---|---|---|
| Descobrir (Discover) | Find and understand the data available on the platform | Knowledge Catalog, Explore Data, Intelligent Query Layer |
| Investigação (Investigation) | Work cases, cross-check evidence and track open items | Investigation, PJ Onboarding, Compliance Pending Items, Lineage, Cases, Alerts, Notebook |
| Processar (Process) | Ingest, transform and assess content at scale | Database Agents, Persona Agents, Twin Objects, Rules, Batch Screening, Upload, DATTA Captain |
| Governança (Governance) | Curation and quality of the knowledge behind the answers | Knowledge Curation, Data Governance |
Preview features
Seven features carry an italic (Preview) label next to their name:
| Feature | Where the label shows |
|---|---|
| Intelligent Query Layer | card under Discover |
| Lineage, Cases, Alerts, Notebook | cards under Investigation |
| DATTA Captain | card under Process, tab and card under System, full-screen bar, assistant header |
| DATTA BI | sidebar group, DATTA Prep full-screen bar |
The label means feature under development: behavior, screens and contracts may change without notice between releases. It says nothing about permissions or availability — the feature is there and opens normally for anyone with access.
Lineage and Cases have no page of their own in this documentation; for them, this table is the record of the preview.
Maintenance
The list is VIEWS_PREVIEW, in the shell (compiled/index.js), next to VIEW_META. The suffix deliberately stays out of VIEW_META.label: that label also feeds the breadcrumb, the menu tooltip and the tab title, and (Preview) there would repeat the mark across every trail until it became noise.
Taking a feature out of preview means removing its key from that list — and deleting the note at the top of the matching page in this documentation, plus its row in the table above. Three screens repeat the text instead of reading the list — the Captain full-screen view (compiled/captain.js), DATTA Prep (compiled/dattax-prep.js) and the assistant (captain-widget.js) — because none of them can depend on the shell: the first two are fragment bundles, and the third also mounts outside the shell, on pages where compiled/index.js is not even loaded.
DATTA Prep is not an eighth feature: it is a screen of DATTA BI (trail: [BC_G.bi]), and it carries the mark because anyone arriving by deep link never sees the sidebar group that carries it.
Search
The field at the top filters by name and by description. A category whose cards were all filtered out disappears with them — the label never floats over an empty grid.
Why this screen exists
Until August 2026 these four categories were collapsible groups in the sidebar. Remembering where a screen lived meant opening all four, one by one, and the sidebar carried four headers that led nowhere on their own. The menu also had no room for a description: just the name, with no hint of what it was for.
The sidebar kept what people open every day — Chat, Rules, Batch Screening, Panels, Upload, Explore Data and the DATTA Extract, BPM and BI groups. The catalog of what exists got a screen of its own, where the description fits.
Permissions
The screen itself is open to any authenticated user: it is an index, not data. Clicking a card takes you to the corresponding screen, and each screen enforces its own permissions — anyone without access gets the destination screen's refusal, in Portuguese.
This is deliberate: the authorization gate belongs to the backend (CLAUDE.md §13), never to the menu. Hiding the card would be a visual hint, not a barrier.
Maintenance
The order, category and icon of each capability live in FEATURE_CATEGORIAS, in the shell (compiled/index.js). The name and description do not: they come from VIEW_META, the same source that feeds the breadcrumb and the sidebar tooltips.
So when adding a new capability, declare it in VIEW_META (already mandatory for any view) and add one line to FEATURE_CATEGORIAS with the view, the category and the icon name. Writing the text in both places would create a mirror that ages on its own.