A role-based administration team is a group of users that can view and share ownership of tasks and configurations that belong to the team. For example, if you have multiple departments that want to share queries or tasks, you can group the departments into a team. A team's tasks and configurations appear in a special group named after the team in a tool's tree view. For example, if you have a team named "Salt Lake" that you are a member of, you would see a "'Salt Lake' devices" subgroup under the Devices group in the Network view. People can belong to multiple teams.
People who aren't in a particular team won't see that team's group anywhere in the console. People with the administrator right see all teams and team content. While you can use public folders to share console content, public folder content is visible to everyone with rights to a tool. The advantage with teams is that only team members see team content, potentially making content more organized and accessible to team members.
Teams consist of one or more group permissions. You can even create teams with as few as 1 or 2 people. For example, if a person is out sick, you can add that person's substitute to the same team. Or, if you have two people that share responsibilities, you can put them in the same team.
Administrators and team members can change the ownership of tree items by right-clicking them and clicking Info. Information dialog boxes have an Owner drop-down list where you can select the item's owner.