Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
Why AB Projects Requires Microsoft Graph Permissions
The Microsoft Graph API permissions AB Projects uses and why — covering Teams channel linking and roster sync, posting task activity and syncing thread replies, Outlook calendar scheduling, and Microsoft SSO. The Entra app registration / consent screen is the authoritative list.
Who Can See What?
Visibility in AB Projects is membership-based: every project member sees all of the project's tasks, comments, subtasks, and history. Roles (Owner/Admin/Member) control management, not visibility — there is no private-task or read-only tier. Confidentiality is done via separate channels.
Confidentiality and Enterprise Agreements
How confidentiality works in AB Projects: access is scoped by Teams channel membership and Microsoft identity, with a full audit trail. There is no per-task privacy flag, NDA workflow, watermarking, or access expiration; NDAs and private terms are handled via Enterprise agreements.
Data Retention and Export
How AB Projects retains data on Microsoft Azure: deletes are soft-deletes (no auto-purge, no self-serve restore window), change history and comments are preserved, and there is no built-in export yet — data export and recovery are handled as manual support requests.
SSO and Microsoft Login
AB Projects uses Microsoft SSO (Microsoft Entra ID) for password-free sign-in with your Microsoft 365 account. No separate password and no per-user license to assign; project access follows your Teams-channel membership.