Understanding Projects and Teams
In AB Projects, work is organized around projects. A project is a self-contained workspace — its own tasks, statuses, types, environments, wiki, and members — tied to a Microsoft Teams channel where the team already works.
What is a project?
- A project represents a unit of work — a product, department, client, or initiative.
- Everything is scoped to the project: its task list, comments, subtasks, Board/List/Gantt views, and its own configurable statuses/types/environments. (Some projects also have CRM capabilities.)
- It runs under your organization’s Microsoft 365 tenant — identity and SSO are inherited; each project manages its own members and roles.
- A person can belong to many projects and switch between them from the Projects tab.
Teams integration: one channel per project
- A project is linked to a Microsoft Teams team and channel. The relationship is one project ↔ one channel, so there’s no ambiguity about where a project “lives.”
- A project is created/linked by setting up the AB Projects tab in a channel (see Navigating the Interface). An admin can change or relink the channel later from Settings.
- If a channel has been unlinked, opening the tab there will prompt to set it up again.
Members come from the channel
- You don’t add people one by one. Members are synced automatically from the linked Teams channel — everyone in that channel becomes a project member and stays in sync as the channel changes.
- Need someone in immediately? An admin can use the manual invite on the Team page (limited to the channel’s roster). Full details: Inviting Team Members.
- Because membership follows the Microsoft Teams channel, access stays aligned with what your Microsoft admins already control.
Roles
- Project roles are Owner, Admin, and Member.
- Owner / Admin manage the project — settings, the linked channel, task options, and members’ roles.
- Member is the standard role for everyone working in the project: create, edit, assign, comment, and complete tasks.
- Admins set roles from the Team / Members area.
Tips
- Use a separate project per client, product area, or internal team — each gets its own scoped tasks, options, and members.
- Pick the Teams channel the team already works in — the whole channel is onboarded automatically.
- Switch context anytime from the Projects tab; use Home for a cross-project “what’s on me” view.
With project-scoped workspaces and channel-driven membership, AB Projects keeps collaboration clean, access secure, and every team’s work in its own clear place.