Who Can See What?
Visibility in AB Projects is simple: it's based on project membership, not on per-task permissions. If you're a member of a project, you can see that project's work; roles control what you can manage, not what you can see.
What a project member can see
- All tasks in the project — there is no per-task "private" visibility, so tasks aren't hidden from some members and shown to others.
- Comments and change history on any task they can see — any member can read and add comments.
- Subtasks — these are just tasks in the same project, visible to the same members.
- The same content across the List, Gantt, and Kanban views and in the linked Teams channel.
Who is a member is driven by the connected Teams channel and synced automatically (see Becoming a Project Member in AB Projects). To keep a workstream confidential, put it in a separate Teams channel/project with only the right people (see Confidentiality and Enterprise Agreements).
Roles control management, not visibility
Every member has one of three roles — Owner, Admin, or Member (there is no "Editor" or "Viewer", and no read-only tier):
- Owner / Admin — everything a Member can do, plus manage members and roles, configure the workflow (statuses/types/environments), and manage the Teams link; Owner also handles ownership transfer and project deletion.
- Member — create, edit, assign, and comment on tasks, and participate day to day.
See Role-Based Access Control for the full breakdown.
A few specifics
- A task's Open link (from the Teams card) opens the task only for people who are members of that project and signed in with Microsoft SSO — it's not a public link.
- Members you select in a comment's mention picker are @mentioned in the Teams channel post and get Teams' notification; the comment itself is still visible to all project members (see Commenting with Mentions in Channels).
- Inside Microsoft Teams, the same membership rules apply, scoped to the linked project.
In short: membership decides visibility, role decides management. For anything that needs to be hidden from the wider team, use a dedicated channel/project.