Permissions in the RES_PERM database table
Resource permissions are stored in the RES_PERM database table and are common to all applications you are
granting permissions to. The following table lists some example actions, the resources targeted by these
actions, and the corresponding permission information for each resource, as entered in the database.
| The action and resource to grant resource permissions for. | RES_PERM database table column values | ||||
|---|---|---|---|---|---|
| Action | Resource | ID | TYPE | RESOURCE | PERMISSION |
| View | Alerts | 1 | GUI | all_alerts | view |
| View | Mappers | 2 | GUI | mapper | view |
| View | Transactions | 3 | GUI | transaction | view |
| View | Configuration Values | 4 | GUI | value | view |
| View | Formats | 5 | GUI | format | view |
| View | Actions | 6 | GUI | resolution_action | view |
| Cancel | The resolution action called cancel for an invalid batch (state S_BatValidationFail). Requires view permission on the resolution_action resource. | 7 | RES_ACT | S_BatValidationFail | Cancel |
|
Configuration values category Cat1. For more information about defining permissions for this resource, see Permissions for resource type VAL_CAT. |
8 | GUI | value | val_cat |
| Create | 9 | VAL_CAT | Cat1 | create | |
| Edit | 10 | VAL_CAT | Cat1 | edit | |
| Delete | 11 | VAL_CAT | Cat1 | delete | |
| Create | Formats | 12 | GUI | format | create |
| Edit | 13 | GUI | format | edit | |
| Delete | 14 | GUI | format | delete | |
| Create | Mappers | 15 | GUI | mapper | create |
| Edit | 16 | GUI | mapper | edit | |
| Delete | 17 | GUI | mapper | delete | |