Features — the catalog of what the platform does
The Features screen answers a single question: what can I do here?
It lists the platform capabilities as cards — all of them, or the active workspace's —, grouped by the stage of work they belong 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.
With an active workspace
With a workspace active, the screen shows only the features checked in it (the Features tab of the workspace manager) — the same filter as the side menu. A line below the title says which workspace the filter comes from, with the Gerenciar workspaces shortcut. Chat, Panels and DATTA Captain always show (Chat since 2026-09-29: it is the door to the Captain and the assistant); a category left without cards disappears; the DATTA Extract card keeps only the checked screens.
In All workspaces, or with a workspace that checked no feature, the screen lists everything. Switching workspace, or saving the active workspace's features, updates the screen right away.
The filter exists because 14 of the 25 workspace features have no menu item of their own: without it, checking or unchecking those features changed nothing anywhere. The full filter rules are in the Workspaces guide, under "The side menu shows the active workspace".
The six categories
| Category | What for | What's inside |
|---|---|---|
| Descobrir (Discover) | Find and understand the data available on the platform | Chat, Panels, DATTA BI, Knowledge Catalog, Explore Data, Intelligent Query Layer |
| Investigação (Investigation) | Work cases, cross-check evidence and track open items | DATTA Investigation (also in the side menu, below Chat), Compliance Pending Items, Lineage, Cases, Alerts, Notebook |
| Processar (Process) | Ingest, transform and assess content at scale | Twin Objects, Rules, Batch Screening, Upload, DATTA Extract (Packages, Assistant, ETL Designer, Scheduler) |
| Agentes (Agents) | AI agents that query databases, answer for a domain or operate the platform | Database Agents, Persona Agents, DATTA Captain |
| DATTA BPM | Model BPMN processes and track what the engine runs | Process Modeler, Process Monitor |
| Governança (Governance) | Classification, owner and steward of the catalog's datasets | Data Governance |
The DATTA Extract card
DATTA Extract is one product with four screens, and it has one card. The first click opens the four screens inside the card itself — Packages, Assistant, ETL Designer and Scheduler —, and clicking one of them takes you to that screen. Clicking the header again closes the card.
Curation of AI-generated knowledge assets is no longer a Governança card: since September 2026 it is the Curadoria tab of the Knowledge Catalog (under Discover), next to the Glossário tab.
What has no card
Process Panel and PJ Onboarding are not in the catalog: they are panels inside the Panels feature, and you reach them through the Panels gallery. They can still be enabled or disabled per workspace, in the workspace settings.
Neo4j Browser and Neo4j Bloom also left the catalog in September 2026. They remain under System → Data Layer → Neo4j and System → External Access.
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 Agents, 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.
Each account may, however, not see preview features: that is the Funcionalidades em preview switch in user registration (see the users guide), on by default for the Administrator. Off, the seven disappear from the menu, from this screen and from System, and the DATTA Captain button leaves the top bar. The switch reaches the browser as the token's preview claim, read by the shell in previewDoUsuario (compiled/index.js) and applied in the same filtroDoMenu as the workspace filter; the assistant (captain-widget.js) has its own reading.
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, within what the active workspace shows. A category whose cards were all filtered out disappears with them — the label never floats over an empty grid. With no result, the screen says whether the search may have hit the workspace filter.
Search also looks at the screens inside the DATTA Extract card: typing "ETL" shows the card already open, with only ETL Designer in it.
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. The workspace filter is only a hint too: hiding a card does not prevent opening the screen through a link.
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.
The card of a product with several screens (today, DATTA Extract) is an item with grupo, label, desc, icon and the itens list of its screens — it is not a view, so its label lives in the table itself.
A workspace feature that must not have a card goes into FEATURES_FORA_DO_CATALOGO, right below, with the reason. The make features-catalogo-check gate fails if a workspace feature is in neither place, in both, or if the exclusion list names a key that no longer exists.