User.timezone is not actually required; default is UTC

newrelic · Jul 22, 2021 · 73decda · 73decda
1 parent 538555e
commit 73decda
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...s/accounts/automated-user-management/scim-support-automated-user-management.mdx b/...s/accounts/automated-user-management/scim-support-automated-user-management.mdx
@@ -144,7 +144,7 @@ New Relic uses a subset of the available fields in the SCIM core schema. Other S
       </td>
 
       <td>
-        **Required.** Time zone of the user in IANA Time Zone database format, also known as the "Olson" time zone database format (e.g., "America/Los_Angeles").
+        Time zone of the user in IANA Time Zone database format, also known as the "Olson" time zone database format (e.g., "America/Los_Angeles").
       </td>
     </tr>
 
@@ -794,4 +794,4 @@ Users provisioned via your identity provider start out as [full users](/docs/acc
 Once your users are in New Relic, you need to grant them access to specific New Relic accounts, specific groups, and specific roles. Without doing this, your users have no access to New Relic accounts. To learn how to do this, see: 
 
 * [How access grants work](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles#understand-concepts)
-* The [user management tutorial](/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model/) 
+* The [user management tutorial](/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model/)