anchor.diff:  
   Associating a template with a notification requires the `notifications.manage` scope.
   
  -<pre class='terminal'>
  -$ uaac curl https://notifications.user.example.com/clients/notifications-admin/notifications/system-going-down/template \
  +```
  +uaac curl https://notifications.user.example.com/clients/notifications-admin/notifications/system-going-down/template \
   -X PUT --data '{"template": "E3710280-954B-4147-B7E2-AF5BF62772B5"}'
  -</pre>
  +```
   
   Any notification that does not have a custom template applied, such as `system-up`, defaults to a system-provided template.
   
  
positive.code: * A UAA scope
  * An email address
  
  For more information, see the [Notifications V1 Documentation](https://github.com/cloudfoundry-incubator/notifications/blob/master/V1_API.md) on GitHub.
  
  The following example sends the `system-going-down` notification described above to all users in the system:
  
  <pre class='terminal'>
  $ uaac curl https://notifications.user.example.com/everyone -X POST --data \
  '{"kind_id":"system-going-down","text":"The system is going down while we upgrade our storage","html":"<strong>THE SYSTEM IS DOWN</strong><p>The system is going down while we upgrade our storage</p>","subject":"Upgrade to Storage","reply_to":"no-reply@example.com"}'
  </pre>
  
negative.code: 
  A template is made up of a name, a subject, a text representation of the template you are sending for mail clients that do not support HTML, and an HTML version of the template. 
  
  The system provides a default template for all notifications, but you can create a custom template by running: 
  
  ```
  uaac curl https://notifications.user.example.com/templates -X POST --data \
  '{"name":"site-maintenance","subject":"Maintenance: {{.Subject}}","text":"The site has gone down for maintenance. More information to follow {{.Text}}","html":"<p>The site has gone down for maintenance. More information to follow {{.HTML}}"}'
  ```
  
  Variables that take the form `{{.}}` interpolate data provided in the send step before a notification is sent. Data that you can insert into a template during the send step include `{{.Text}}`, `{{.HTML}}`, and `{{.Subject}}`.
  
  This `curl` command returns a unique template ID that can be used in subsequent calls to refer to your custom template. The result looks similar to:
  
  ```
  {"template-id": "E3710280-954B-4147-B7E2-AF5BF62772B5"}
  ```
  
  Check all of your saved templates by running:
  
  ```
  uaac curl https://notifications.user.example.com/templates -X GET
  ```
  
  
  ## <a id='associate'></a> Associate a Custom Template with a Notification
  