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.
Sending Email from AB Sales
How AB Sales sends email — in plain terms. It sends from your own company mailbox through Microsoft 365, set up once by your admin. Covers the sending identity, choosing a mailbox, templates, campaigns, AI-drafted replies, and deliverability.
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.
Data Retention and Export
How AB Projects retains data: nothing is purged on a timer, change history and comments are preserved, and deleting a task is permanent — there is no recycle bin. Data is hosted on Microsoft Azure (Japan East). No self-serve export yet; exports and account-data deletion are handled by support on request.
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.