anchor.diff:  The ADMIN user should be listed. Click on the pencil icon to see this user's role(s). You may edit the
   roles by selecting the appropriate checkboxes.
   
  -When other users want access to the NiFi UI, they navigate to the configured URL and are
  +The following roles are available in NiFi:
  +
  +[options="header,footer"]
  +|========================================================================================================
  +| Role Name | Description
  +| Administrator | Administrator is able to configure thread pool sizes and user accounts
  +| Data Flow Manager | Data Flow Manager is given the ability to manipulate the dataflow. S/he is able to
  +                      add, remove, and manipulate components on the graph; add, remove, and manipulate
  +                      Controller Services and Reporting Tasks; create and manage templates;
  +                      view statistics; and view the bulletin board.
  +| Read Only | Users with Read Only access are able to view the dataflow but are unable to change anything.
  +| Provenance | Users with Provenance access are able to query the Data Provenance repository and view
  +               the lineage of data. Additionally, this role provides the ability to view or download
  +               the content of a FlowFile from a Provenance event (assuming that the content is still
  +               available in the Content Repository and that the Authority Provider also grants access).
  +               This access is not provided to users with Read Only 
  +               (unless the user has both Read Only and Provenance roles) because the information provided 
  +               to users with this role can potentially be very sensitive in nature, as all FlowFile attributes 
  +               and data are exposed. In order to Replay a Provenance event, a user is required to have both
  +               the Provenance role as well as the Data Flow Manager role.
  +| NiFi | The NiFi Role is intended to be assigned to machines that will interact with an instance of NiFi
  +         via Site-to-Site. This role provides the ability to send data to or retrieve data from Root
  +         Group Ports (but only those that they are given permissions to interact with - see the User Guide
  +         for more information on providing access to specific Ports) as well as obtain information about
  +         which Ports exist. Note that this role allows the client to know only about the Ports that it
  +         has permissions to interact with.
  +| Proxy | The Proxy Role is assigned to a system in order to grant that system permission to make requests
  +          on behalf of a user. For instance, if an HTTP proxy service is used to gain access to the system,
  +          the certificate being used by that service can be given the Proxy Role.
  +|========================================================================================================
  +
  +
  +When users want access to the NiFi UI, they navigate to the configured URL and are
   prompted to request access. When someone has requested access, the ADMIN user sees a star
   on the Users icon in the Management Toolbar, alerting the ADMIN to the fact that a request is
   pending. Upon opening the User Management Page, the pending request is visible, and the ADMIN
  
positive.code: 
  This section provides a quick overview of NiFi Clustering and instructions on how to set up a basic cluster. In the future, we hope to provide supplemental documentation that covers the NiFi Cluster Architecture in depth. 
  
  The design of NiFi clustering is a simple master/slave model where there is a master and one or more slaves. While the model is that of master and slave, if the master dies, the slaves are all instructed to continue operating as they were to ensure the dataflow remains live. The absence of the master simply means new slaves cannot join the cluster and cluster flow changes cannot occur until the master is restored. In NiFi clustering, we call the master the NiFi Cluster Manager (NCM), and the slaves are called Nodes. See a full description of each in the Terminology section below.
  
  *Why Cluster?* +
  
  
negative.code: 
  After the _authorized-users.xml_ file has been edited and saved, restart NiFi.
  Once the application starts, the ADMIN user is
  able to access the UI at the HTTPS URL that is configured in the _nifi.properties_ file.
  
  From the UI, click on the Users icon ( image:iconUsers.png["Users", width=32] ) in the
  Management Toolbar (upper-right corner of the UI), and the User Management Page opens.
  