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.
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.
Confidentiality and Enterprise Agreements
Confidentiality in AB Projects is done by Teams channel scoping, not per-task privacy: people outside the channel aren't project members and see nothing. There is no private-task flag, NDA workflow, watermarking, or access expiration — NDAs, data-processing terms, and private commercial arrangements are handled through Enterprise agreements.
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.