Clearer business selection and task assignment in CRM MCP
Scoped connections explain their limits, ambiguous business names require an ID, and guest assignment errors explain project membership.
Product update 1 min read
What changed
MCP refuses an explicit request for a different business instead of silently filing it under a connection's fixed business. When several business names match, it asks for the business ID. An assignment refused because a guest has not joined the project now explains that requirement.
How to use it
- Ask CRM for the business list.
- Select the intended business by ID before creating work.
- Add a guest to the intended project's members before assigning its tasks.
Good to know
A connection authorised for one business cannot access another. Reconnect using the intended account and approve that business. This change does not widen existing permissions.