• /
  • ログイン
  • 無料アカウント

Introduction to New Relic user management

New Relic has two user models: an older user model referred to as the original user model and a newer one, released in July of 2020, called the New Relic One user model.

Find the docs you need

The user model you're on affects how you manage your users and their access to roles and accounts (read about the user model differences). We have different sets of docs for the two user models:

Not sure which user model you're on? See Determine user model.

User management UI

For how to use the user management UI:

Not sure which user model you're on? See Determine user model.

Determine your user model

When you log in to New Relic, the user record associated with that login is on either one user model or the other. To determine what user model you're on, from the account dropdown select User preferences. If you see the UI below, you're on the New Relic One user model. If you see a different UI with more content displayed, you're on the original user model (see original user docs).

New Relic One user model - user preferences

To determine if you can manage users on the New Relic One user model, see Manage users.

The user model is independent of your pricing model. For how user model relates to pricing, see the Pricing and user model table.

User model comparison

When you log in to New Relic, the user record associated with your login is on either one user model or the other. Here's an explanation of the differences between the user models:

  • New Relic One user model (see docs): this newer, improved user model was released in July 2020. It's the default user model for new New Relic sign ups. Here are the major differences from the original user model:
    • All your accounts and users are contained under a top-level organization. This gives an organization stronger control over managing users and what they can access. One impact of this is that users who work with multiple New Relic organizations may have an email address associated with multiple logins.
    • Users on this model have a different system for managing permissions and account access. Using access grants, you assign users access to specific roles on specific accounts.
  • Original user model (see docs): some aspects of this older model that are different from our newer model:
    • There wasn't as much organization-level control over users. For example, a New Relic user had the ability to access multiple accounts they'd been granted access to using a single login.
    • Users on the original user model have a different user management system.

To learn more about benefits of the new model, see our blog post about user model changes and an explanation of the new account structure. For impacts and limitations, see Feature impacts.

Requirements for New Relic One user model

Here are the factors governing which organizations have users on the newer model:

  • All New Relic organizations that signed up after July 30 2020 have users on this model (and also have the new pricing model).
  • Some older New Relic organizations have had their users migrated to the new model by New Relic or by using the user migration procedure.
  • Partner accounts (resellers, managed service providers), and organizations using the partnership account structure, cannot yet migrate their users to the new model.

Feature impacts of user model

The new user model offers many benefits. Here are some feature impacts of being on the New Relic One user model that may be not obvious to users accustomed to our previous user model:

  • More separation of organizations/accounts: If you have an email address associated with multiple New Relic accounts, this may mean you need to log out and log back in. Learn more about account access.
  • Adding accounts: Pro and Enterprise edition can have more than one account in their organization. Currently users in these organizations cannot, on their own, add accounts. They must get help from their New Relic account representative. To learn about adding users to accounts, see Manage users.
  • Alerts-related impacts:
    • Policy actions: For alert policies and conditions, some UI locations display the user that made the last modification. For users on the new model, it will display their user ID and not their user name. For example, a policy might read Last modified Sep 7, '20 4:26 pm by user 1234567 instead of by John Doe. If you have user management permissions, you can determine what user this is by going to the User management UI.
    • Notifications: Users on the new model won’t show up as an option when choosing users to receive alert notifications. The result of this is that these users will not get New Relic mobile app push notifications. As a workaround, you can instead use their email address as the notification channel.
  • You can't use the REST API to generate a list of users (only original model users). Instead you'd use the user management UI.
  • Changing account name: These users cannot change the name of their organization after it has been created.

Relation between user model and pricing model

The user model isn't directly related to our two pricing models. For information about how these relate, see Pricing model and user model.

問題を作成する
Copyright © 2022 New Relic Inc.