About teams

Teams are groups of users that share access to the same advertisers, agencies, orders, and ad units. They allow you to specify which entities in your network a user has access to. For example, you might have a German trafficking team to work with your German advertisers, an automotive team to work with your auto advertisers, or teams for each of your web properties, such as your sports site, your news site, and your humor site.

Teams provide users with access to entities in DFP. You add users to a team, and you assign advertisers, agencies, orders, and ad units to the team. Users on the team can only see and work with the entities that have been assigned to the team. Users and entities can be assigned to more than one team.

You can't assign line items or creatives to teams. However, a line item is always part of an order, so it's restricted by the order it's in. Similarly, every creative belongs to an advertiser, and users can only view creatives that belong to advertisers assigned to their teams.

Restrictions imposed by teams

When you use teams, the following restrictions are imposed on how objects interact.

Limits on access

  • Advertisers, agencies, orders, and ad units: Users can only see and interact with advertisers, agencies, orders, and ad units assigned to one of their teams.
  • Creatives: Creatives can't be assigned to teams. However, each creative belongs to an advertiser. Users can only see and interact with creatives that belong to advertisers assigned to one of their teams.
  • Placements: Placements can't be assigned to teams. However, placements contain ad units, which can be assigned to teams. A user can only see and interact with a placement if all of the placement's ad units are assigned to teams the user is on.

    For example, a user is on Team China and Team India. Placement A contains ad units assigned to Team China. Placement B contains ad units assigned to Team India and Team Japan. The user can view Placement A, but not Placement B.

  • Users: Admins can see all users and add them to teams. Other users can only see other users who are on at least one of the same teams.

    For example, an order is assigned to Team Cats and Team Dogs. The trafficker is only on Team Cats, while the salesperson is only on Team Dogs. When the trafficker views the order, she doesn't see the salesperson, and when the salesperson views the order, he doesn't see the trafficker.

  • History: Users can see the histories of entities to which they're assigned. However, the names of any salespeople or traffickers are hidden if they're not on the same team as the user. For example, if a line item is assigned to Team A and Team B, a trafficker on Team A wouldn't be able to see the name of a salesperson on Team B.

    Change history on the "Admin" tab is only viewable by users on the "All entities" team.

Limits on assignments to teams

  • Orders are under advertisers: Orders can only be assigned to teams that their parent advertisers are assigned to.
  • Assignments of users and agencies to orders: Users and agencies can only be assigned to orders as traffickers, salespeople, etc., if they're on a team to which the order is assigned.
  • Adding users to teams: If it suits your business needs, you might choose to create team admins. Team admins can assign users and objects to their own teams or others. For example, a team admin on Team 1 and Team 2 can create a new user and add the user to Team 1, Team 2, both or any other team. The team admins could also create a new team and assign users and objects to it.

Inventory restrictions

  • Inventory targeting: Line items can only target ad units (or placements containing ad units) that are assigned to at least one team in common with the order. (Run-of-network line items are an exception.)
  • Run-of-network line items: Only users on the "All entities" or "All inventory" team can create run-of-network line items. Other users can only create line items that target specific inventory assigned to their teams. As a best practice, you can designate some users as trusted run-of-network users who can traffic house ads, AdSense and Ad Exchange line items, and so on.
To simplify trafficking, you can create a run-of-team placement: for each of your teams, create a placement that includes all of the ad units on the team. That way traffickers can easily target all of their available inventory. You'll need to keep these run-of-team placements up to date manually with your latest inventory.

Unrestricted entities and functionality

Some entities and functionality in DFP are not restricted by teams. These include:

Teams administration

Teams limit access, but someone has to set up teams and add users and entities to them. These users, typically admins, are on the "All entities" team, which provides access to all entities in your network. By default, admins are added to the "All entities" team. The user role also includes a permission that enables admins to see and edit all users. (Learn more about roles.)

You can also designate team-level admins by removing admins from the "All entities" team and adding them to other teams. These team-level admins can view all users and add them to their own teams. They can also create new teams. They can only see advertisers, agencies, orders, and ad units that have been assigned to one of their teams.

Teams versus roles

Teams provide users with access to entities in your network: advertisers, agencies, ad units, and orders. Roles determine which features and functions a user can access, such as viewing or editing creatives. To view or edit an object, a user has to be both part of a team that includes the object and assigned a role that can access the object. (Learn more about roles.)

Depending on the user's role, a user might not have permission to view orders, ad units, or advertisers and agencies. Even if the user is on a team that includes these objects, that user can't access them because of the user role restrictions.

If you're having trouble with users who don't have the access you think they should based on the teams they're on, check their roles to ensure that they have the necessary permission to view and edit the objects they need access to.

How helpful is this article:

Feedback recorded. Thanks!
  • Not at all helpful
  • Not very helpful
  • Somewhat helpful
  • Very helpful
  • Extremely helpful