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.
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.
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.