Creating a secured action

You can create new secured actions to secure elements in the Web Client.

Note: The system administrator and users with the appropriate role can access these features. See What are Roles and Secured Actions?

When creating a new secured action, ensure the action has a unique name not previously used (unless you are recovering an accidentally deleted secured action). If you deleted a secured action without manually removing the action from elements in the Application Architect, the new action can give access you do not expect.

For example, you created a secured action named Print or Reports and added that action to multiple Print options (using the Applied Security property in the Application Architect). Then you deleted the Print or Reports secured action but did not manually change the Applied Security property for the Print options. If you create a new secured action named Print or Reports, all the Print options formerly attached to the Print or Reports action, link to the new Print or Reports action.

The application recommends using a descriptive name for the secured actions that can be used to track the action intended purpose. For example, the Entity or Account or Delete secured action is used to control elements that allow users to delete accounts. This naming structure is recommended, but not enforced. The secured action name is a string value and any naming convention can be used.

To create:

Select New Secured Action from the Administration menu.
Specify the secured action name in the Secured Action field.
Specify descriptive information about the secured action in the Description field.
Click Save to save the secured action or Save and New to save the secured action and create another.
Note: You can:
- Use the Roles tab to add the secured action to a role. See Working with the Roles tab
- Use the Locations tab to view where the secured action is used. See Locations tab