Naming history: Starting with the Victorious Vicuna release (January 2026), “Chat Settings” was renamed to “Agent Settings.” With the Wise Wolf release, the Multi-Agent feature now enables creating and managing multiple Agents per organization.
Creating and Configuring an Agent
An administrator (System Admin, Account Manager, or Company Admin) can create Agents from the administration panel with the following settings:General Settings
- Name and description: identify the Agent in the user interface and the discovery page.
- Instruction (system prompt): defines the Agent’s behavior for all users who have access to it.
- Default model: specifies which AI model is used by this Agent.
- Company: the company linked to this Agent.
- Support email: the email address where bug reports will be sent when users encounter issues and submit reports.
Tools and Capabilities
- Agent Tools: manage the tools available for this Agent (e.g., Search Documents, Search Visual).
- Agent MCP Servers: configure the MCP servers available for this Agent (e.g., Web Search Linkup).
Agent Ownership
When creating an Agent, an administrator must choose its ownership, which determines who can access it. Ownership is set at creation and cannot be changed afterwards.| Ownership | Who can access it | Team required? |
|---|---|---|
| Personal | The creator only | No |
| Company | All users in the organization | No |
| Team | Members of a specific team | Yes — select the target team at creation |
The
ownership field (Personal, Company, Team) was introduced in Xenial Xerus (March 2026) as a shorthand to simplify agent creation. On earlier versions, the same access control is achieved by passing the appropriate group_id directly: a user’s personal group for a personal agent, the company-wide group for a company agent, or a specific team’s group for a team agent.Document Scope
- Documents and Workspaces: select the document sources the Agent can access to search and cite information.
Workspace Restriction
By default, a shared Agent (Company or Team) can access all workspaces belonging to its team. You can optionally restrict this to a specific subset of workspaces using the Workspace Restriction setting, configurable after the Agent has been saved. When a workspace restriction is set, the Agent will only search and cite documents from those workspaces — regardless of what users pass in their queries.Workspace Restriction is available from Xenial Xerus (March 2026). On earlier versions, agents always access all workspaces of their associated group.
Access Control
- Teams: automatically determined by the ownership chosen at creation. Defines which users can view and use this Agent — a central element of data governance.
Viewing Agents
The Agent Settings page in the administration displays all Agents associated with the organization. Administrators can view and manage all Agents, regardless of which teams they are assigned to.On the user side: Users only see the Agents they have access to through their teams, from the chat interface and the Agent discovery page.
Default Agent vs Specialized Agents
Each organization has a default Agent (“My Assistant”) that is automatically selected when creating a new session. Additional Agents created by administrators are specialized Agents that users can select manually.Permissions Summary
| Action | User | Administrator |
|---|---|---|
| Create a Personal Agent | ✅ | ✅ |
| Create a Company Agent (entire organization) | ❌ | ✅ |
| Create a Team Agent (specific group) | ❌ | ✅ |
| Configure tools, MCP, documents, workspace restriction | ❌ | ✅ |
| Use an Agent (if access via ownership/group) | ✅ | ✅ |
| Manage favorites | ✅ | ✅ |
| View Agents you have access to (chat interface) | ✅ | ✅ |
| View all organization Agents (admin) | ❌ | ✅ |
Best Practices
- Name your Agents clearly: an explicit name and description help users choose the right Agent (e.g., “HR Assistant — Leave & Payroll”, “Regulatory Watch — Banking Sector”).
- Limit the document scope: an Agent with access to a targeted set of documents will produce more relevant responses than one with access to everything.
- Use teams for governance: assign each Agent to the relevant teams to ensure only authorized users can access the associated documents.