anchor.diff:  1. Create a `notifications-admin` client with the required scopes by running:
   
       ```
  -    uaac client add notifications-admin --authorized\_grant\_types client\_credentials --authorities \
  -        notifications.manage,notifications.write,notification\_templates.write,notification\_templates.read,critical\_notifications.write
  +    uaac client add notifications-admin --authorized_grant_types client_credentials --authorities \
  +       notifications.manage,notifications.write,notification_templates.write,notification_templates.read,critical_notifications.write
       ```
  -    * `notifications.write`: Send a notification. For example, you can send notifications to a user, space, or everyone in the system.
  +    * `notifications.write`: Send a notification. For example, you can send notifications to a
  +      user, space, or everyone in the system.
       * `notifications.manage`: Update notifications and assign templates for that notification.
       * (Optional) `notification_templates.write`: Create a custom template for a notification.
       * (Optional) `notification_templates.read`: Check which templates are saved in the database.
  
positive.code: owner: Notifications
  ---
  
  This topic describes how to use the Notifications Service, including how to create a client, obtain a token, register notifications, create a custom template, and send notifications to your users.
  
  <%= vars.notifications_api_1 %>
  
  
  ## <a id='prereqs'></a> Prerequisites
  
  
negative.code: uaac curl https://notifications.user.example.com/templates -X GET
  ```
  
  ## <a id='associate'></a> Associate a Custom Template with a Notification
  
  In this example, the `system-going-down` notification belonging to the `notifications-admin` client
  is associated with the template ID `E3710280-954B-4147-B7E2-AF5BF62772B5`. This is the template ID
  of the template we created in the previous section.
  
  Associating a template with a notification requires the `notifications.manage` scope.
  
  