Task permissions & resources
Each scheduled task runs in its own isolated session. It only has access to the resources you explicitly connect to it.
What to connect
When you create a task, connect every resource it needs:
Integrations - If the task needs to read from Stripe, post to Slack, or interact with any external tool, add those integrations when you create the task.
Collections - If the task needs to read or write data in your collections, connect the relevant tables.
Co-worker - Assigning a co-worker gives the task that co-worker's role, personality, and expertise.
Why resources don't inherit
Tasks run in fresh, isolated sessions. They do not have access to your current chat's context, your co-worker's connections, or any other session's data. This is by design for reliability and predictability.
When you create a task, always explicitly list every integration and collection it needs.
Example
A weekly pipeline summary task needs:
Integrations: Slack to post the summary, HubSpot to pull deal data
Collections: Deals table to read pipeline data
Co-worker: Sales Analyst to analyze and format the summary
Without these connections, the task will fail or produce incomplete results.