Context Sources and Tools
Choose what a worker can read and what it can call.
Context sources and tool categories are separate controls.
Context decides what the worker can consider. Tools decide what the worker can do. Review both before activating a worker.
Think of sources and tools as the worker's operating boundary. A worker should only see the records it needs and only call actions that are part of its job.
Context Sources
Context sources decide what workspace data can be included in the worker prompt. Available context sources are:
- Tasks.
- Projects.
- CRM.
- Finance.
- Docs.
- Products.
Choose only the sources the worker needs.
More context can improve answers, but it can also expose irrelevant or sensitive data. Start with the smallest useful set and expand after reviewing runs.
Choose context based on the records the worker must understand, not based on the module where the worker is launched. A task-review worker may need projects; a collection-review worker may need finance and CRM; a proposal-review worker may need docs and products.
Tool Categories
Tool categories decide what workspace tools the worker can call. Available categories are:
- Productivity.
- CRM.
- Finance.
- Docs.
- Files.
- Products.
- Scheduling.
- HRM.
- Commerce.
- Workflows.
Grant write-capable tools only when the worker is expected to create or update records. A read-and-summarize worker usually does not need broad tool access.
If a tool could change customer-facing data, create invoices, update CRM records, send files, or affect HRM information, test it with one safe record and keep human review in the process until the output is predictable.
For high-risk areas such as finance, HRM, customer messages, documents, and public pages, prefer draft or review workflows before letting a worker write final records.
How to Choose
Start narrow. A worker that summarizes overdue tasks may need task and project context with productivity tools. It probably does not need finance, HRM, or commerce tools.
Write down the expected inputs and output before selecting sources and tools. If you cannot explain why the worker needs a source or tool category, leave it off for the first version.
Document the intended boundary in the worker instructions. For example, say which records it should review, what it may create, and what it should leave for human approval.
Review Mismatches
If a worker has broad tools but narrow instructions, tighten the tools. If a worker needs data but cannot answer, check whether the required context source is enabled.
Review Routine
After changing sources or tools, run the worker on one safe record and inspect the run output. Confirm it used the intended context and did not attempt actions outside its job.
Review both successful and failed runs. A worker can complete successfully while using too much context, producing vague output, or recommending an action that should stay manual.
Troubleshooting
If the worker cannot answer, add the specific missing context source instead of turning on everything.
If the worker takes unsafe action, pause it and remove tool categories before editing instructions.
Change Review
Every time you add a source or tool:
- Run one controlled test.
- Review the run detail.
- Confirm the worker did not use unrelated context.
- Confirm any created records are correct.
- Decide whether the new access should stay enabled.