From 7928fff27bf32ffed67dc8487bd9344bd3f6828d Mon Sep 17 00:00:00 2001 From: ZuluEcho9 Date: Fri, 13 May 2022 14:54:21 -0700 Subject: [PATCH] fix(add accounts): adding new UI ability --- .../account-structure/add-accounts.mdx | 13 +- ...factors-affecting-access-features-data.mdx | 2 +- .../new-relic-account-structure.mdx | 2 +- .../account-user-mgmt-tutorial.mdx | 11 +- ...-groups-roles-new-relic-one-user-model.mdx | 205 ----------------- .../overview-user-models.mdx | 1 - .../examples/manage-accounts-nerdgraph.mdx | 6 +- ...-groups-roles-new-relic-one-user-model.mdx | 217 ------------------ ...-groups-roles-new-relic-one-user-model.mdx | 217 ------------------ 9 files changed, 18 insertions(+), 656 deletions(-) delete mode 100644 src/content/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model.mdx delete mode 100644 src/i18n/content/jp/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model.mdx delete mode 100644 src/i18n/content/kr/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model.mdx diff --git a/src/content/docs/accounts/accounts-billing/account-structure/add-accounts.mdx b/src/content/docs/accounts/accounts-billing/account-structure/add-accounts.mdx index a452a7dd89d..8a46b884af4 100644 --- a/src/content/docs/accounts/accounts-billing/account-structure/add-accounts.mdx +++ b/src/content/docs/accounts/accounts-billing/account-structure/add-accounts.mdx @@ -5,12 +5,13 @@ translate: metaDescription: How to add accounts to your New Relic organization. --- -How you add accounts to your New Relic organization depends on the type of [user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-user-models) your users are on: +Some New Relic organizations have the ability to add more accounts to their organization. For why you'd want to do this, see [Organization structure](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure). -* New Relic One user model: here are some relevant docs: - * [Add and rename accounts via our NerdGraph API.](/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph) - * To learn about the structure of your New Relic organization, see [Organization structure](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure). -* Original user model: see [Add accounts](/docs/accounts/original-accounts-billing/original-users-roles/parent-child-account-structure/#creating). +How you add accounts to your New Relic organization depends on the type of [user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-user-models) your users are on: +* New Relic One user model: + * To add an account from the UI: from the [**Organization and access** UI page](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-ui-and-tasks#where), click **Accounts**, and then click **Create account**. + * To add an account via API: see [Manage accounts with NerdGraph](/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph). + * To learn about organization and account structure, see [Organization structure](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure). +* Original user model: see [Add accounts](/docs/accounts/original-accounts-billing/original-users-roles/parent-child-account-structure/#creating). -Want to determine which you're on? See [Determine user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models/#determine-user-model). diff --git a/src/content/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data.mdx b/src/content/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data.mdx index 96cc6a9db96..c6c4fb9123f 100644 --- a/src/content/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data.mdx +++ b/src/content/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data.mdx @@ -40,7 +40,7 @@ Potential permissions-related factors that can affect your access: We have two pricing models available, and this can impact feature availability: * Our [New Relic One pricing model](/docs/new-relic-one-pricing-billing): This newer pricing model gives users broad cross-platform access. For this pricing model, the main factors affecting access are your organization's [edition](https://newrelic.com/pricing) and a user's [permissions](#user-permissions). -* Our original [product-based pricing model](/docs/accounts/original-accounts-billing/product-pricing/product-based-pricing): This plan separates our offerings by product. If you’re on this plan, access to some features may depend on the products you pay for. +* Our original [product-based pricing model](/docs/accounts/original-accounts-billing/product-pricing/product-based-pricing): This plan separates our offerings by product. If you're on this plan, access to some features may depend on the products you pay for. We also have three [pricing editions](https://newrelic.com/pricing): Standard, Pro, and Enterprise. Some features are only available to Pro or Enterprise edition organizations: those features are mostly related to higher-level account administration (like the ability to add accounts to an organization). diff --git a/src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx b/src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx index 6291a3787e3..8f9896493a5 100644 --- a/src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx +++ b/src/content/docs/accounts/accounts-billing/account-structure/new-relic-account-structure.mdx @@ -26,7 +26,7 @@ Why an organization creates new accounts depends on their goals and structure. T Each account in an organization has its own [account ID](/docs/accounts/accounts-billing/account-setup/account-id), and that ID is used for some account-specific tasks, like making API calls. -To add and rename accounts, you can [use our NerdGraph API](/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph) (UI features coming soon). +To add and rename accounts, see [Add accounts](/docs/accounts/accounts-billing/account-structure/add-accounts). ### How users access accounts [#account-access] diff --git a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial.mdx b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial.mdx index 3759e25fac2..4711edd6e58 100644 --- a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial.mdx +++ b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial.mdx @@ -23,7 +23,6 @@ Before you start this tutorial, some things to understand: * This tutorial presents one recommended workflow but there are many ways to do these steps and no particular order of steps is necessary. * For an example spreadsheet showing how one might plan out your users' roles and account access, see the [Access grant planning spreadsheet](https://docs.google.com/spreadsheets/d/1FnguDXRUX9FGY14oV4Gx6O08v4vNC2Pv0GGCsU7Pxuw/edit?usp=sharing). - ## Overview [#overview] This tutorial will walk you through: @@ -39,7 +38,7 @@ This tutorial will walk you through: If you're reading this, you likely already have a New Relic organization. When you [sign up for New Relic](https://newrelic.com/signup), your New Relic organization is created. The organization structure represents a New Relic customer: it's what contains everything relevant to a customer's use of New Relic: their accounts, their users, and their data. -When a New Relic organization is created, it contains a single account. A Standard edition organization can only have a single account, but Pro and Enterprise edition organizations can add more accounts. An account can be considered a workspace. For example, you might have an account for a specific app, or a set of related hosts and services for a specific initiative or project. Each account has its own [account ID](/docs/accounts/accounts-billing/account-structure/account-id), and that ID is used for some account-specific tasks, like making API calls. +When a New Relic organization is created, it contains a single account. A Standard edition organization can only have a single account, but Pro and Enterprise edition organizations can add more accounts. Each account has its own [account ID](/docs/accounts/accounts-billing/account-structure/account-id), and that ID is used for some account-specific tasks, like making API calls. When your organization is created, it has several default "access grants," which grant the two available default groups access to specific roles, and a specific scope of accounts. When you add users via the UI, there are two default groups that you can assign your users to: @@ -60,11 +59,11 @@ Pro and Enterprise edition organizations are able to add custom groups, or bring ## Step 2: Add accounts [#add-accounts] -Before adding your users in New Relic, you might want to set up some accounts and [get some data reporting](/docs/using-new-relic/welcome-new-relic/get-started/get-started-full-stack-observability) to them. All of that isn't required at this point (you can always add more accounts later and grant users access to them later) but for the purposes of this tutorial, we'll walk you through adding accounts. +Before adding your users in New Relic, you might want to [get some data reporting](/docs/using-new-relic/welcome-new-relic/get-started/get-started-full-stack-observability) and set up additional accounts. This isn't required at this point: you can always set up accounts and get data reporting later, and adjust your users' access after that. -As covered in Step #1, an account is meant to represent a workspace of some sort. It's a useful way to separate your use of New Relic by business-relevant boundaries. An account can have a large amount and variety of data reporting to it. There's nothing preventing even quite large companies from having a single account or just a handful of accounts. It's all really a matter of what your organization's goals are and how useful you find it to create the account boundaries. +For guidance on why an organization should create more accounts, see [Organization structure](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure/#new-model). -To manage accounts: [use our NerdGraph API to view, add, and rename accounts](/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph). The ability to add accounts via the UI is coming soon. When you're done adding accounts, return to continue this tutorial. +If you did want to create accounts at this point, see [Add accounts](/docs/accounts/accounts-billing/account-structure/add-accounts). ## Step 3: Set up authentication domains [#auth-domains] @@ -190,7 +189,7 @@ Suggested steps for adding users: 2. Optional: select your authentication domain using the switcher in the top left. (Remember that groups reside within the boundaries of an authentication domain). 3. To add a user, click **Add user**. Complete the prompts in the UI, including choosing the [user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type) and group. Any custom groups you’ve added should be available from the group dropdown. If the custom group you choose has had an access grant created for it, once you add the user to that group, that user will have access. -To edit a user’s group or other details: click on the user you want to edit and make changes. For tips on bulk editing and other common tasks, see [Common user management tasks](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-ui-and-tasks#workflow). +To edit a user's group or other details: click on the user you want to edit and make changes. For tips on bulk editing and other common tasks, see [Common user management tasks](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-ui-and-tasks#workflow). Once your users are added, remember that you have the option of using our API to add and remove users from groups: see [NerdGraph user management](/docs/apis/nerdgraph/examples/nerdgraph-user-mgmt#add-users). diff --git a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model.mdx b/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model.mdx deleted file mode 100644 index 590f03d3d01..00000000000 --- a/src/content/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model.mdx +++ /dev/null @@ -1,205 +0,0 @@ ---- -title: 'A tutorial on setting up accounts, access grants, and users' -metaDescription: A tutorial that will walk you through creating and managing New Relic accounts and users. -redirects: - - /docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model ---- - -import groupAccessUi from 'images/group-access-ui.png' - -import orgAccessUI from 'images/organization-and-access-ui-default-groups.png' - -This tutorial will walk you through adding and managing accounts and users. - -## Before you start [#requirements] - -Before you start this tutorial, some things to understand: -* Pro or Enterprise edition is required (Standard edition can't add accounts or access grants) -* This tutorial is for managing users who are on our [New Relic One user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models). -* This tutorial will be easier if you first have a basic understanding of: - * [Organization and account concepts](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure#new-model) - * [User management concepts](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#understand-concepts) -* This tutorial won't show you all user management functionality. For more complete docs, review the [user management docs](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users). -* This tutorial presents one recommended workflow but there are many ways to do these steps and no particular order of steps is necessary. -* For an example spreadsheet showing how one might plan out your users' roles and account access, see the [Access grant planning spreadsheet](https://docs.google.com/spreadsheets/d/1FnguDXRUX9FGY14oV4Gx6O08v4vNC2Pv0GGCsU7Pxuw/edit?usp=sharing). - -## Overview [#overview] - -This tutorial will walk you through: - -1. [Organization creation](#create-organization) -2. [How to add accounts](#add-accounts) -3. [How to set up an authentication domain](#auth-domains) -4. [How to set up custom roles](#roles) -5. [How to set up access grants](#group-access) (give groups access to roles and accounts) -6. [How to add users](#add-users) - -## Step 1: Organization creation [#create-organization] - -If you're reading this, you likely already have a New Relic organization. When you [sign up for New Relic](https://newrelic.com/signup), your New Relic organization is created. The organization structure represents a New Relic customer: it's what contains everything relevant to a customer's use of New Relic: their accounts, their users, and their data. - -When a New Relic organization is created, it contains a single account. A Standard edition organization can only have a single account, but Pro and Enterprise edition organizations can add more accounts. Each account in an organization has its own [account ID](/docs/accounts/accounts-billing/account-structure/account-id), and that ID is used for some account-specific tasks, like making API calls. - -When your organization is created, it has several default "access grants," which grant the two available default groups access to specific roles, and a specific scope of accounts. When you add users via the UI, there are two default groups that you can assign your users to: - -* **Admin**: can use and configure observability features for that initial account, and the ability to view and configure organization-level settings (like adding accounts or managing users). -* **User**: can use and configure observability features, without the higher level organization capabilities. - -You can see the default access grants created for these groups by going to the **Organization and access** UI: - -New Relic organization and access UI - default access grants - -You can see how the **User** group has the **All product admin** role and access to that initially created account. And you can see how the **Admin** group has four access grants, reflecting its greater capabilities. The "Default" next to those group names refers to them being in the original, default authentication domain (we'll talk more about that later). - -Pro and Enterprise edition organizations are able to add custom groups, or bring in groups from their identity provider. - -## Step 2: Add accounts [#add-accounts] - -Before adding your users in New Relic, you'll probably want to [get some data reporting](/docs/using-new-relic/welcome-new-relic/get-started/get-started-full-stack-observability) and may want to add some accounts. Adding accounts isn't required at this point but for the purposes of this tutorial, we'll walk you through adding accounts. - -For an explanation of why you'd want to add additional accounts, see [Account structure](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure/#new-model). - -To manage accounts: [use our NerdGraph API to view, add, and rename accounts](/docs/apis/nerdgraph/examples/manage-accounts-nerdgraph). The ability to add accounts via the UI is coming soon. When you're done adding accounts, return to continue this tutorial. - -## Step 3: Set up authentication domains [#auth-domains] - -When your organization is first created, the groups and users are located in a default authentication domain, named "Default." An "authentication domain" is a grouping of New Relic users governed by the same user management settings, like how they're provisioned (added and updated), how they're authenticated (logged in), session settings, and how user upgrades are handled. - -The default authentication settings are: -* Users are manually added and managed via the New Relic UI -* Users manually log in to New Relic using their email and password - -Having that one authentication domain might be fine for many organizations, but some organizations want one or both of the following: -* Single sign-on (SAML SSO) -* Managing their users from their identity provider via SCIM provisioning - -And if they want those things, they'll have to create an additional authentication domain. Note that groups and users are contained within authentication domains, and you can't easily change an authentication domain's provisioning setting or authentication setting once the domain is created: this means you should spend some time thinking about what your authentication domain settings should be before you add users to them. - -If you're okay with the default authentication domain (managing your users from New Relic, with your users logging in with their email and password), you can skip to [Step #4](#roles). If you want to use SAML SSO or SCIM provisioning, see these options: - - - -For how to set up SCIM provisioning and SAML SSO, see our [automated user management docs](/docs/accounts/accounts/automated-user-management/automated-user-provisioning-single-sign#how-to). When you're done: - -* Ensure you can see the groups from your identity provider in New Relic's **Organization and access** UI. -* Return here to continue this tutorial. - - - -For how to set up SAML SSO, see the [SSO docs](/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more#authentication). When you're done, return here to continue this tutorial. - - - - -## Step 4. Create custom roles (optional) [#roles] - -We have default-available roles ([standard roles](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts/#roles)), so creating custom roles is optional. If you don't have a need for custom roles, you can skip this step. - -Some tips to help you understand what roles are: -* Users are assigned to groups (for example, the default **Admin** and **User** groups), and those groups are assigned various roles and accounts via what we call "access grants." Put another way: it's not the group that gives users access to New Relic capabilities: it's the roles. -* A role contains various capabilities. For example: the capability to create and modify alert conditions, or the capability to delete data ingest license keys (to see the capabilities in the UI, see [Capabilities](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#capabilities).) -* Unlike groups and users, roles are not contained in an authentication domain: they're available across the entire organization. -* We have several default-available roles, which we call [standard roles](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles). Some of these are assigned to the **Admin** and **User** groups that are available by default. If your organization is Pro or Enterprise edition, you can create your own custom roles. - -For an example spreadsheet showing how one might plan out roles and groups and access grants, see this [Access grant planning spreadsheet](https://docs.google.com/spreadsheets/d/1FnguDXRUX9FGY14oV4Gx6O08v4vNC2Pv0GGCsU7Pxuw/edit?usp=sharing). - -To view existing roles: from the [account dropdown](/docs/using-new-relic/welcome-new-relic/get-started/glossary#account-dropdown), click **Administration**, then click **Organization and access**, and then click **Roles**. - -To create a custom role, click **Add new custom role**. Review the list of available capabilities and decide which ones your custom role needs. - -Here's a short NerdByte video showing how to create a custom role (4:07 minutes): - -