Skip to main content
Planview Customer Success Center

Agile Teams

The Agile Teams capability allows for individual users to be grouped into dedicated teams and teams to be grouped within other teams. It also significantly reduces the amount of time account administrators and board administrators will need to spend on bulk user administration and new user onboarding.

Agile Teams are created and defined under the Teams section within Account Settings. Account Administrators and Team Organizers (new account role) have the ability to create and manage Agile Teams. Administrators can create, manage, and view all teams. Team Organizers can create and edit their own teams, but can't edit others' teams.

To access Agile Teams:

On the Home screen, go to Account Settings by clicking the gear icon Account Settings on Home.png .This will take you to the Account Settings screen. Click the Teams tab:

Teams page.png

At present all teams are public to the organization.

You would use the Enable/Disable toggle if, say, you're in the middle of doing some Admin work on a team and you don't want the team to be added to boards, but you don't want to lose their information. Thus you can disable the team, and after the team is built, you can enable it.

Team Behavior

Planview AgilePlace supports a nested teams structure with five levels, currently. For example, let's say that we have three teams: Engineering, Front-End, and Sparkles. The Engineering team could be the top-level parent team with Front-End as a child team and Sparkles could be a child team of the Front-End team. This means that if I assigned the Engineering team to the Lean/Agile Development board with role of User then the Front-End team and Sparkles team would inherit the User role on the Lean/Agile Development board, unless these users originally had Reader permissions, in which case they remain Readers (see note box below).



Reader users will be capped as a Reader across all boards even if they're added to a team and that team has higher permissions on boards.


  • Individual users can be added to as many teams as desired.
  • A team can only have one parent team (Team Alpha can't be added to both Team Engineering and Team Product).

Edit a Team

To Update a team, click the team name and click Edit details to add individuals or teams, and change other team details. To add an emoji for the team, right click at the start of the team name and select an emoji from the list. Click Update Team.

AddEmojiToTeamName.png            Bacon.png



An individual user can be part of multiple teams. A team can only be part of one other team.


When you click on a team, there are three views available:

  • Overview - Displays a preview of members and boards for a given team.
  • Members View - Shows all members (including other teams) for a given team.
  • Board View - Shows all boards that a given team has access to with corresponding permissions. 


To assign boards to a team, click Overview > Add board (below).


On the subsequent Assign Board Access popup you can look up boards and assign board roles for teams.


Account Roles/Board Roles



Account Admins are able to assign teams to any/all boards within an account. Team Organizers are able to assign teams only to boards where they have the correct permissions (Board Manager or higher).

Also, Team Organizer is an Account Role, not a Board Role (board roles include Reader, User, Manager, and Administrator).


Team Organizers:

  • Have access to Account Settings, where they see a read-only view of the Account User List and have access to the Teams tab.
  • Can create and manage their own teams. They cannot edit/manage teams that they didn't create.
  • Can interact with the Planning Series capability.
  • Can create, archive, and duplicate boards.
  • When creating a new board, the default user security setting is now "Assign the Everyone Team to this board with a permission of _". This is a checkbox setting that is enabled by default. When unchecked, the permission dropdown is disabled.


When you add users and teams to a board, the highest permission wins except for Readers. For all other users, if you assigned Amanda to a board with the role of User, but she's part of Team Alpha, which has a board role of Manager, Amanda would have Manager permission for that board because she is part of Team Alpha.

If there's a discrepancy between team and user permissions, a warning symbol will appear next the the user or team within the Members tab on a board. Additionally, role inheritance is displayed by a clickable connections icon on the Boards section of the Team page.



  • The Board User List tab within Board Settings has been renamed to Members.
  • The Members tab is blank except for showing the user that created the board and/or showing the Everyone team, if added during the board creation process.
  • Within Members, user permission mismatches will be highlighted. A user permission mismatch could occur because a user is either an Account Admin or has been added to a board with a lower permission than a team's (that they belong to) permission on that board.
  • For boards that have default user security set to Reader or higher, the Everyone team will be added with the corresponding board role.
  • Teams can be added to boards from the account-level Teams tab. This includes the Everyone and External teams.
  • Teams can be added to boards from the Members tab. This includes the Everyone and External teams. 

Everyone and External teams

All teams are manually generated except the External and Everyone teams, which are system-generated and locked, and exist for all accounts. When accessing a user profile from the Account User List, user profiles have an attribute called External user, where, if checked, the user will be added to the External team and removed from the Everyone team. You might use this in the case of external members and contractors, where you want to limit their access to a subset of boards, but want the access for everyone else in the organization to be open. 

  • The Everyone team includes every user within the account that doesn't have the External User user attribute configured.
  • The External team only includes users with the External User attribute configured.



The External user setting doesn't impact any permissions or authentication. It is a way to mark and separate which users have access to your environment that are not part of your organization.