Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
Task Dependencies: Blocked By and Blocks
How task dependencies work in AB Projects: add predecessors from the task that is waiting, read the automatic Blocks mirror, understand why an unmet predecessor warns rather than blocks, and how an AI assistant can set dependencies over MCP.
Your Personal Settings
Your personal AB Support settings — profile, language, timezone, and the opt-in ticket digest email — how they differ from a desk's admin-only settings, and why the digest has its own Save button.
The AB Support Dashboard
A desk opens on an interactive dashboard — in Teams or the web app. Its metric tiles are clickable and open the ticket list filtered to exactly those tickets. Which tiles click through, which don't, and how to read the numbers.
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 (members, channels, statuses, knowledge sources), reached from the gear inside the desk.
CRM Settings
Everything in the CRM Settings page — automation on/off, the sending mailbox and daily email cap, the Teams notification channel, and labels. Templates and campaigns now live on the Agents tab. Owner/Admin only.
Becoming a Project Member in AB Projects
How you become a member of an AB Projects project: being in the linked Teams channel is the only requirement — the roster sync adds you as a Member automatically, and there is a checklist for names missing from the assignee or mention picker.
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.
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.
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.
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.