• Log inStart now

User type: basic, core, and full platform users

In this doc you'll learn how we define user type, what capabilities each user type has, and how to decide on a user type.

Want to learn about how users are calculated for billing purposes? See New Relic pricing. If you haven't already, be sure to sign up for a New Relic account. It's free, forever.

What's the "user type"?

A user's user type is what determines the set of New Relic capabilities a user can theoretically access. A user's user type takes precedence and overrides any role-related restrictions. (Learn more about factors that affect user access.)

There are three user types:

  • Basic user: several basic but powerful New Relic platform capabilities.
  • Core user (limited availability): has more capabilities than a basic user.
  • Full platform user: all capabilities.

To skip to learning more about capabilities, see Capabilities. To learn more about the user type concept, keep reading.

On our usage-based pricing, basic users are free, and core users and full platform users are billable. Because user count is a billing factor, it's important to understand how user billing calculation works.

If you're tasked with adding New Relic users, one of the key decisions to make is what user type to make them. If you're not sure at first, you can add them as basic users and later decide which users you want to upgrade. For how to adjust user type, see Manage user type.

The user type is meant to be a fairly long-term setting based on a user's expected New Relic responsibilities over the next several months or longer. That intention is reflected in our billing calculations and downgrade rules. For more frequent or more granular adjustments to a user's access, you should use roles.

Overview of user type capabilities

Here's an overview of the capabilities of each user type:

Basic user

Core user (limited availability)

Full platform user

Basic users are free and you can have an unlimited number of them. They can set up New Relic observability tools, run queries of your data, create charts and dashboards, use some basic alerting features, and more.

For more detail, see the complete capabilities table.

Core users can access more features than basic users but less than full platform users. They have access to some powerful developer-centric features like New Relic CodeStream, our Logs UI, and the ability to build New Relic apps.

For more detail, see the complete capabilities table.

Full platform users can access everything, including our more curated observability UI experiences, such as APM, infrastructure monitoring, browser monitoring, mobile monitoring, synthetic monitors, and more.

For more details, see the complete capabilities table.

Remember that the user type overrides any role-related permissions.

Want to understand how billing works? See User billing calculation.

How to pick a user type

For organizations on our usage-based pricing, user type is a factor in billing. Before deciding on user types, you'll want to ensure you understand user-related calculations and downgrade rules. For an in-depth capability comparison, see the Capability table.

Here are some tips for deciding on a user type:

Reasons to make someone a full platform 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 (for example, version control systems, and implementation of CI/CD).
  • They need full access to our platform: They need to use New Relic's curated dashboards and experiences (not just the ability to create their own custom queries and charts).
  • They need to be able to manage users and/or billing.

Reasons to make someone a core user:

  • They're developers who aren't tasked with reliability and uptime as their primary responsibility.
  • They don't require full platform access, but would benefit from some of the specific functionalities offered to core users, like:

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 tools to get data into New Relic, 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 don't 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 or billing.

Detailed user type comparison table

Here's a detailed comparison of capabilities by user type.

Important points about this table:

  • The user type is meant to be a long-term setting. User-type-related restrictions override role-based permissions. Learn more about user access factors.
  • Many of the features in the table refer to access to the UI experiences, not to the underlying data itself. All users, including basic users, can query all data in the accounts they have access to, and can create and view custom charts. Put another way: basic users can access APM data, browser monitoring data, and more, but they don't have access to our curated UI experiences.

For tips on why you'd choose one user type versus another, see Decide on user type.

Access to...

Basic user

Core user (see availability)

Full platform user

Unlimited queries

Custom charts and dashboards

Report data from any source (agents, integrations, APIs)

Log management

Search/view only1

New Relic Instant Observability and quickstarts

Limited access1

Limited access1

Alerts and applied intelligence

(not advanced features1)

(not advanced features1)

New Relic Explorer with Lookout and Navigator

List view only

(except deviating signals)

NerdGraph (our GraphQL API)

(for permitted features1)

(for permitted features1)

New Relic CodeStream integration

Errors tracking with errors inbox

New Relic custom apps

Admin settings (managing billing, managing users)

Application performance monitoring (APM)

OpenTelemetry monitoring

Kubernetes monitoring and Pixie

Infrastructure monitoring

Distributed tracing

Service level management

Infinite Tracing (Pro & Enterprise editions only)

Network performance monitoring (NPM)

Browser and mobile monitoring

Synthetic monitoring

Serverless monitoring

Entity maps and service maps

Workloads

1Here are more details about how user type access works for some features:

Manage user type and upgrade requests

How you manage a user's user type depends on which user model your organization's users are on:

For rules around billing and downgrading users, see Billing and downgrade rules.

Learn how user type relates to roles

For an explanation of how the concept of user type relates to our roles, see User management concepts.

Lacking access to something?

For questions related to lack of access to New Relic accounts or features, see Factors affecting access.

Copyright © 2022 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.