幫助 & 支援
尋找指南、技巧和常見問題解答，充分利用AB。按主題瀏覽或搜尋您需要的內容。
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.
Managing Project Settings
Learn how to manage AB Projects project settings: name, description, icon, perma name, estimate unit, task workflow (statuses, types, environments), GitHub integration, the Microsoft Teams link, and ownership, leaving, and deletion.
Role-Based Access Control
Learn how roles work in AB Projects. Every member is an Owner, Admin, or Member; new members join as Member by default. Admin and Owner control members, the Teams link, and workflow configuration, all scoped per project.