Team Overview

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 id is team_4567 and the parent_team_id is team_1234 will also be able to book desks in Sales Suite.

Attributes


  • 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 organization & project
  • total_users - number: Sum of all user's that currently belong in a team

Endpoints


Teams

GET /teams

Permissions: team:read

Roles: owner

Retrieve all teams within an organization

GET /teams/:teamId

Permissions: team:read

Roles: owner

Retrieve details about a specific team

POST /teams

Permissions: team:add

Roles: owner

Create a new team within an organization

Was this page helpful?