Matrix-based security and Project-based Matrix Authorization Strategy are provided by the plugin:matrix-auth[Matrix Authorization Strategy Plugin] and may not be installed on your Jenkins. For most Jenkins environments, Matrix-based security provides the most security and flexibility so it is recommended as a starting point for "production" environments. The table shown above can get quite wide as each column represents a permission provided by Jenkins core or a plugin. Hovering the mouse over a permission will display more information about the permission. Each row in the table represents a user or group (also known as a "role"). This includes special entries named "anonymous" and "authenticated." The "anonymous" entry represents permissions granted to all unauthenticated users accessing the Jenkins environment. Whereas "authenticated' can be used to grant permissions to all authenticated users accessing the environment. The permissions granted in the matrix are additive. For example, if a user "kohsuke" is in the groups "developers" and "administrators", then the permissions granted to "kohsuke" will be a union of all those permissions granted to "kohsuke", "developers", "administrators", "authenticated", and "anonymous." Jenkins allows user-input in a number of different configuration fields and text areas which can lead to users inadvertently, or maliciously, inserting unsafe HTML and/or JavaScript. By default the  Markup Formatter  configuration is set to  Plain Text  which will escape unsafe characters such as  <  and  &  to their respective character entities. Using the  Safe HTML  Markup Formatter allows for users and administrators to inject useful and information HTML snippets into Project Descriptions and elsewhere. 151 Markup Formatter NOTE Figure 2. Matrix-based security