Agent Builder - Advanced Configuration¶
Advanced features and power-user settings for fine-tuning your AI agent.
Overview¶
This guide covers advanced configurations for power users who want to enhance their agent with:
- Dynamic behavior based on user context
- Custom personality traits
- Voice processing capabilities
- External tool integrations
- Advanced analytics and quality monitoring
For basic agent setup, see Agent Builder - Basic Configuration.
Advanced Configuration Sections¶
- Pre Processors and Tags - Dynamic tagging and pre-processing
- Instructions (Advanced) - Conditional instructions, special instructions, current message prompt
- Agent Parameters - Dynamic variables for instructions
- Prompt Shortcuts - Quick actions for users
- Personality Traits - Agent personality configuration
- Documentation - User-facing agent documentation
- Behavior - Advanced behavior settings
- Audio and Speech - Voice processing configuration
- Context - Advanced context management
- Tools - External integrations and capabilities
- Post Processors - Response analysis and evaluation
1. Pre Processors and Tags¶

When to use
Use pre processors when you need dynamic agent behavior based on user authentication, location, subscription status, or any runtime context. Essential for personalized agent experiences.
Overview¶
Pre Processors execute JavaScript code before the user query is sent to the LLM. They can dynamically set tags based on user context, authentication status, session data, or any custom logic.
Pre Processors and Tags configuration
How Pre Processors Work¶
Workflow: 1. User sends a message 2. Pre Processor executes (JavaScript snippet) 3. Pre Processor returns tags based on logic 4. Tags determine agent behavior, shortcuts visibility, tool availability 5. Query is sent to LLM with tag context
Adding Pre Processors¶
Pre Processor added to agent with tag configuration
Steps:
- Configure Pre Processor in Settings (see Settings > Processors)
- Click "Add" button in Pre Processors section
- Select configured pre processor from list
- Configure tags returned by the pre processor
Use Case Example: Authentication-Based Behavior¶
Use Case
Show different shortcuts and features based on whether the user is logged in or anonymous.
Pre Processor Logic:
// preprocessor example
const subscriberid = ld.get(data, 'user_data.subscriberid', null);
if (subscriberid !== "") {
ctx.addTag('authenticated');
} else {
ctx.addTag('unauthenticated');
}
Tag Configuration:
- Tag:
authenticated→ Shows "View My Account", "Order History" shortcuts - Tag:
unauthenticated→ Shows "Sign Up", "Learn More" shortcuts
Benefits:
- Dynamic agent behavior based on user state
- Personalized experience
- Controlled feature access
2. Instructions (Advanced)¶
When to use
Use these advanced instruction features when you need conditional behavior based on tags, role-based special instructions, or per-message prompt manipulation. For basic Initial Message and Agent Instructions, see Builder — Basic Configuration.
Overview¶
The Instructions section in Agent Settings provides advanced instruction management beyond the basic Agent Instructions and Initial Message.

Available User Data
You can access user information in your prompts using {{data.userInformation.email}}, {{data.userInformation.name}}, and {{data.userInformation.id}} to personalize responses. This information is available for logged-in users in Web App and Sidebar modality. For dynamic user data parameters, use {{data.keyname}} syntax.
Special Instructions¶
Special / Additional instructions to be used in the agent. These are typically set by the Co-Admin role but can also be set by Owner, Admin, Workspace Admin, and Co-Admin.
Use {special_instructions} as a placeholder in your Agent Instructions to control where special instructions are inserted.
Each Special Instructions field supports Conditional Instructions (see below).
Current Message Prompt¶
A secondary mechanism to steer the agent's responses. The Current Message Prompt allows you to append or prepend instructions to each user prompt message.
- To create a dynamic prompt, use
{message}as a placeholder in your text - If
{message}is not included, the current message will be appended at the end automatically
When to use
Use this when language models do not pay enough attention to the system prompt, or when attention to system prompt instructions fades over long conversations. This is a fallback mechanism — try the system prompt alone first.
Each Current Message Prompt field supports Conditional Instructions (see below).
Conditional Instructions¶
Conditional Instructions allow you to apply different instruction blocks based on tag criteria. For example, a separate instruction can be applied when the user is "Authenticated" vs. "Unauthenticated."
Conditional Instructions apply to Agent Instructions, Special Instructions, and Current Message Prompt.
Key Features:
- Tag-based conditional instruction blocks
- Support for common instructions preceding conditional blocks — reducing redundancy
- Backward compatible with existing instruction sets
- Use the "Insert Condition" button to add a condition block
- Use the "Verify" button to validate the condition syntax
End of Conversation Message¶
When enabled, this message is sent exactly as written when the conversation ends due to system idle timeout. The system injects an internal user turn with the tag internal_end_of_conversation, allowing the agent to perform final actions.
| Field | Description |
|---|---|
| Enable checkbox | Turn the feature on/off |
| Message text | The exact message sent when conversation ends (e.g., "Thank you for chatting with me. Have a great day!") |
Permission
Access to the End of Conversation Message setting is RBAC-controlled and provided to the Admin role by default.
Add Instruction¶
Click "Add Instruction" to add additional instruction blocks. This allows multiple instruction sets to be configured for the same agent.
3. Agent Parameters¶

