Teams

Important!

TAP users only have access to campaigns/flights that are assigned to the team(s) they belong to. (Exception: Organization Administrators can access all campaigns from all teams.) If you wish to restrict access to campaigns, be sure to create meaningful teams and to assign users to teams according to the access you wish them to have. For example, if you have multiple stations in different markets, you can create a team for each station or for each market. A trafficker can then be assigned to only those stations or markets which you want them to have access to. (See Teams Use Case Example, below.)

You can change a campaign’s team assignment after creating the campaign. If a user is locked out of a campaign because they don't belong to the team it is assigned to, you can fix the problem by changing the campaign's team assignment, or you can assign that user to the team that the campaign is already assigned to.

See "Best Practices for Teams" below. Also see Team Notes in "Creating Campaigns."

Every organization is required to have at least one team. Teams are typically made up of the organization's administrator, campaign managers, traffickers, and so on. Teams are used to filter campaigns and flights so that team members only see campaigns and flights that are assigned to their team.

When an organization is created, a "Default" team is created with it. Even if you only need one team, you should create a new team and assign all of your users to it. As a best practice, only assign Organization Administrators to the "Default" team.

Larger publishers might want to separate trafficker groups by region, market, or along whatever lines make up your organizational structure. (For example, a national publisher might have an "eastern region" team and a "western region" team, or a team for each major city within its broadcast area.)

A campaign (and thus its flights) can only be assigned to one team, but a user can belong to more than one team.

To see the list of teams for the current organization, select Teams from the left sidebar. Once on the Teams page you will see a list of the current teams for that organization. Click any team (or select Edit team from its Options menu) to view the Team overview or edit the team name.

A team can belong to only one organization. However, individual users can belong to multiple teams and multiple organizations.

Creating a Team

Not all users can create or manage teams; it depends on your user role. To create a team, first be sure you are in the correct organization, then go to the Settings menu.

To create a team:

1. Select Teams from the left sidebar of the Settings menu.

2. On the Teams page, select + New team in the upper-right corner.

3. Enter the team name on the New team page.

4. (Optional) Un-select Access to sell-thru rate (STR) report if you do not want members of this team to access the STR report in TAP Explore.

5. Click Create team (or Create team and... create another team).

Tip: If you want to restrict access to a particular station or podcast to only one team, use a team name that reflects the station/podcast name, and be sure to assign all campaigns for that station/podcast to that team.

To add people to a team, go to the Users page.

Teams and Reporting

Users can only access reporting data for campaigns that are associated with teams they belong to.

For example, in the team assignment scenario shown here:

• User 1's TAP Explore and Affidavit reports will only include data for campaigns that are associated with Team A, except for TAP Explore's STR report, which includes all teams.

• User 2's TAP Explore and Affidavit reports will only include data for campaigns that are associated with Team B, except for TAP Explore's STR report, which includes all teams.

• User 3's TAP Explore and Affidavit reports will include data for campaigns that are associated with both Team A and Team B.

In TAP Explore you can filter your queries by Team Name, and you can include Team Name as a dimension in your reports. See Best Practices for Teams, below, for tips on how to use this filter/dimension to its best advantage.

Teams Use Case Example

To keep it simple, this use case only mentions traffickers, but the same rules apply to other user roles except Organization Administrators, who can see all campaigns from all teams.

You have several stations in New York, plus a station in Boston, one in Chicago, and one in Chugwater. You want the traffickers for the New York stations to be able to see all campaigns for every New York station, and the other traffickers to only see campaigns that are assigned to their station (Boston, Chicago, Chugwater).

Exceptions are Bob, who needs to see all stations on the east coast (New York and Boston) and Olivia, who works in Chugwater but also monitors the Chicago station campaigns.

Occasionally, Olivia needs temporary access to one of Bob's New York campaigns. When that happens, the organization administrator adds Olivia to the New York Team and then removes her when that temporary need has passed.

The use case example above refers to live streaming stations, but the same principles can be applied to podcasts or other publisher types. For example, instead of dividing the teams up by geography, you could divide them according to podcast programs or program groups.

Best Practices for Teams

For best results, please observe the following best practices when creating teams and users.

• Unless you have a very small organization, do not assign users to the "Default" team, except for Organizations Administrators. Instead, create teams according to your organization's stations and markets, and assign users to the appropriate teams for their work.

• Be sure to align your users' team settings with any Content Access Control (CAC) restrictions they might have in the Triton Streaming Console. For example, if a user does not have access to a particular station or market in CAC, do not assign them to a TAP team that is assigned to that station or market.

• Do not assign the Organization Administrator role to a user who also has Content Access Control restrictions (CAC) in the Triton Streaming Console. (Or, put another way, do not apply CAC restrictions in the the Console to your TAP Organization Administrators.)

• Be aware that applying any Content Access Control (CAC) settings in the Triton Streaming Console can affect TAP reporting (TAP Explore, affidavits, and forecasting), as the queries will only return data for stations the user has access to.

• If you have access to multiple organizations, consider re-naming the "Default" team to something that reflects the organization name. Otherwise, if you run TAP Explore reports using the Team Name filter/dimension you will see multiple instances of the "Default" team with no way to tell which Default team belongs to which organization.

• To avoid confusion between sandbox teams and production teams, include the word "Sandbox" in your sandbox team names (including the "Default" team).

Archiving a Team

Archiving a team works the same way as archiving advertisers, campaigns, and flights. For more information see Archiving.