From the User Manager, use the view selector to select the Permissions Browser, as shown in Figure 266. By default, the Permissions Browser shows the three object types collapsed into just three rows in the tree: station (components), file, and history.
As needed, expand and contract the object tree to find objects that have been explicitly assigned into one or more categories, and scroll across to see each user’s permissions for those objects.
Again, displayed row color provides the same data as in the Category Browser, where:
-
Yellow rows are objects explicitly assigned into one or more categories.
-
Dimmed rows represent objects inheriting their parent’s category or categories.
You can also use Show Configured to automatically fully expand the tree.
In the Permissions Browser, select -> from the menu, or click the 
icon, as shown as shown in Figure 295. The PermissionsBrowser tree expands to show all explicitly assigned objects.
In each cell intersecting a user (column) and object (row), that user’s permissions are shown with abbreviations—see Permissions abbreviations. For any user, you can access permissions.
Permissions for each object are shown in each of the user columns using abbreviations (Figure 295).
Full permissions are “rwiRWI”, where the capital RWI is for admin-level Read, Write, Invoke. It is possible for a user to have no permissions for some objects (blank cell), if those objects are assigned to a
category the user does not even have operator read “r” permissions for. See About permission levels for more details.
Double-click anywhere in a column to access a user’s permissions. This produces the same Permissions dialog as from the user’s properties, only user name shows in the window title bar (Figure 297).
If you double-click on any user with “super user” rights, a popup warning reminds you that you cannot modify permissions,
as shown in Figure 298.
If you could see the permission map for any super user, it would simply be all possible permissions checked for all possible categories (rows).
As shown in Figure 299, remember to 
after making any user permissions changes.
