Differences

This shows you the differences between two versions of the page.

--- certna:apex_managing_roles [2020/03/24 19:04] – brett.zamora
+++ certna:apex_managing_roles [2020/03/26 22:31] (current) – brett.zamora
@@ Line 1: / Line 1: @@
 ==== Manage Roles ====
-Functionality in APEX is controlled through a series of Role and Permission definitions. Role definitions are found in the ROLES table, which contains 2 fields, the ROLE_ID and the ROLE_NAME.
+Functionality in APEX is controlled through a series of Role and Permission definitions. This framework is tremendously powerful and it allows APEX to be configured to support a wide variety of needs.
-APEX does not have a UI for role creation because any new role record would be created with a database script along with its corresponding permissions during a standard APEX update deployment.
+You can click this link for more detailed information about [[certna:apex_roles_permissions|APEX Roles & Permissions]].
-The following roles are currently defined in the CeRTNA ERDS/G2G system:
+To manage Roles you must login to a user that has been assigned a System Administrator role. Once you are signed into APEX as a System Administrator you will be presented with the following System Administrator view:
+{{:certna:images:manage_roles-01.png|}}
+To update the permissions for a role, click the Manage Roles option on the Administration tab. The following screen will be displayed:
+{{:certna:images:manage_roles-02.png|}}
+Select the role that you want to set permissions for. Permissions are enabled when the box for a selected row is checked and the permissions are disabled if the box is unchecked. click the desired permission and then click the Save Role/Permissons Mappings button.
+You can also back out of any changes that you have made by clicking the Discard Role/Permission Mappings button.
+For more detailed information about Roles & Permissions [[certna:apex_roles_permissions|click here]].
-{{tablelayout?colwidth="100px,200px,300px"&rowsFixed=1&rowsVisible=6&float=center}}
-^ ROLE_ID ^ ROLE_NAME ^ DESCRIPTION ^
-| 1 | Submitter User | A role that is able to submit transactions for electronic recording. |
-| 2 | County User | A role for county-side non-administrative functions. |
-| 4 | System Administrator | A role with full access to the ERDS/G2G system. |
-| 8 | Security Administrator | Defined but not used in the ERDS/G2G system. |
-| 16 | Submitter/User Administrator | Defined but not used in the ERDS/G2G system. |
-| 32 | County Administrator | A role county-side user and admin functions. |
-| 64 | System Alert Recipient | Defined but not used in the ERDS/G2G system. |
-| 128 | Submitter Developer | A role the emulates a submitter user but also has access to developer tools. |
-| 256 | County Developer | A role that emulates a county administrator user but also has access to developer tools. |
-| 512 | County Public Service User | A role for accessing county oriented web services. |
-| 1024 | Agent Public Service User | A role for accessing submitter oriented web services. |
-| 2048 | Payload Service User | A role setup for server-side server-side sending/retrieving/returning of transactions. |
-| 4096 | Service Submitter User | A role to facilitate submitter remote folders support. |
-| 8192 | Service County User | A role to facilitate county user remote folders support. |
-| 16384 | Service County Administrator | A role to facilitate county administrator remote folders support. |