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 Your Tickets and Customers
Who has access to an AB Support desk's tickets and customers — desk membership follows the Teams channel, signing in on the web doesn't change it, and one desk (or another AB product) can never see another's data.
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.
Teams Channel and Project Linking in AB Projects
How AB Projects links each Microsoft Teams channel one-to-one with a project: the link is made when the tab is added, membership syncs from the channel roster automatically, and comments flow between task and channel thread.
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.
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.
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.