Adding or Removing Members
In AB Projects, each project is linked one-to-one with a Microsoft Teams team or channel. Membership follows that link: the people in the connected Teams channel are the people in the project. This keeps identity, access, and the member roster consistent with Teams instead of being a separate list you have to maintain by hand.
How members are added
There are two ways a person becomes a member of a project.
- Automatic sync from Teams (primary). When someone in the connected Teams channel opens the AB Projects tab, AB Projects syncs the channel roster and adds anyone who is in the channel but not yet a project member. New members join as Member. This runs in the background, so the roster keeps itself up to date as people are added to the Teams channel — you normally don't add members manually at all.
- Manual invite from the channel roster (secondary). An Owner or Admin can open Project Settings → Members and invite people who are already in the connected Teams channel but haven't opened the tab yet. The picker only lists people from the linked Teams channel — you cannot add an arbitrary Microsoft 365 user who isn't in that channel. To bring in someone new, add them to the Teams channel first; they then become invitable (and will auto-join when they open the tab).
Roles and permissions
A project member has one of three roles:
- Owner — full control of the project, including settings, workflow configuration, members, and the Teams link. A project always has at least one Owner.
- Admin — can manage members, configure task statuses/types/environments, and manage tasks.
- Member — can create, edit, and comment on tasks, and participate in the project day to day.
An Owner or Admin can change a member's role at any time from the Members tab. (There are no separate "Editor" or "Viewer" roles — everyone who works in the project is a Member or higher.)
Removing a member — and the Teams catch
From Project Settings → Members, an Owner or Admin can remove a member. Removal is a soft-delete: the person loses access to the project, but the tasks they created, their comments, and their change history stay intact and attributed.
Important: because membership is driven by the Teams link, removing someone from the project alone is not enough if they are still in the connected Teams channel. The next time the channel roster syncs, the automatic sync sees them in the channel but not in the project and re-adds them as a Member. To remove someone for good, remove them from the connected Microsoft Teams channel (or team) as well — ideally first. Removing them in AB Projects only is the right move when they have also left the Teams channel.
Tips
- Manage the Teams channel roster as your source of truth — AB Projects follows it. Adding or removing people in Teams is the most reliable way to control project access.
- Use the manual invite when someone is already in the Teams channel but hasn't opened the tab yet and you want them on the project now.
- Promote a trusted member to Admin so member and workflow management isn't bottlenecked on a single Owner.
- Removing a member never deletes their work. History and attribution are preserved so the project's audit trail stays complete.
By following the Teams link for membership, AB Projects keeps each project's roster accurate with almost no manual upkeep — while still giving Owners and Admins direct control over roles and access when they need it.