Skip to main content
Scoping tells an agent which objects and pages to focus on. Two settings on the agent drive scope:
  • Scoped objects: the objects the agent should prefer when answering.
  • Scoped pages: the documents and pages the agent should prefer.
Leave either setting empty for no specific focus. Leave both empty for a workspace-wide agent with no focus at all.

​
How scope works

Scope is a soft focus hint, not a hard access barrier:
  1. The agent is told to prefer the listed objects and pages when answering.
  2. It may still reference other workspace data when the request clearly calls for it, so generic questions are not refused.
  3. Scope does not block any tools. Which tools an agent can use is controlled separately (see Tool gating).
Hard scope enforcement (blocking the agent from anything outside the focus areas) was deliberately avoided. It caused the agent to refuse ordinary questions. Scope nudges the agent toward the right data rather than fencing it in.

​
When to scope

  • A “Sales Coach” agent focused on the deals object stays on-topic and is less likely to wander into unrelated records.
  • A “Support Triage” agent focused on the conversations object plus the help-center pages answers “how do I” questions and routes incoming tickets without being steered toward unrelated data.
  • A “Workspace Admin” agent left unscoped (workspace-wide) can blueprint new objects and refactor schemas.

​
What scope does not do

  • It does not change your permissions. The agent can never surface anything you couldn’t already access on your own.
  • It does not hard-block access to other objects or pages. It only biases the agent toward the focus areas.
  • It does not restrict conversation topics. The agent is free to discuss anything you ask.