New Relic One users and roles

For accounts on our New Relic One pricing plan, this document explains:

This doc is about managing users for accounts with New Relic One pricing. Not sure which you're on? See Overview of pricing and users.

Manage users

Here are some important user management tips:

  • Basic users are free users but can self-serve to immediately become billable full users. We allow this so that if you have an incident, your team members can upgrade and quickly work on problems.
  • A New Relic user can have a maximum of either three concurrent active sessions, or three unique IP addresses in use at any given time.

Where you manage users in the UI depends on their user model:

User type: basic and full

The user type determines the monitoring and analysis features a user has access to, and is a key factor in billing. (Note that user type does not control account admin-related permissions; that's determined by the user group.)

User types are:

  • Basic user: These users are free and have access to basic features like setting up reporting of data, running queries of data, making custom charts and dashboards, and setting up alerts. They do not have access to Full-Stack Observability features. For details, see Capabilities.
  • Full user: These users are billable and have access to Full-Stack Observability capabilities, including our curated UI experiences, like APM, infrastructure monitoring, browser monitoring, mobile monitoring, and synthetic monitors. The Standard pricing tier includes one full user. For details, see Capabilities.

Are you switching from original pricing to New Relic One pricing? Learn about updating your users. Or learn more about user-related billing calculation.

To understand more about which user type to choose, expand a section:

Compare full vs basic capabilities

Below is a detailed table showing differences between basic user and full user capabilities. In short, basic users have access to our Telemetry Data Platform and Applied Intelligence (read-only) features, while full users have access to that plus Full-Stack Observability features.

Features Full user Basic user
Full-Stack Observability
(New Relic-built UI experiences)
Application performance monitoring (APM) UI fa-check
Infrastructure monitoring UI fa-check
Digital Experience Monitoring (Browser, Mobile, Synthetics) UI fa-check
Serverless monitoring UI fa-check
Logs in context with other UI experiences fa-check
Synthetics checks fa-check
New Relic Edge with Infinite Tracing (tail-based sampling) fa-check
(Pro and Enterprise)
Subscribe to New Relic One catalog apps fa-check
Assorted curated UI experiences (distributed tracing, Kubernetes cluster explorer, workloads, etc.) fa-check
Applied Intelligence (AI)
Proactive Detection fa-check fa-check
(read-only)
Incident Intelligence fa-check fa-check
(read-only)
Telemetry Data Platform
Data ingest from any source (Metrics, Events, Logs, Traces) fa-check fa-check
Alerts and notifications fa-check fa-check
Interactive query interface fa-check fa-check
Custom charts and dashboards (not New Relic-built) fa-check fa-check
Encryption at rest fa-check fa-check
Standard data retention fa-check fa-check
NerdGraph (GraphQL) API fa-check fa-check
Security and compliance fa-check fa-check
Integrations fa-check fa-check
Data management fa-check fa-check
Logs UI fa-check fa-check
Build custom New Relic One apps fa-check fa-check

Learn more about user-related billing calculations.

Tips on choosing user type

Reasons to make someone a full user:

  • They play a key role in the development, testing, deployment, and maintenance phases of the application development lifecycle.
  • They break/fix code regularly; they are responsible for triaging workflows, troubleshooting, or managing users and roles for their team.
  • They have DevOps practices (i.e. version control systems and implement CI/CD).
  • They need to use New Relic's curated dashboards and experiences (not just the ability to create their own custom queries and charts); in other words, they need full access to our platform.
  • They need to be able to manage users.

Reasons to make someone a basic user:

  • They play a key role in the planning phase of the application development lifecycle.
  • They use and configure New Relic agents, APIs, and integrations to send us data, and access, configure, and use alerts on such data (not necessarily responsible for triaging workflows, troubleshooting, or managing users and roles for their team).
  • They want to see high-level analytics and business metrics for future planning (such as C-Suite executives).
  • They do not need to use our curated experiences and dashboards, but would benefit from the ability to create their own custom queries and charts of data; in other words, they don't need full access to the platform.
  • They don't manage users.

Learn more about user-related billing calculations.

Are you switching from our original pricing plan to New Relic One pricing? Learn about how to convert your users.

User groups

This section applies to New Relic One pricing accounts with users on the New Relic One user model. If you have users on our original user model, see the original user model docs.

For Standard tier accounts: when full users are added, there are additional choices related to account administration. The two user groups available are:

  • Admin: Adding someone to this group lets them use and configure platform features and gives them access to more administrative abilities like editing billing-related settings and managing users.
  • User: Adding someone to this group allows them to use and configure features but not manage users or billing.

Coming soon: Pro and Enterprise tiers include additional admin functionalities and group-related features.

Billing calculations

For user-related billing calculations, see Calculations.

For how to query and alert on usage data, see Query usage data.

Capability limitations

For users on the New Relic One user model, there are some limitations, mainly around API access. For details, see Limitations.

For more help

If you need more help, check out these support and learning resources: