Permissions

This panel lets you configure permissions (also known as “functional permissions”) for individual users which override those configured for groups (see Adding or Modifying a Group). The permissions displayed in this screen are only those of for the selected, individual user. To see the combined group and user permissions, see the All Permissions panel.

Figure 16-4  Functional Permissions

[spacer]

Configure permissions by checking the actions that appear in the row with the permission. These determine a user’s capabilities within the application.

[spacer]

The description in the lower panel also may indicate additional dependencies to take into account when configuring your permissions.

Generally, the following describes the effects of enabling these actions:.

Action

Default Behavior

read

When checked, this enables the Edit menu item on the action menu.

write

When checked, this enables the Save button within editors.

execute

When checked, this action lets you launch a particular manager and query for elements. Alternatively this action can control a specific application function, (typically described by the permission name) like provisioning a policy

add

This enables the New menu item on the action menu. If you do not check this action, then the New menu item does not appear.

delete

When checked, this enables the Delete menu item on the action menu within managers.

The functional permissions that use these actions--and their descriptions--appear in this screen. The description appears at the bottom of the screen when you select a permission’s row.

You can click individual checkboxes classified by the columns for listed functional permissions’ rows, or Ctrl+click to select entire rows or ranges of rows, and click the Select or Deselect buttons to check or uncheck all the actions in the row(s) selected.

Functional Permission Descriptions

You can configure the Functional Permission labels and descriptions that appear at the bottom of the Permissions screen (but not in the All Permissions screen). Do this in the rcmsgs.properties file in owareapps\redcell\lib. Messages there appear in two lines, configuring the label for the permission, and its description. For example:

Permission-AC.AdaptiveCLI.1=Adaptive CLI

Permission-AC.AdaptiveCLI.2=Adaptive CLI Editor and Manager Permissions

To alter either the label for a permission (line 1) or its description (line 2) simply edit this file with your favorite text editor, save it, then restart application server.

[spacer]

Entries cannot contain special characters, and must be on a single line.

[spacer]

Functional permissions are cached on the client. Changes to permissions may take, by default, up to five minutes to be reflected on a running client.