Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
Assigning Tickets to Your Team
How to assign a support ticket to a teammate so a real team can divide the work, plus how assignment differs from AI-vs-human handling.
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.
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.