Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
Working the Ticket Queue
How to scan, filter, and work the AB Support ticket queue: the inbox row signals, quick filters and sort, saved filters, keyboard triage, and bulk actions.
AB Support Settings
Two things are called settings in AB Support: your personal settings (language, timezone, ticket digest) and a desk's admin-only settings (channels, statuses, knowledge, members and roles), reached from inside the desk.
Support Desks: Your Workspace per Channel
A desk is your AB Support workspace for one Teams channel — its own tickets, customers and settings, independent of AB Projects and AB Sales. Here's how one is created.
AB Support: Overview
AB Support is AI-assisted customer service inside Microsoft Teams — customers reach you by web chat, email, forms, WhatsApp and SMS; tickets land in one queue your team works. The hub for every AB Support help page.
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.
CRM Settings
Everything in the CRM Settings page — automation on/off, the sending mailbox and daily email cap, the Teams notification channel, email templates, and labels. Owner/Admin only.
MCP Tools Reference
Every MCP tool ActionBridge exposes to AI assistants — ab_* tools for AB Projects (tasks, schedule, Documents, task-document links) and ab_crm_* tools for AB Sales (leads, opportunities, activities, email) — plus the built-in slash-command prompts and resources, and how licensing gates writes.
Why AB Projects Requires Microsoft Graph Permissions
Every Microsoft Graph permission AB Projects requests, mapped to the feature it powers: Teams channel linking and roster sync, task cards and comment sync in channels, Outlook calendar scheduling, and Microsoft SSO. Most access is delegated (limited to what you can already do); the Entra ID consent screen is the authoritative list.
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.
SSO and Microsoft Login
AB Projects has no password of its own — you sign in with your Microsoft 365 work or school account through Microsoft Entra ID SSO, in Teams or at blz.actionbridge.io. Any organization can sign in; personal Microsoft accounts cannot (error AADSTS50020). Includes what to check when sign-in fails.
Managing Subscriptions, Billing & Licenses
How AB Projects pricing and licensing work: a free tier (first 10 active users per tenant) and a Basic plan ($3 per active user / month) purchased on Microsoft AppSource — including the activation page, assigning seats in Settings → Manage licenses, subscription status and history, free trials, and exactly what happens when you cancel or reduce seats.
Integration with Microsoft Teams and Adaptive Cards
How AB Projects and Microsoft Teams fit together as one system: the one-to-one channel–project link, the tab, Adaptive Card posts with two-way thread sync, the chip-picker mention model, and Microsoft SSO with channel-driven membership.
Built-in Automation
AB Projects has no if-this-then-that rule builder — the routine work is automated out of the box: status-driven progress, subtask roll-up, automatic Teams cards (tunable per event type per project), channel-driven membership sync, digests and reminders, and AI assists.
Commenting with Mentions in Channels
How task comments sync with the Microsoft Teams thread — comments always post to the channel; thread replies sync back to the task only when the reply @mentions AB Projects — and how the Mention in Teams notification picker controls who gets pinged.
Installing the AB Projects Teams App
How to install AB Projects in Microsoft Teams: add the app from the Teams app store or Microsoft Marketplace, then add the channel tab to link a channel to a project — with automatic Microsoft 365 sign-in, project types, the included bot, and licensing basics.
Managing Project Settings
A tour of the AB Projects project settings page: identity, members, Teams channel notification toggles, GitHub integration, task workflow options, the Teams link, ownership transfer, leaving, and the unlink-before-delete rule.
Role-Based Access Control
The four project roles in AB Projects — Owner, Admin, Member, and Viewer — what each can do, how roles are changed, the guardrails around ownership and the last Admin, and how the read-only Viewer role differs from having no license seat.
Adding or Removing Members
How people join and leave an AB Projects project: the linked Teams channel is the roster — auto-sync adds the whole channel, the Team page invite covers stragglers, and removing someone for good means removing them from the channel too.
Understanding Projects and Teams
What a project is in AB Projects: a shared workspace of tasks, wiki, and documents tied one-to-one to a Microsoft Teams channel, with membership synced from the channel and four roles — Owner, Admin, Member, and Viewer.