NeuroVaultAI ASSISTANTS · AGENT GOVERNANCE
Control your AI assistants.
Choose what an assistant can access, what it can do, and when it needs approval. An assistant is an AI tool or automated service connected to NeuroVault. These controls apply only to requests sent through NeuroVault; they do not control other AI tools automatically.
Checking your session…
CONNECT YOUR FIRST ASSISTANT
A clear next step.
Your signed-in workspace is used automatically. No organization IDs to enter.
Loading setup progress...
What does this connect?
This checks the identity and tool-access grant in NeuroVault. Registering an identity does not connect your AI provider. The guided provider connector is not available yet; requests must currently be routed through the existing integration.
DEMO — NO EXTERNAL ACTION
Try approval flow
Explore a fictional request with a simulated reviewer. No accounts, rules or real requests are changed.
- Submit a fictional support ticket
- Wait for a teammate to review
- Receive a decision
- Complete the approved action
In real use, a separate eligible teammate must approve. A simulated reviewer can never approve a real request.
Prefer written instructions? Open the setup guide
CONNECT YOUR FIRST ASSISTANT
One step at a time.
You keep control of what your assistant sends. Follow these three steps; your existing assistants and rules stay unchanged.
Start with a name you recognize.
For example, “IT Helpdesk Assistant.” Add its purpose, owner and the tool it needs on the registration page.
Registration creates an identity. It does not connect OpenAI automatically or give the assistant permission to run tools.
Add an assistantAlready registered an assistant?
Continue to step 2. Keep its credential private; never paste your OpenAI API key into an assistant credential field.
Access and protection work together.
First, an administrator reviews tool access on Your assistants. Then review Permissions to decide which requests to block, mask, allow or send for approval.
Want approval before sharing? A different person with the approver role in your workspace must review the request. You cannot approve your own assistant. If you work alone, use blocking or masking rules instead of an approval rule.
Review tool access Review protection rulesWhy are these separate?
Tool access decides which connection the assistant can use. Protection rules decide what information can pass through that connection. An Allow rule alone does not grant tool access.
Start small. Use fictional information.
Open Run an action, connect using the assistant’s NeuroVault credential, and select an authorized tool. Read its destination before sending: an allowed request can execute a real tool.
The result tells you whether it completed, was blocked, was masked or needs approval. Approval does not run the request by itself; the connected runner must resubmit the same request.
Try a request View past resultsConnecting an external AI service
Your integration or runner must send its tool requests through NeuroVault. Registering an assistant here does not protect calls that bypass NeuroVault.
This guide does not change settings or mark setup as complete. Verify access and the actual request result before using real information.
Recorded outcomes
Requests are selected by creation time. Outcomes reflect the latest snapshot. Required redaction does not mean execution succeeded.
Needs investigation
Approval states
Action historyAdvanced: download reports and technical evidence
Download evidence
PDF provides an analytical summary and the latest 25 action references. JSON contains every included action and its recorded events. Exports are limited to 1,000 actions and 50,000 events; choose a shorter window if needed.
Downloads contain protected identifiers and hashes. Store them securely. Each download is a fresh snapshot, so its fingerprint may differ from an earlier download.