Skip to main content

Managing Knowledge for Copilot

Attach and manage Knowledge Sources in Copilot, then verify answers from the target application.

Add the Knowledge Sources your Copilot needs, then check its answers in the application where people use it.
For example, a service desk Copilot can consult a source with approved response targets.


What Is Knowledge in Copilot

Knowledge provides background information that Copilot references during conversations.

Knowledge helps Copilot:

  • Understand business context and rules

  • Deliver accurate and consistent responses

  • Reduce incorrect or overly generic answers

  • Improve relevance within the application context

A Knowledge Source gives Copilot information to answer questions. Configure tools separately when Copilot needs to start a workflow or update a record.


Where Knowledge Is Managed

Knowledge related to Copilot is managed at two levels:

  • Knowledge Sources

    • Define the knowledge content itself

    • Managed centrally under AI Agent → Knowledge Sources

  • Knowledge in Copilot

    • Determines which Knowledge Sources are used by a specific Copilot

    • Configured in the Copilot Knowledge tab


Knowledge Sources and Copilot Knowledge

Copilot does not store knowledge content itself. Instead, it uses existing Knowledge Sources that are created and managed separately.

When adding Knowledge to a Copilot, please note:

  • Use Add knowledge to find and attach an existing Knowledge Source.

  • If the source is missing, create and configure it under AI agent → Knowledge sources in the application settings.

  • A single Knowledge Source can be reused by multiple Copilots or AI Agents

In simple terms:

A Knowledge Source defines the knowledge content itself,
while Knowledge in Copilot defines which Knowledge Sources the Copilot uses.

Creating a Knowledge Source

If the required knowledge does not yet exist, you must create a Knowledge Source before it can be used by a Copilot.

Steps:

  1. Go to Application Management

  2. Open AI Agent

  3. Click Knowledge Sources

  4. Create and configure a new Knowledge Source

Return to Add knowledge after creating the source. Check the selected application in the picker if the source does not appear.

📖 Reference documentation: Knowledge Sources


Accessing the Knowledge Tab in Copilot

To configure Knowledge for a Copilot:

  1. Go to Application Management

  2. Open AI Agent → Copilot Management

  3. Select a Copilot

  4. Switch to the Knowledge tab

All Knowledge used by the Copilot is managed here.


Adding and Managing Knowledge in Copilot

In the Copilot Knowledge tab, administrators can add existing Knowledge Sources to the Copilot.

1. Add steps:

  1. Click Add Knowledge

  2. Select the application if needed and search for the source by name.

  3. Click Add to attach it to the Copilot

  4. Check that the source appears in the Knowledge list and its reference is enabled.

The right side of Select resource shows the Search knowledge field and the Add button for an existing source.

If the required Knowledge Source is not available, create it first under AI Agent → Knowledge Sources.

2: Managing Knowledge Added to Copilot

Each Knowledge added to a Copilot can be managed individually.

From the Knowledge list, administrators can:

  • Enable or disable a Knowledge

  • Click Edit to open Knowledge settings

  • Choose Delete from the row menu to remove this Copilot’s reference to the source.

Only enabled Knowledge is used during Copilot conversations.

3: Editing Knowledge Settings

Open the row menu and select Edit. Choose the default name and description or enter a custom name and description for this Copilot, then click Save.

Name and Description

This section controls how the Knowledge is named and interpreted by Copilot:

  • Use knowledge base default name and description

    • Copilot uses the default name and description from the Knowledge Source

    • Name and Description fields are read-only

    • Recommended when:

      • Consistent naming is required across Copilots

      • The Knowledge Source already clearly describes its purpose

      • The knowledge is standard and reusable

  • Use customized name and description

    • Allows custom Name and Description for this Copilot

    • Name and Description fields become editable

    • Custom values:

      • Affect only Copilot behavior

      • Do not modify the Knowledge Source itself

    • Recommended when:

      • A Knowledge Source is reused across different Copilots

      • Copilots serve different roles or business scenarios

      • Context-specific descriptions improve Copilot accuracy

Copilot knowledge example showing the custom name and description option and the referenced SLA targets knowledge source.

4. Knowledge Source

  • Displays the Knowledge Source referenced by this Knowledge

  • The reference cannot be changed from Copilot

  • Check the new source’s contents and scope first. In the Copilot Knowledge list, remove the old reference and add the new one.


Remove Knowledge

If a Knowledge is no longer needed:

  • Delete it from the Copilot Knowledge list

  • The Knowledge Source remains unchanged

  • Only the association with the Copilot is removed


Scope and Limitations

  • Knowledge applies at the application level

  • Copilot only uses enabled Knowledge

  • Use Test run to check the response, then test in the target application with the intended user accounts. Check who can use Copilot and which records their answers include.

  • Copilot does not modify Knowledge Source content


Maintenance and Best Practices

When business rules or information change:

  • Update the relevant Knowledge Source

  • Disable outdated Knowledge

  • Add new Knowledge Sources when needed

Publish the Copilot configuration change and use Test run. Ask for a response target that changed, compare it with the current policy, and try a question the source does not cover. If an answer uses old information, check that the intended reference is enabled, then inspect the source filters, selected fields, and last sync time if shown. Repeat these checks in the target application with the intended user accounts.

Did this answer your question?