In AB Projects, a project is a shared workspace — tasks, wiki, documents, and members — and every project is tied to exactly one Microsoft Teams channel. The part people get wrong: you don't build the team inside AB. The channel decides who's in.
What lives inside a project
Everything is scoped to the project — nothing leaks between projects, even for people who belong to several.
Tasks and views
The project's task list with Board, List, and Gantt views, plus comments, subtasks, and change history. See Creating and Editing Tasks.
Its own workflow
Each project defines its own task statuses, types, and environments, so each team's board matches its own process. See Task Statuses and Workflows.
Wiki and documents
A project wiki for shared knowledge, linkable to tasks. See Wiki Overview.
Members and roles
The roster synced from the Teams channel, each person with a project-scoped role. See Role-Based Access Control.
One channel, one project
A project is created (or linked) when someone adds the AB Projects tab to a Teams channel — see Installing the AB Projects Teams App. From then on, that channel maps to exactly one project and that project links back to exactly one channel, so there's never any ambiguity about where a project “lives.” Task updates and comments post into that channel, and replies in the channel thread sync back to the task.
An Owner or Admin can unlink the channel later from the project's settings; the project and its tasks survive unlinking. See Managing Project Settings.
Members come from the channel
You don't add people one by one. When anyone in the channel opens the AB Projects tab, the whole channel roster is synced into the project — including people who have never opened the tab themselves. New members join as Member. If someone is in the channel but not yet on the project, an Owner or Admin can also bring them in immediately from the Team page (the picker is limited to the channel's roster). Full details: Adding or Removing Members and Becoming a Project Member.
Because membership follows the channel, project access stays aligned with what your Microsoft admins already control — identity comes from your organization's Microsoft 365 tenant (your company's Microsoft 365 account), and sign-in is the same single sign-on Teams itself uses.
Roles at a glance
Every member has one of four project-scoped roles:
| Role | In one sentence |
|---|---|
| Owner | Full control, including ownership transfer and (when unlinked) deleting the project. |
| Admin | Manages members, workflow configuration, integrations, and the Teams link. |
| Member | The default working role — creates, edits, assigns, and completes tasks. |
| Viewer | Read-only: sees everything, can't change anything or be assigned tasks. |
Roles are per project — being an Admin in one project says nothing about your role in another. The full permission model is in Role-Based Access Control.
Working across projects
A person can belong to many projects — one per client, product area, or internal team is a good default. Switch between them from the Projects tab, and use Home for a cross-project view of what's on you. See Navigating the Interface.
In short: pick the Teams channel where the team already talks, add the AB Projects tab, and the workspace and its membership take care of themselves.