When to use Tools, Agents, or Knowledge Bases

There are several ways to train Copilot on a given piece of information to improve your outputs.

Should it be a Knowledge base (and, if so, at the Workspace or Project level?), a Tool, or an Agent?

This help doc will help you decide!

Knowledge Bases

You might get the most benefit from providing information as a Knowledge Base when it's a single, discrete document that you don't want to interact with and just want to be silently integrated into your outputs.

For example, a brand guide is something you rarely want to have a conversation with, you just want to ensure your users' outputs respect it even if it's not top-of-mind at the moment they're using Copilot.

Workspace vs Project Knowledge Bases

Next, you need to decide whether something should be added to the Workspace or Project layer. At the Workspace level, any Project in that Workspace will be able to use it. Conversely, at the Project level, it only exists within the context of that Project. The the decision is as simple as "Is this relevant to many Projects or just one?"

Tools

You might want to talk to us about creating a Custom Tool for you when the information is a resource, database, feed, or other collection of data that changes over time.

For example, there might be a news feed specific to your industry that Copilot could read and integrate into your outputs.

Agents

You might want to talk to us about creating a Custom Agent for you when you want a role to be performed that you can ask questions of, converse with, or otherwise perform a function.

For example, you might have a very specific set of PR values and insights and it would be beneficial if an Agent could be an advocate for those values and insights within Copilot.