When to use
Use agent parameters when you need reusable templates or want to easily update values (like company name, support hours, contact info) without modifying core instructions.
Overview¶
Agent Parameters are dynamic variables that can be used within agent instructions using {botParams.<key>} syntax.
Agent Parameters configuration
How to Use¶
Step 1: Define Parameters
Add key-value pairs in the Agent Parameters section:
company_name: fifthelement.ai
product_name: AI Agent Platform
support_hours: 9 AM - 6 PM EST
support_email: support@fifthelement.ai
documentation_url: https://docs.fifthelement.ai
Step 2: Reference in Instructions
Use parameters in your instructions:
You are a support agent for {botParams.company_name}.
Our product, {botParams.product_name}, is an enterprise AI platform.
If users need help:
- Support hours: {botParams.support_hours}
- Email: {botParams.support_email}
- Documentation: {botParams.documentation_url}
Benefits: - Easy updates without touching instructions - Reusable agent templates - Multi-environment configuration (dev, staging, prod)
4. Prompt Shortcuts¶
When to use
Use shortcuts for common tasks, frequently asked questions, or guided workflows. They improve user experience by reducing typing and providing clear action paths.
Overview¶
Prompt Shortcuts are predefined prompts or questions displayed as buttons in the end-user chat interface. By assigning a short label and an actual prompt for each button, Agent admins can expedite interactions and steer users through conversations with pre-made options.
Only the label is visible to the end user — not the prompt behind it.

Shortcut Configuration Fields¶

| Field | Required | Description |
|---|---|---|
| Label | Yes | Brief text displayed on the button in the chat interface. Should be concise and indicate what to expect |
| Prompt / Hyperlink | Yes | The actual prompt sent to the agent when clicked. If "Shortcut is Hyperlink" is enabled, this becomes a URL that opens in a new tab |
| Add Tag (one-off) | No | A tag offered by the shortcut when it is used. Useful for tracking which shortcuts users click |
| Shortcut is Hyperlink | No | When checked, the shortcut opens the URL in a new tab instead of sending a prompt |
| Use Chat History | No | Include conversation history when using this shortcut, making the agent context-aware of past exchanges |
| Tool to use for this shortcut | No | Assign a predefined tool from Settings > Tools to be used when this shortcut is triggered |
When to Display This Prompt¶
Control when each shortcut is visible to users:
| Option | Description |
|---|---|
| Always | Shortcut is always shown in the chat |
| Show when Tag is present | Shortcut is only visible when a specific tag (from a pre-processor) is active on the session |
| Hide when Tag is present | Shortcut is hidden when a specific tag is active — shown otherwise |
| Conditional with LLM (Deprecated) | LLM decides whether to show the shortcut based on a condition prompt. This option is deprecated and will be removed in a future release |
Use Case
Show different shortcuts based on user authentication status. Use a pre-processor to set authenticated / unauthenticated tags, then:
- "View My Account" → Show when Tag is present:
authenticated - "Sign Up for Free" → Hide when Tag is present:
authenticated
Static Context for Shortcuts¶
When a static context is provided for a shortcut, it overrides the agent's configured context. The response will be based solely on the static context provided with the shortcut.
User Defined Shortcuts¶
End users can create their own shortcuts for messages they use frequently. This feature must be enabled by the Agent admin.
How end users create shortcuts:
- Within the chat interface, hover over or select a message from chat history
- A + icon appears on the right side of the message
- Click or tap and hold the icon to create a shortcut
- The agent auto-generates a short label based on the message
- The shortcut appears at the end of the chat area
Managing User Shortcuts:
- Edit: Click and hold the shortcut to edit the label inline
- Delete: Click the trash can icon that appears when editing
- Mobile: Long press on a message to create a shortcut
Enable this feature
Navigate to Agent Settings to enable User Defined Shortcuts. If the + icon does not appear, check that this feature is enabled.
AI-Generated Prompt Shortcuts¶
After each agent response, the system can analyze conversation context and automatically generate relevant follow-up suggestion buttons alongside static shortcuts.
Configuration (under Prompt Shortcuts):
| Setting | Description |
|---|---|
| Allow/Disallow | Enable or disable AI shortcut generation |
| Quantity | Number of AI-generated shortcuts to display per response (1 to 5) |
| AI Shortcut Generation Template | Customize the system prompt that defines how the AI anticipates user needs |
Available Template Variables:
| Variable | Description |
|---|---|
{{count}} | Number of shortcuts to generate |
{{bot_last_message}} | Agent's most recent message |
{{user_instructions}} | User memory/preferences |
Initial Session Tagging¶
A system-level tag internal_no_message is automatically applied at conversation start and removed on the first user message. This can be used to trigger initial prompt shortcuts before a user has typed anything — for example, displaying a welcome menu of options.
5. Personality Traits¶

