Resolves the team to its member resources, grants project access to each user who is not already a member, and leaves existing members unchanged. Access levels follow the same rules as creating or updating individual project membership (workspace role constraints, guest vs licensed user, global admin, etc.).
A project member is a user who has access to a specific project. Project members are assigned a project security role, which controls the level of access they have to the project. Possible project security roles include manage, edit, collaborate, creator, and guest.
Bearer authentication of the form Bearer <token>, where token is your auth token.
Business team identifier (BusinessTeamId); all active team members with a user account are considered.
Optional flags for default access (e.g. editor vs collaborator) for newly added members.
When true, new teammates receive editor-level access (subject to workspace role rules). When false, they receive collaborator access (again subject to role rules, e.g. guests).
True if the API call succeeded; false otherwise.