New Relic One gives you access to data from across your organization's accounts. This document explains the benefit of cross-account access and some security-related implications.
Benefits of cross-account access
Some organizations have multiple New Relic accounts with complex account hierarchies. New Relic One makes it easier for these organizations to find the data they need by providing cross-account access. This cross-account access allows you to see information about services, hosts, and other entities from other accounts in your organization.
Some examples of how this cross-account access may help you:
- You can use the primary New Relic One search to find entities, dashboards, and other components from accounts you have access to.
- Your entity explorer includes services and hosts from the accounts you have access to.
- Distributed tracing shows you traces from across your organization, not just from an application-specific view.
For more about similar features, see Introduction to New Relic One.
Like any other New Relic product or service, New Relic One is designed to protect you and your customers' data privacy. For more information about New Relic's security measures, see our security and privacy documentation, or visit the New Relic security website.
In addition, the cross-account nature of New Relic One requires security features that ensure users cannot access data they are not authorized to access. Here are some cross-account security-related features:
- Access based on account hierarchy. Your organization's account hierarchy affects what a user can see. For example, if you have access to a master account, you can see data from that account’s sub-accounts. But if you have access only to a sub-account, then you can see only that sub-account’s data.
- Access based on login authentication. The method used to log in can affect what a user can see. For example, if you use a third-party single sign on (SSO) mechanism, it may not give you simultaneous access to all the New Relic accounts you’re theoretically authorized to access.
- Obfuscation of details for non-authorized accounts. Some features, like distributed tracing and service maps, will show you some basic information about entities from accounts associated with your organization but that you don’t have direct access to. In this case, details about those entities will be obfuscated for security purposes.
For suggestions for gaining more access to other accounts or features, see the New Relic One troubleshooting documentation.