When to use
Use personality traits when you want to fine-tune your agent's conversational style beyond basic instructions. Ideal for brand-aligned communication or specific audience personas.
Overview¶
Personality Traits allow you to fine-tune your agent's conversational style and tone. Select up to 5 traits from various personality dimensions.
Personality Traits configuration with multiple trait dimensions
Available Traits¶
Each dimension has three options: Left Extreme, None (Neutral), Right Extreme
| Dimension | Left | None | Right |
|---|---|---|---|
| Humor | Funny | None | Serious |
| Confidence | Modest | None | Arrogant |
| Emotion | Happy | None | Sad |
| Risk-Taking | Adventurous | None | Cautious |
| Cooperation | Agreeable | None | Disagreeable |
| Ambition | Ambitious | None | Content |
| Assertiveness | Confident | None | Insecure |
| Certainty | Decisive | None | Indecisive |
| Empathy | Empathetic | None | Apathetic |
| Sociability | Extroverted | None | Introversion |
| Formality | Formal | None | Informal |
| Independence | Independent | None | Dependent |
| Optimism | Optimistic | None | Pessimistic |
| Playfulness | Playful | None | Serious |
| Creativity | Creative | None | Conventional |
| Spontaneity | Spontaneous | None | Predictable |
| Dominance | Dominant | None | Submissive |
| Open-Mindedness | Open minded | None | Closed minded |
| Detail Orientation | Brief | None | Detailed |
| Encouragement | Encouraging | None | Critical |
| Energy Level | Energetic | None | Calm |
Example Configurations¶
Use Cases
Customer Support Agent: - Empathetic, Formal, Detailed, Encouraging, Calm
Marketing Content Agent: - Creative, Energetic, Optimistic, Playful, Confident
Technical Documentation Agent: - Detailed, Formal, Decisive, Independent, Predictable
Maximum 5 traits can be selected to avoid conflicting personalities.
6. Documentation¶

