DokuWiki

This is an old revision of the document!

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.

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.

The following roles are currently defined in the CeRTNA ERDS/G2G system:

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.