Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
Who Can See What? (AB Sales)
Visibility in AB Sales is workspace-based: every workspace member sees that workspace's whole pipeline, each workspace's data is isolated, and roles (Owner/Admin/Member) control management, not visibility.
MCP Tools Reference
All 40 MCP tools ActionBridge gives AI assistants — ab_* for AB Projects (tasks, schedule, Documents) and ab_crm_* for AB Sales (leads, opportunities, activities, email) — plus the slash-command prompts, resource feeds, which tools need a license, and which writes post a Microsoft Teams card.
I Can't See My Tasks
Tasks not showing in AB Projects? It's almost always a remembered filter, the wrong project or view (Gantt needs dates), or Teams-channel membership that hasn't synced — and if you can see tasks but not create them, it's a license seat, not a bug.
Who Can See What?
Visibility in AB Projects is decided by project membership: every member sees all of the project's tasks, comments, subtasks, and history. Roles (Owner/Admin/Member/Viewer) control what you can change, not what you can see — there are no private tasks. To hide work, use a separate channel and project.
Confidentiality and Enterprise Agreements
Confidentiality in AB Projects is done by Teams channel scoping, not per-task privacy: people outside the channel aren't project members and see nothing. There is no private-task flag, NDA workflow, watermarking, or access expiration — NDAs, data-processing terms, and private commercial arrangements are handled through Enterprise agreements.