When to use
Add user-facing documentation when deploying agents in Web App or Sidebar modalities. Helps users understand agent capabilities and how to get the best results.
Overview¶
The Documentation section allows you to create user-facing information about your agent. This content is displayed when users open the agent in Web App modality via the "How to use this agent - Quick Guide" button.
Documentation configuration with rich text editor
Documentation shown to users in Web App modality
What to Include¶
User Documentation Label: - Title displayed above the documentation - Example: "Quick Start Guide", "Agent Capabilities", "How to Use"
User Documentation (Rich Text):
Recommended Content:
1. Agent Purpose:
This agent helps you find information about our products,
troubleshoot common issues, and connect with support.
2. What It Can Do:
✓ Answer product questions
✓ Provide troubleshooting steps
✓ Search documentation
✓ Escalate to human agents
3. How It Works:
1. Ask your question in natural language
2. The agent will search our knowledge base
3. Receive instant answers with source links
4. Use shortcuts for common tasks
4. Best Practices:
• Be specific in your questions
• Use shortcuts for faster results
• Provide error messages when troubleshooting
• Rate responses to help improve the agent
5. Limitations:
This agent cannot:
- Process refunds (contact support@company.com)
- Modify account settings directly
- Provide pricing quotes (contact sales)
Welcome Screen HTML¶
Replaces the previous blank state shown on a new chat with a configurable Welcome Screen. Admins author the landing experience for an agent — a greeting, a short description of the agent's purpose, documentation, suggested starter questions, or anything else they want users to see first. Applies to Web App and Sidebar modalities. Other modalities (Floating Embed Widget, etc.) are unaffected.
Documentation section with the Welcome Screen HTML field alongside User Documentation Label and User Documentation — Preview, Use template, and Generate with AI affordances are exposed directly on the field
Configuration¶
The Welcome Screen HTML field sits inside the Documentation section of Agent Settings, alongside the existing User Documentation Label and User Documentation fields. Admins author arbitrary HTML — without being constrained to a fixed tile layout.
| Field | Description |
|---|---|
| Welcome Screen HTML | Arbitrary HTML rendered as the initial state of a new chat on Web App and Sidebar. Empty value preserves the existing default empty state |
The ? icon next to the field documents allowed tags and provides sample code.
Permissions
Welcome Screen HTML lives inside the Documentation section and is editable by Admins plus any role granted access to that section via RBAC.
Author Affordances¶
| Control | Behavior |
|---|---|
| Preview / Edit toggle | Flip between the raw HTML editor and a live rendered preview of the Welcome Screen without leaving the page or saving |
| Use template | Inserts a working starter HTML template into the field as a starting point for further edits |
| Generate with AI | Opens the Generate welcome screen modal with a "What should the welcome screen emphasize?" prompt. Describe the desired tone or focus (e.g., "Use applicable emojis to make the welcome screen welcoming."), click Generate, and the AI writes the full Welcome Screen HTML into the field. Cancel closes the modal with no change |
| Revert | Restores the previously saved Welcome Screen HTML — useful if a Generate-with-AI run or manual edit needs to be discarded |
| Character count | Live count displayed in the bottom-right of the field |
Preview mode renders the authored HTML — greeting, agent purpose, and clickable starter questions appear exactly as the end user will see them. The ← Edit link returns to the raw HTML editor
Generate welcome screen modal — describe what the welcome screen should emphasize, click Generate, and the AI writes the full HTML into the field
End-User Experience¶
- Saved Welcome Screen HTML renders as the initial state of every new chat on the Web App and Sidebar modalities, above the message input.
- Any clickable links or starter questions authored in the HTML behave as the admin defined them — for example, underlined sample questions that submit on click.
- Leaving the field empty preserves the existing default empty state — no regression for agents that don't configure this.
Welcome Screen as the initial empty state of a new chat — Web App (left) and Sidebar (right). Clickable starter questions submit on click; the message input remains active below
7. Behavior¶
When to use
Configure behavior settings to fine-tune debugging, cost display, feedback, conversation encryption, analytics, and more.
Overview¶
The Behavior section contains toggles and settings that control how your agent interacts with users, handles data, and integrates with external systems.

