Invite people, organize teams and keep team membership separate from workspace roles.
Member and team management lives under Settings Teams and owner or admin surfaces when the current user is allowed to manage it.A team has a name, description, type, active state and optional manager. Team membership records link a profile to a team and can keep a team specific role. The membership model allows one profile to belong to multiple teams.
The workspace role helps determine permission defaults. Team membership helps determine which team scope the user belongs to. They are not the same field.For example, a finance user can have Accounting and Agreements access through role defaults while also belonging to an operational team for shared work. A support user can have Tickets access without receiving Accounting access simply because both people belong to the same team.
Managers can receive team based scope and permissions. Their exact visible areas depend on the permission snapshot and access resolver, so do not assume the word “manager” means full workspace visibility.
Revoking a workspace membership, leaving a team and denying a product area are different actions. Use the one that matches the access you actually want to remove.