The account or job will not appear on their lookups, and if they enter the account code or job code, Coins ERP+ issues a message informing them that they are not allowed to access it.
Use Job Security and GL Security Maintenance. Memo Security and Employee Security operate in a similar way.
To set up account or job security:
A parameter defines which field on the account or job record is used as the basis of security. For example, security could be based on the job group field, or one of the account analysis sets.
In the security maintenance function, for each user or group, you enter a can-do list of values for that field. The user then has access to all accounts or jobs on which the security field matches the list.
For example, if job security is based on the job group field, an entry of !CIVIL,* allows the user access to all jobs except those belonging to the group CIVIL.
šNote: You can also set up security for an individual user, across all companies, from within the userās record in User Workbench. Click the Security tab menu, and choose the appropriate item.
For example, to allow the user access to all jobs belonging to the group CIVIL except job 1652, enter CIVIL in the Security List frame and !1652 in the Code frame.
You can also specify a can-do list of individual accounts or jobs that you want to grant or deny the user access to.
If you change the security control field, or decide to implement security after the records (for example, the jobs or GL accounts) have already been set up, you need to regenerate the security file.
To regenerate the security file:
Go to the appropriate Re-generate Security function (for example, Re-generate GL Account Security or Job Security).
check the Continue? box and click
. Coins ERP+ re-generates security based on the new control field.
Parameters
GL/ACCTSEC - Account Security Field
JC/COSECDEF - Default contract security when blank to NONE
JC/JOBSEC - Contract Security Field