How to train Assist 2.0: Knowledge or Agents?

There are a couple of ways to train Assist 2.0 on a given piece of information to improve your outputs.

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

This help doc will help you decide!

Knowledge

You might get the most benefit from providing information as Knowledge when it's a single, discrete document that you don't want to interact with directly — you just want it 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 outputs respect it, even if it's not top-of-mind at the moment you're using Assist 2.0.

Organisation, Workspace, or Project Knowledge?

Next, you need to decide which layer Knowledge should sit at. Assist 2.0 has three:

• Organisation level — available to every Workspace and Project in your Organisation.
• Workspace level — available to every Project within that Workspace.
• Project level — only available within that specific Project.

The decision is as simple as "How widely is this relevant?" If it applies everywhere (e.g. company-wide brand guidelines), put it at the Organisation level. If it's specific to a team or function, Workspace. If it only matters for one piece of work, Project.

Agents

You might want to talk to us about creating a Custom Agent when you want a role to be performed — something you can ask questions of, converse with, or have perform a specific function.

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