---
title: New Relic Teams
source: https://docs.newrelic.com/docs/service-architecture-intelligence/teams/teams
---

New Relic Teams connects the entities you're monitoring to the teams that own them. By clearly defining ownership, you can quickly identify the responsible team during an incident, find the right contact for any service or entity, and understand where a team sits within your organization. Teams helps you accelerate troubleshooting, enhance collaboration, and improve operational efficiency across your entire stack.

## Availability [#availability]

Teams is available for all [Full platform users](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-type/#user-type-capabilities). Core and Basic users don't have access to Teams. On the [Data + Core Compute](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/) pricing model, all users are Full platform users and have access to Teams.

## Roles and permissions [#roles-permissions]

The following roles determine what actions users can perform in Teams.

| Action                  | Required role                                                                                                                                                                                                                                                                                                                |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| View teams              | [**Organization read only**](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#standard-roles)                                                                                                                                                                |
| Modify teams            | [**Organization Product Admin**](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#standard-roles)                                                                                                                                                            |
| Create and delete teams | [**Organization Manager**](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#standard-roles) or [**Authentication Manager**](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#standard-roles) |

### Teams capabilities [#teams-capabilities]

To enable additional users to create and delete teams without granting them the Organization Manager or Authentication Manager roles, you can [create a custom role for Teams through the UI](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial/#roles). Teams permissions are organization-scoped.

| Capability                                                 | Permission identifier                |
| ---------------------------------------------------------- | ------------------------------------ |
| Read teams                                                 | `teams.read.team`                    |
| Delete teams                                               | `teams.delete.team`                  |
| Create teams                                               | `teams.create.team`                  |
| Modify teams                                               | `teams.update.team`                  |
| Read access to the automations/hierarchies settings page   | `teams.read.organization_settings`   |
| Modify access to the automations/hierarchies settings page | `teams.manage.organization_settings` |
| Create teams from IdP user groups (for example, Okta)      | `authentication_domain.read.groups`  |

> #### 💡 TIP
>
> You can also create a custom role for Teams via the NerdGraph API. For step-by-step instructions, see [Create custom roles for Teams](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-teams-custom-role-tutorial).

## Ownership and organizational context [#ownership]

The primary use case for Teams is ownership: enabling you to understand who owns what across the platform. This includes identifying the owning team for any given entity, along with relevant contact information. This capability is especially critical during incidents but is also broadly useful for day-to-day tasks.

By properly setting up Teams and ownership, you can quickly identify the responsible team whenever needed. Ownership information is surfaced in multiple places across the platform:

**During an alert event**

When you're looking at the **Issues** page in **Alerts > Issues and Activity**, you can find the Team information in the **Impacted entities** section.

![Screenshot showing how to find team during alert event](https://docs.newrelic.com/images/teams_screenshot-crop_find-in-incident.webp "How to find team during alert event")

**While navigating the platform**

You can always find the team ownership information in the header of an entity page.

![Screenshot showing how to find during navigation of site](https://docs.newrelic.com/images/teams_screenshot-crop_find-navigating.webp "Screenshot showing how to find during navigation of site")

**In maps**

When you're looking at maps, you can hover over any entities to show Team details. Also, you can click on an entity to open a right pane that includes team details.

![Screenshot showing how to find owner in maps](https://docs.newrelic.com/images/teams_screenshot-crop_find-in-maps.webp "Screenshot showing how to find owner in maps")

**In Catalogs**

When you're in **Catalogs**, you can view the Team or Teams assigned to each entity. To navigate to the **Teams** hub page, click the **link**.

![Screenshot showing how to find owner in Catalogs](https://docs.newrelic.com/images/catalogs_teams.webp "Screenshot showing how to find owner in Catalogs")

To narrow the Catalog results, you can also filter by Team. You can save UI changes by creating a Saved View, as explained in the [Customize the Team Hub](https://docs.newrelic.com/docs/service-architecture-intelligence/teams/manage-teams/#customize-team-hub) section.
/\*  \*/

**In All Entities**

When you're in **All Entities**, you can filter by Team to narrow the results.

![Screenshot showing how to find owner in all entities](https://docs.newrelic.com/images/teams_screenshot-crop_find-in-all-entities.webp "Screenshot showing how to find owner in all entities")

> #### 💡 NOTE
>
> If you have [Catalogs](https://docs.newrelic.com/docs/service-architecture-intelligence/catalogs/catalogs) enabled, it replaces **All Entities** as your default experience. You can filter by Team in Catalogs as well.

### Organizational structure and hierarchies [#organizational-structure]

Teams also provides organizational context, allowing you to see where a team sits within your organization, including its department and reporting structure. **Team Hierarchies** allow you to mirror your actual organization by nesting teams under "Parent" teams. This gives you instant operational clarity, making it easy to see which department is impacted when a specific team's service triggers an alert.

![Screenshot showing the org hierarchy](https://docs.newrelic.com/images/Teams-Hierarchies-Managers.webp "Screenshot showing the org hierarchy")

With hierarchies, you can:

-   **Navigate contextually:** Drill down from a high-level department view to a specific functional squad.
-   **Gain operational clarity:** Understand exactly which parent organization is impacted when a specific team's service triggers an alert.
-   **Manage ownership cleanly:** Better manage entity ownership and contact points across complex, multi-layered organizations.
-   **Identify leadership at a glance:** View the designated Manager or Point of Contact (POC) for any team at any level of the hierarchy. This ensures that when issues arise, you know exactly which leader is responsible for the underlying services without having to go through an external directory.

## The Team Hub [#team-hub-page]

The Team Hub acts as a centralized workspace where your team can access its assets, manage team-level settings, and view insights across the entities it owns. The Team Hub is also [customizable](https://docs.newrelic.com/docs/service-architecture-intelligence/teams/manage-teams/#customize-team-hub), allowing teams to tailor the experience to their needs.

In the **Overview** tab you will find:

-   All active issues related to the entities your team owns that have been opened in the last 3 days.
-   A summary of your team's [Service Levels](https://docs.newrelic.com/docs/service-level-management/intro-slm/) statuses.
-   A summary of your team's [Workloads](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/workloads/workloads-isolate-resolve-alert-events-faster/) statuses.
-   A summary of your team's [Scorecards](https://docs.newrelic.com/docs/service-architecture-intelligence/scorecards/getting-started) compliance.
-   All error groups ([Errors Inbox](https://docs.newrelic.com/docs/triage-inbox/getting-started/)) of your team.
-   The list of team members that make up this team.
-   The list of all the important [dashboards](https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) for easy access by any members of the team.
-   Links to documentation, runbooks, and troubleshooting guides relevant to your monitored systems and applications.
-   The list of the team's [Workflows](https://docs.newrelic.com/docs/alerts/get-notified/alert-event-workflows/).
-   The list of the team's [Alert Policies](https://docs.newrelic.com/docs/alerts/organize-alerts/create-edit-or-find-alert-policy/).
-   Development and productivity metrics: Integrated directly from GitHub to provide a real-time view of your engineering health, including:
    -   PR cycle time and open PRs: Track how long Pull Requests stay open and identify bottlenecks in the review process.
    -   Deployment frequency, Mean Time to Recovery (MTTR), and Change Lead Time (CLT) to measure software delivery performance.

![Screenshot showing the team hub page](https://docs.newrelic.com/images/teams_hub.webp "Screenshot showing the team hub page")

In the **Entities** tab you will find all the entities your team owns and their [health status](https://docs.newrelic.com/docs/alerts/create-alert/examples/view-entity-health-status-find-entities-without-alert-conditions/).

[Manage Teams](https://docs.newrelic.com/docs/service-architecture-intelligence/teams/manage-teams)

Learn how to create teams, manage hierarchies, and customize the Team Hub

[Configure entity ownership](https://docs.newrelic.com/docs/service-architecture-intelligence/teams/team-ownership)

Learn how to assign entity ownership to teams
