Merge pull request #3238 from kdef-nr/scim-api-corrections

SCIM api corrections
newrelic · Jul 22, 2021 · 3a18cb0 · 3a18cb0
2 parents 5d2dbde + 389d3e5
commit 3a18cb0
Showing 1 changed file with 9 additions and 9 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>
 
@@ -160,7 +160,7 @@ New Relic uses a subset of the available fields in the SCIM core schema. Other S
 
     <tr>
       <td>
-        `members`
+        `groups`
       </td>
 
       <td>
@@ -457,7 +457,7 @@ Supported actions are:
       }],
       "timezone": "America/Los_Angeles",
       "active": true,
-      "members": []
+      "groups": []
     }
     ```
 
@@ -488,7 +488,7 @@ Supported actions are:
         "created": "2019-11-08T22:07:12.477Z",
         "lastModified": "2019-11-08T22:07:12.477Z"
       },
-      "members": []
+      "groups": []
     }
     ```
   </Collapser>
@@ -530,7 +530,7 @@ Supported actions are:
         "created": "2019-11-08T22:07:12.477Z",
         "lastModified": "2019-11-08T22:07:12.477Z"
       },
-      "members": []
+      "groups": []
     }
     ```
   </Collapser>
@@ -577,7 +577,7 @@ Supported actions are:
           "created": "2019-11-08T22:07:12.477Z",
           "lastModified": "2019-11-08T22:07:12.477Z"
         },
-        "members": []
+        "groups": []
       }]
     }
     ```
@@ -587,7 +587,7 @@ Supported actions are:
     id="update-user-put"
     title="Update user with PUT"
   >
-    In the request, include the fields that you want to change. If you include the `members` field, the user’s groups will be adjusted to match the contents of the members field. Example request:
+    In the request, include the fields that you want to change. If you include the `groups` field, the user’s groups will be adjusted to match the contents of the groups field. Example request:
 
     ```
     PUT /Users/<var>YOUR_USER_ID</var>
@@ -630,7 +630,7 @@ Supported actions are:
         "created": "2019-11-08T22:07:12.477Z",
         "lastModified": "2019-11-08T22:28:33.552Z"
       },
-      "members": []
+      "groups": []
     }
     ```
   </Collapser>
@@ -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/)