Scopes: partitions inside a workspace

A scope is a partition inside your workspace. It lets you keep some knowledge and conversations apart: one team's material from another's, one campaign's from the rest, or training material from customer-facing content.

What can be scoped?

Sources (your knowledge), conversations and voice exemplars. Anything without a scope is workspace-wide and visible everywhere in the workspace.

What kinds of scope are there?

When you create a scope you choose a type that describes what it partitions:

• Account: material about one customer account;
• Audience: material for one audience, such as partners;
• Campaign: material for one campaign;
• Activity: material for one kind of activity;
• Training: material for internal training;
• Custom: anything else.

The type is a label to help you organise; every type works the same way.

How do scopes affect answers?

When the brain answers within a scope, it can use:

• workspace-wide knowledge, plus
• knowledge in the selected scopes,

and nothing from other scopes. The separation is enforced by the database, not just by the screen.

How do I use them?

1. Create scopes in Operations → Scopes.
2. Put knowledge into a scope when you import it in bulk (a scope for the whole batch, or per file).
3. Give a role surface the scopes its agents should draw on.
4. On screens that support it, such as Sources, Conversations and Workflows, use the scope filter to see one partition at a time.

What happens if I delete a scope?

It's deactivated rather than erased, so nothing it contained is lost.

Do I need scopes?

Most workspaces don't, at first. Start without them; add scopes when you find you need to keep material apart, for example when a partner team or a single large account needs its own knowledge.

How is this different from a separate workspace?

A scope lives inside one workspace: same agents, same settings, same administrators, with some knowledge kept apart. A separate workspace has its own everything. Use scopes for partitions within a team, and separate workspaces for separate organisations.