Enable and Manage
Learn how organization administrators enable official built-in Agents, configure authorized users and knowledge bases, and manage enablement limits, cooldown periods, and deactivation.
Open Built-in Agent Management
Go to Organization Settings → Built-in Agent Management.
You can also select Go to Built-in Agent Management in the Agent Marketplace to open it directly.
If Built-in Agent Management is not in the menu, your plan does not include official built-in Agents. The screen will display Built-in Agents cannot be enabled under the current plan. Please upgrade your plan. Contact the sales team to upgrade.
If you can view the page but the switches are locked, you do not have permission to manage enablement. Contact your organization administrator.

Each row shows the Agent's name, scenario category, version, and current Authorized: {Role Name} setting. Deactivated Agents display Deactivated, Knowledge Base Retained, while Agents in cooldown display Cooldown: N Days Remaining.
Three action icons, followed by the enablement switch, appear from left to right on each row:
Configure Authorized Users
Specify which roles/groups can use the Agent
Clear Knowledge Base
Delete all imported documents (cannot be undone)
Import to Knowledge Base
Open the Agent's dedicated knowledge base to upload documents
Use the search box at the top to search by keyword. You can also filter by status—All / Enabled / Not Enabled / Knowledge Base Retained—or by scenario category.
Enable or Deactivate: Select “Apply Changes” to Take Effect
Changing a switch does not take effect immediately. All changes remain pending until you select Apply Changes at the bottom to submit them together.
Review the Change Summary at the Bottom
A fixed action bar appears at the bottom of the screen. When changes are pending, it shows the number Pending Enablement, the number Pending Deactivation, and the resulting number of Enabled Agents versus the limit. It also reminds you that an Agent cannot be deactivated within 7 days of enablement. The Apply Changes button becomes available at this point.

If an individual item fails after the changes are applied, the screen identifies the reason for each failure, such as reaching the limit, an active cooldown period, or insufficient permissions. Successful changes are unaffected.
Enablement Limit and Cooldown Period
Concurrent Enablement Limit
The Enabled Count at the top of the page shows how many slots are currently used and the maximum allowed. The limit depends on your plan. See Trial and Subscription Plans · Feature Differences.
When the limit is reached, switches for Agents that are not enabled are locked and display Enablement limit reached. Deactivate an Agent or upgrade your plan.
7-day Cooldown Period
Each time an Agent is enabled, it cannot be deactivated for 7 days. During this period, the list displays Cooldown: N Days Remaining, and the switch is locked with the message In cooldown. Can be deactivated in N days.
When You Want to Downgrade Your Plan
If the number of Agents currently enabled exceeds the new plan's limit, the system blocks the plan change. You must first deactivate enough Agents to meet the new plan's limit.
Because deactivation is also subject to the 7-day cooldown period, allow time for the cooldown when planning a downgrade.
What Happens When You Deactivate an Agent
Deactivation does more than hide the Agent. The system removes the assistant along with its conversation channels:
The assistant disappears from the AI Assistants list, and members can no longer chat with it
Its conversation channels, such as Web Chat, and group permissions are removed
Its Agent schedules stop running
Your imported knowledge base is retained, with the status Deactivated, Knowledge Base Retained
If you re-enable it later, the system creates a new assistant based on the latest official blueprint and automatically reconnects the original knowledge base, so you do not need to upload the documents again. However, conversations from before deactivation do not appear under the new assistant.
Configure Authorized Users
Enabling an Agent does not make it available to the entire organization. You must also specify which roles/groups can use it.
Select Configure Authorized Users on the Agent's row. In the drawer, select the roles/groups that can use it, then select Save.
Configured Agents display Authorized: {Role Name} in the list
Agents without authorized users display Not Yet Available

Import to the Dedicated Knowledge Base
You cannot change the role instructions or tools of an official built-in Agent, but you can give it your organization's documents. Every enabled Agent has a dedicated knowledge base.
Select Import to Knowledge Base on the Agent's row to open its knowledge base settings. From there, use it like any other knowledge base: upload documents, create FAQs, and configure tags. See Knowledge Base Overview.
Clear the Knowledge Base
Select Clear Knowledge Base on the Agent's row to delete its imported documents.
This permanently deletes all imported documents and cannot be undone. Before proceeding, make sure the documents are backed up elsewhere.
The outcome depends on the Agent's current status:
Enabled
Only the knowledge base content is deleted. The knowledge base itself remains connected to the Agent, and you can continue importing new documents
Deactivated, Knowledge Base Retained
The entire knowledge base is deleted and disconnected. Re-enabling the Agent later creates a new, empty knowledge base
Connectors: Which Ones You Need to Configure First
Some official built-in Agents must connect to third-party services, such as Google Workspace, Microsoft 365, or Notion, to retrieve data. Cards indicate one of two authorization types:
Administrator Must Configure Connection First
The connector uses organization-level credentials
An organization administrator completes the connection setup before members can use it
No label
Personal user authorization
Each member authorizes their own account in the conversation the first time the connector is used
For more information, see Connectors.
Last updated
Was this helpful?
