Visibility in AB Projects comes down to one thing: project membership. If you're a member of a project, you see everything in it. Roles change what you can change, never what you can see.
There are no per-task permissions and no private tasks. You can't hide a task from some members and show it to others. If a workstream shouldn't be visible to the whole team, it needs its own Teams channel and project — see Confidentiality and Enterprise Agreements.
What every project member sees
- All tasks in the project — nothing is hidden per task.
- All comments and change history on any task.
- All subtasks — they're just tasks in the same project, visible to the same people.
- The same content everywhere — the List, Gantt, and Kanban views, the Teams channel tab, and the web app all show one project to one membership.
Who counts as a member follows the connected Teams channel and syncs automatically — see Adding or Removing Members and, for bringing in new people, Inviting Team Members.
Roles decide what you can change, not what you can see
Every member has one of four roles. None of them limits visibility — even a Viewer sees the whole project; the differences are all about what you can change:
| Role | Sees | Can change |
|---|---|---|
| Owner | Everything in the project | Everything an Admin can, plus ownership transfer and project deletion |
| Admin | Members and roles, the workflow (statuses, types, environments), and the Teams link | |
| Member | Day-to-day work: create, edit, assign, and comment on tasks | |
| Viewer | Nothing — read-only by design; can browse every task, comment, and view |
Full details are in Role-Based Access Control.
Two different things can make someone read-only. The Viewer role is a deliberate permission choice by your project admins. Separately, a member without a paid seat can also see everything but not write — that's licensing, not permissions, and it resolves the moment a seat is assigned (see Managing Subscriptions, Billing & Licenses).
A few specifics
- A task's Open link on the Teams card opens the task only for project members signed in with Microsoft SSO — it is not a public link (see SSO and Microsoft Login).
- People you pick in a comment's mention picker get @mentioned in the Teams channel post and receive Teams' notification — but the comment itself is still visible to all project members.
- Inside Microsoft Teams, the channel tab applies exactly the same membership rules, scoped to the linked project.
In short: membership decides visibility, role decides what you can change. Anything that needs to be hidden from the wider team belongs in its own channel and project.