Debug Permission
User must have debug permission to enable "Set Custom Data" for testing userData on Web App.
Debug and Development¶
| Setting | Description |
|---|---|
| Show Context Sent to API for Debugging | Displays context sent to the API in the chat window. User must have debug permission to enable debug mode |
| Verbose Tool Calls | Displays tool execution details in the chat interface |
| Request Debug Logs | Enables request debug logs for the agent |
| Display Thinking Content | Displays the AI model's reasoning process in a collapsible section within the chat interface |
Language Model Control¶
| Setting | Description |
|---|---|
| Prioritize User Selected Language Model | When checked, the user-selected model takes priority over tag-based language model selection |
| User to Change Language Model | Allows users to switch language models. Applicable only for Web App and Sidebar modalities |
User Experience¶
| Setting | Description |
|---|---|
| Display Session Cost | Shows the estimated cost of each user session based on API usage |
| Include Tokens in Price Info | Shows token count for the session. Requires Display Session Cost to be enabled |
| Display Chat Progress | Displays a visual indicator to users while the agent is generating a response |
| Display Chat Reaction | Adds like/dislike buttons for users to provide feedback on responses |
| Enforce Retrieval Tool Use | Forces knowledge base consultation. Works only when a single retrieval tool can be qualified for the user query |
User Capabilities¶
| Setting | Description |
|---|---|
| Allow User Defined Instructions | Allows users to define their own instructions for the agent. Not applicable to Widget modality. Requires {{user_instructions}} placeholder in agent instructions |
| Conversation Download | Allows users to download conversation transcripts as a PDF |
| Chat Attachments | Allows users to attach image(s) and PDF(s) to a message for real-time analysis. A paperclip icon appears in the chat prompt |
| Upload to Repositories | Allows users to upload AI-generated responses as documents to repositories they have write access to |
When Upload to Repositories is enabled:
- Configure Allowed Repositories for AI Response Upload — select one or more repositories where users can upload AI responses
- Only repositories where users have write access will be available at runtime
Context and Title Generation¶
| Setting | Description |
|---|---|
| Generate and Display Title for the Context | Automatically generates and displays a title for the context being worked on |
| Dynamic Title Prefix | A specified prefix added before the automatically generated title |
| Context Token Limit for Dynamic Title Generation | Limits the context sent for title generation to the specified token count |
Conversation Management¶
| Setting | Description |
|---|---|
| Conversation Filters | Select filters to display in the conversations view dropdown. Uses whitelist logic — only explicitly selected filters are shown. System filters (Flagged, Flagged + Resolved, Unresolved, Like, Dislike, Dislike+Feedback) are always available |
| WebApp Footer Message | Footer message displayed on the web app (e.g., "AI can make mistakes, double check responses"). Left blank = not displayed |
| Conversation Inactivity Duration | Duration of user inactivity, in minutes, after which Conversation Post-Processor(s) are triggered. The conversation itself stays open — the user can resume it at any time, and post-processors re-run on each subsequent inactivity cycle. Default: 60 minutes. See Continuous Conversations |
Security and Encryption¶
Encrypt Conversation:
When enabled, only users who participated in the conversation can see messages in clear text. Supervisors monitoring conversations will see encrypted values.
| Encryption Type | Description |
|---|---|
| Encrypt PII | Only PII data in messages will be encrypted |
| Encrypt Message | The entire message will be encrypted |
Analytics¶
GTM Id (Google Tag Manager Id):
Enter a GTM ID to enable analytics data transmission and website insights. This tracks agent events like widget open, message sent, AI response received, new conversation created, and sharing of conversation transcripts.
Email Notifications¶
Prerequisite
Both notification options are only visible and configurable if SMTP is configured for the workspace.
| Setting | Description |
|---|---|
| Notification for Conversation Flags | Get notified when users flag conversations for review. Configure email recipients who receive alerts |
| Notification for Message Dislikes | Receive notifications when users provide negative feedback (dislikes) on messages. Only visible if Display Chat Reaction is enabled. Configure email recipients |
Administrators can customize notification email templates from Settings > Email Settings > Create Email Template for both "Conversation Flag" and "Message Dislike" notifications. Placeholders for dynamic content (conversation ID, user comment, disliked message text) are available.
8. Audio and Speech¶

When to use
Configure voice processing when deploying agents for telephone support (SIP) or web-based voice interactions (WebSocket). Essential for call center automation and voice-enabled customer support.
Overview¶
Configure real-time voice processing capabilities for your agent, enabling voice interactions via SIP (telephony) or WebSocket (web-based).
Audio and Speech configuration section
Configuring audio and speech settings
Realtime Voice Processing¶
Enable Realtime Voice Processing:
Once enabled, you can configure:
SIP Realtime Voice Processing:
When to use
Use for telephone/SIP integration, inbound/outbound call handling, and voice-based customer support.
- For telephone/SIP integration
- Inbound/outbound call handling
Websocket Realtime Voice Processing:
When to use
Use for browser-based voice chat, web applications requiring real-time voice responses.
- For web-based voice interactions
- Browser-based voice chat
Enable SIP or Websocket realtime voice processing
Configuration Details¶
Refer to on-screen documentation for detailed configuration of: - Audio codecs - Voice models (ASR/TTS) - Latency settings - Call routing - Interruption handling
9. Context¶

