The team object is used to group users both from an organizational standpoint a project-by-project basis. When a Tactic organization is first set up, we try to encourage companies to model their organizational units & sub units within teams. Permissions & policies for specific resources & resource groups can then be granted to those teams. Once that is finished, the majority of teams are created on an ad-hoc basis and are more to help facilitate employees coordinating times to collaborate together, especially when cross functional teams (teams that are a mix of organizational unit teams) need to work together.
It is important to note that teams can be assigned to specific resources & resource groups. In addition to the specific Team Id assigned, any teams that have a child relationship with the assigned team will also be granted the same permissions.
For example, if Team "Sales" has an id of
team_1234 and is assigned permission to book desks in
Sales Suite, any users of Team "SDR" where the team
team_4567 and the
team_1234 will also be able to book desks in
id- string: Unique Tactic user id
parent_team_id- string: Unique Tactic team id that enables team hierachy
name- string: User's name
type- enum: Possible values are
total_users- number: Sum of all user's that currently belong in a team
Retrieve all teams within an organization
Retrieve details about a specific team
Create a new team within an organization