Work arrives in issues, messages and documents. Canopy Connectors let bots and coding agents use those sources through named connected accounts. You decide which accounts they can access and which actions need approval.
Keep work and personal accounts distinct
Create named accounts such as GitHub Work and GitHub Personal. Several accounts can use the same service without sharing their grants. This makes a request specific: read the work issue, summarize the personal project, or use only the account named in the task.
Grant each account to selected bots and workers. A bot grant and a worker grant are separate choices. Start with one account and a read request, then check the available tools before giving it a broader role in your workflow.
Use remote MCP with clear service requirements
Canopy includes connector types for GitHub, Slack, Linear, Notion and Atlassian. Each service has its own authentication requirements. GitHub can use a personal access token or a configured OAuth application. Slack needs an eligible application in your workspace.
Microsoft 365 requires your organization's endpoint and access setup. Google Workspace also needs a chosen remote MCP server. Use Custom MCP for other tools over supported remote transports. A connector label does not guarantee your organization has enabled the external service.
Separate access from approval
A grant answers whether a bot or coding Thread can use an account. Approval rules answer whether a particular action can proceed. A bot can read a permitted issue while still asking before creating a public comment or changing an external record.
Connector credentials remain encrypted in Canopy gateways. Workers and models receive tool descriptions and results, rather than the account tokens. Connected content can still enter model requests, so choose accounts and providers with the data in the task in mind.
Build one complete workflow before adding more tools
Open Settings → Connectors, create an account and complete its sign-in. Test the connection to inspect its tools, then grant access to the intended bot or worker. Try a bounded request that names a real issue or document you can check yourself.
After access changes, a bot refreshes its tools on a following turn. Existing Codex Threads may need a new Thread to see newly added tools. Removing a grant blocks execution even if an old session still lists the tool.