---
name: monitoring-teams
title: Working with teams
description: You can use teams to add another dimension of control on the data that is available through a monitoring instance in addition to platform and service access controls. A user with the **manager** service access role for an IBM Cloud Monitoring instance can create, delete, add members, and change the scope of teams in that instance. Once a team is created, an admin can add a user to it through IBM Cloud® Identity and Access Management (IAM).
last-updated: 2026-09-17
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/monitoring?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Working with teams
{: #teams}

You can use teams to add another dimension of control on the data that is available through a monitoring instance in addition to platform and service access controls. A user with the **manager** service access role for an IBM Cloud Monitoring instance can create, delete, add members, and change the scope of teams in that instance. Once a team is created, an admin can add a user to it through IBM Cloud® Identity and Access Management (IAM).
{: shortdesc}

In the world of microservices, it is becoming harder to track down valuable metrics and ensure that no sensitive data is exposed. By using teams, administrators can apply a fine grain control on resources. Consider the following information when you work with teams:
* You can create 1 or more teams in a monitoring instance.
* You can specify what resources and metrics are visible for users that are granted IAM permissions to work in the team.
* You can enhance the users experience by customizing the initial dashboard that users in a team get when they launch the web UI.

These instructions assume that you have provisioned a monitoring service instance on IBM Cloud.
{: note}


## Assigning a user to a team
{: #teams_assign}

To add a user to a team, complete the following steps:
1. Check that you have the **administrator** platform role to work with the monitoring service or with a specific instance.
2. Define a team level IAM policy for the user. For more information, see [Granting permissions to work in a team](https://cloud.ibm.com/docs/monitoring?topic=monitoring-iam_grant_team&format=markdown).

When the policy is defined, the user is added to the list of users that have access to work with resources configured for a team.


## Creating a team
{: #teams_create}

You must have **manager** role to create a team in a monitoring instance.

An administrator or a manager of an IBM Cloud Monitoring instance must switch to the *Monitor Operations* team before he can create teams and manage existing teams.
{: note}

Complete the following steps to create a team:

1. [Launch the web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch).

2. Click the **user icon**.  This is the icon with the initials of the logged on user.  Then click **Settings**.

3. Click **Teams**. The list of existing teams is displayed.

4. Click **Add Team**. The team configuration page is displayed.

5. Configure the team details.

    * Choose a color.

    * Enter the name of the team

    * [Optional] Enter a description for this team.

    * [Optional] Set the **Default team** parameter if you want this team to become the default team for new users.

    * Set the **Default Entry Point** to specify the view in the web UI that opens every time a user logs in. By default, the *Explore* view is set.

6. Configure the team scope.

    * [Optional] Set **Scope by** to specify the level of data that members of the team have access to. Valid values are *Host* and *Container*.

        If the parameter is set to *Host*, members can see all Host-level and Container-level information.

        If the parameter is set to *Container*, members can see only Container-level information.

    * Set the **Scope** to limit what data users can see. You can set one or more conditions by specifying expressions for metrics.

        By default, the scope is set to *everywhere*.

    * [Optional] Enable or disable **Sysdig captures**. Check this box to allow this team to take IBM Cloud Monitoring captures.

        Capture files will only be visible to members of this team.

        Captures include detailed information from every container on a host, regardless of the team’s scope.

    * [Optional] Enable or disable **Infrastructure Events**. Check this box to allow members to view all custom infrastructure events from every user and monitoring agent. When is not checked, users can see infrastructure events that are sent specifically to this team.

    * [Optional] Enable or disable **Platform Metrics**. Check this box to allow members to view platform metrics.  You can scope the metrics to limit the metrics team members can see.

7. Click **Save**.

    ![Team Configuration](images/team-configuration.png "Team Configuration"){: caption="Team configuration" caption-side="bottom"}

## Changing the scope of a team
{: #teams_scope}

You must have **manager** role to change the scope of a team in a monitoring instance.

To change the scope of the data that is visible to members of a team, complete the following steps:

1. [Launch the web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch).

2. Click the **user icon**.  This is the icon with the initials of the logged on user.  Then click **Settings**.

3. Select **Teams**. The list of existing teams is displayed.

4. Identify the team and select it. The details of the team are displayed.

5. Change configuration details in the *Visibility* section.

6. Click **Save**.


## Deleting a team
{: #teams_delete}

You must have **manager** role to delete a team in a monitoring instance.

Complete the following steps to delete a team:

The default team, **Monitor Operations**, cannot be deleted.
{: note}

1. Launch the web UI. For more information on how to launch the Web UI, see [Navigating to the Web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch).

2. Click the **user icon**.  This is the icon with the initials of the logged on user.  Then click **Settings**.

3. Select **Teams**. The list of existing teams is displayed.

4. Identify the team that you want to delete and select it. The details of the team are displayed.

5. Click **Delete team**.

When you delete a team, users that only belong to this team will be moved to the default team.
{: important}


## Changing the default entry point of a team
{: #teams_change_default_entry_point}

You must have **manager** role to change the default entry point for a team in a monitoring instance.

Complete the following steps to change the default entry point:

1. [Launch the web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch&format=markdown#launch).

2. Click the **user icon**. This is the icon with the initials of the logged on user. Then click **Settings**. 

3. Select **Teams**. The list of existing teams displays.

4. Identify the team that you want to update and select it. The details of the team are displayed.

5. In the **Default Entry Point** field, change from **Explorer** to **Advisor**    .

6. Click **Save**.

   The next time that a user who is a member of this team logs in to the web UI, the *Advisor* view opens by default.