- Data tools act as you. Anything that returns rows or charts applies your resource access and row-level security. You never see data through the assistant that you couldn’t open yourself.
- Write tools enforce the UI’s levels. A tool that changes something checks the same permission level as the equivalent button. If you lack it, the tool refuses and the assistant relays the reason.
Data and discovery tools
Available to Ask Netter and the ontology design chat.Graph navigation
These let the assistant find and traverse the connections between your datasets and entities. All of them are filtered to the assets you have Viewer or higher on.Ontology design tools
Available to the ontology design chat. These change your data model, so each carries a permission gate that matches the ontology editor’s buttons.App design tools
Available to the app design chat. The chat shapes an app’s data contract; the actual access a viewer gets is enforced at runtime by the app’s bindings and actions.Pipeline tools
Available to the pipeline chat. It builds a pipeline—a graph of steps and pre-coded operators—inside a project you already have access to. The chat validates step config and graph structure as you go; it never reaches past your access, and the resulting pipeline’s permissions and row-level security apply when it runs.Workflow tools
Available to the workflow chat. It builds a workflow—a graph of nodes wired to a trigger. As with the pipeline chat, structure is validated as you build, and access is enforced when the workflow runs.
A node that writes to an entity must be covered by an approved action, and that write is checked against the permissions and row-level security of the user the workflow runs as. The builder flags any uncovered write so a workflow can’t ship with a hidden permission gap.
Dashboard chat tools
Available to the dashboard chat. It edits a dashboard’s layout and code—it shapes the view, not the data.
There are no data-write tools here. The dashboard chat can’t insert, update, or delete rows—it only arranges how existing data is shown.
Why this design
The assistant runs your tools, not a superuser’s. Reads are filtered to what you can see, writes are checked against what you can change, and destructive operations ask you to confirm in words. The assistant can move faster than you clicking buttons, but it can’t reach past your permissions.Next
- Assistant overview — the chats and how tool calls surface in the transcript.
- Permissions and row-level security — the model the tools enforce.
- Entity bindings — how app design tools translate into viewer access.