When to use
Add context when your agent needs to reference specific information: documents, knowledge bases, product data, or company policies. Essential for RAG (Retrieval-Augmented Generation) use cases.
Overview¶
The Context section allows you to add information that your agent can reference when generating responses. Context can be provided as text, documents, or knowledge repositories.
Context configuration with Text, Document, and Knowledge Repository tabs
Context Types¶
Text:
When to use
Use for quick facts, guidelines, policies, or small amounts of structured data that don't change frequently.
- Direct text input
- Token count displayed
- Example: Product specifications, company policies
Document:
When to use
Use for user manuals, technical documentation, or any existing documents your agent should reference.
- Upload documents (PDF, DOCX, TXT, etc.)
- Processed and embedded for retrieval
- Example: User manuals, technical documentation
Knowledge Repository:
When to use
Use for large-scale knowledge bases, full documentation sites, FAQs, or extensive support articles.
- Connect to pre-configured knowledge bases
- Vector search enabled
- Example: Full documentation sites, FAQs, support articles
Context Options¶
Limit Context Token:
- Restrict context size to prevent exceeding model limits
- Recommended for cost control
Allow User Provided Context:
When to use
Enable when users need to upload their own documents for analysis or personalized assistance.
- Let users upload documents per session
- Use Case: Custom document analysis
Important: Add 'Context Tool' under the 'Tools' section to enable context usage.
10. Tools¶

When to use
Add tools to extend your agent's capabilities beyond conversation: retrieving knowledge, calling APIs, escalating to humans, or executing custom logic.
Overview¶
Tools extend your agent's capabilities beyond conversation, enabling it to retrieve data, perform actions, and integrate with external systems.
Tools configuration section
Adding tools to the agent
Adding Tools¶
Steps:
- Click "Add" button in Tools section
- Select a tool from available options:
- Knowledge Retrieval - RAG: Access knowledge bases
- Transfer to Human: Escalate to human agents
- API Integration: Call external APIs
- Context Tool: Use context from Context section
- Custom Tools: JavaScript-based custom tools
- Configure tool settings:
- Scope Limiting: Set tags to control when tool is used
- Instructions: Add guidance for tool usage
- Parameters: Configure tool-specific settings
Tool Configuration Options¶
Scope Limiting (Tag-Based):
When to use
Use tag-based scope limiting to control tool availability based on user authentication, subscription tier, or any custom condition.
- Control tool availability based on tags
- Example: "Transfer to Human" only for tag
needs_escalation
Tool Instructions:
- Provide specific guidance on how/when to use the tool
- Example: "Use this tool when user asks for order status"
11. Post Processors¶

When to use
Use post processors for quality assurance, compliance checking, sentiment analysis, conversation summarization, or post-conversation analytics.
Overview¶
Post Processors analyze agent responses by sending them to an LLM for evaluation, quality checks, or additional processing.
Post Processors configuration
Types of Post Processors¶
Turn Post Processor:
When to use
Use for real-time quality monitoring, sentiment analysis per response, compliance checking, or immediate flagging of issues.
- Executes after each user-agent exchange
- Analyzes individual responses in real-time
Use Cases: - Sentiment analysis per response - Compliance checking - Quality scoring - Real-time flagging
Conversation Post Processor:
When to use
Use for overall conversation summaries, CSAT prediction, conversation categorization, or generating post-conversation follow-up tasks.
- Executes after the entire conversation ends
- Triggered when conversation expires (after Conversation Inactivity Duration)
Use Cases: - Overall conversation summary - CSAT prediction - Conversation categorization - Post-conversation analytics
Configuration¶
Steps:
- Configure Post Processors in Settings (see Settings > Processors)
- In Agent Builder, navigate to Post Processors section
- Click "Add" to select configured post processors
- Choose processor type:
- Turn Post Processor
- Conversation Post Processor
- Save configuration
Summary¶
You've now configured advanced features for your AI agent:
- Dynamic behavior with Pre Processors
- Conditional and special instructions
- Reusable parameters
- User-friendly shortcuts with conditional visibility
- Custom personality
- User documentation
- Advanced behavior settings
- Voice capabilities
- Knowledge context
- External tool integrations
- Quality monitoring with post processors
Don't forget to click "Save" to apply all configurations!
Related Topics¶
- Agent Builder - Basic Configuration - Essential setup steps
- Agent Reports - Monitor agent performance and analytics
- Agent's Look & Feel - Customize branding and appearance
- Cloning an Agent - Duplicate and modify existing agents
- Version Control - Manage agent versions and rollback
- Knowledge Overview - Configure knowledge bases for RAG
- Settings > AI Models - Manage available language models
- Settings > Processors - Configure pre/post processors