Merge pull request #19376 from newrelic/NR-293577-domain-capture

Chore(user management): Added domain capture reference

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/account-user-mgmt-tutorial.mdx

@@ -6,7 +6,9 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-This tutorial will walk you through adding and managing accounts and users.
+This tutorial walks you through the steps to add and manage accounts and users.
+
+
 
 ## Before you start [#requirements]
 
@@ -19,9 +21,13 @@ Before you start this tutorial, some things to understand:
   * [User management concepts](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#understand-concepts)
 * This presents one recommended workflow but no particular order of steps is required.
 
+<Callout variant="tip">
+We recommend that you consider implementing [domain capture](/docs/accounts/accounts-billing/account-setup/domain-capture/) that lets you automatically add users to your organization based on their email domain. This prevents users from accidentally signing up for New Relic and creating an unnecessary and unwanted New Relic organization. This feature is available for Pro and Enterprise accounts.
+</Callout>
+
 ## Overview [#overview]
 
-This tutorial will walk you through:
+This tutorial walks you through:
 
 1. [Organization creation](#create-organization)
 2. [How to add accounts](#add-accounts)
@@ -30,6 +36,7 @@ This tutorial will walk you through:
 5. [How to manage group access](#group-access)
 6. [How to add users](#add-users)
 
+
 <Steps>
   <Step>
     ## Organization creation and setup [#create-organization]

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/authentication-domains-saml-sso-scim-more.mdx

@@ -8,11 +8,12 @@ redirects:
 freshnessValidatedDate: 2024-11-08
 ---
 
-
 To manage their users, New Relic organizations can configure one or more authentication domains, which control how users are added to a New Relic account, how they're authenticated, and more.
 
 ## Authentication domains explained [#auth-domain-definition]
 
+
+
 An <DNT>**authentication domain**</DNT> is a grouping of New Relic users governed by the same user management settings, like [how they're provisioned](#source-users) (added and updated) and [how they're authenticated](#authentication) (logged in).
 
 When you create a New Relic organization, the default authentication settings are:
@@ -85,7 +86,8 @@ If you have user records in more than one authentication domain, you can [switch
 ## Source of users: how your users are added and managed [#source-users]
 
 <Callout variant="tip">
-  For an introduction to our SAML SSO and SCIM offerings, please read [Get started with SSO and SCIM](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-saml-scim).
+  * For an introduction to our SAML SSO and SCIM offerings, refer [Get started with SSO and SCIM](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-saml-scim).
+  * We recommend that you consider implementing [domain capture](/docs/accounts/accounts-billing/account-setup/domain-capture/) that lets you automatically add users to your organization based on their email domain. This prevents users from accidentally signing up for New Relic and creating an unnecessary and unwanted New Relic organization. This feature is available for Pro and Enterprise accounts.
 </Callout>
 
 From the [authentication domain UI](#ui), you can set one of two options for the source of your users: