Defining GL Account Security
Using GL account security, you can restrict who can create transactions in operational functions that update GL accounts based on user ID or role.
Use GL Account Security Maintenance (36.3.13.1) to assign users or roles to account numbers. Use the GL Account Security Report (36.3.13.2) to list all accounts that have controlled access.
GL Account Security Maintenance (36.3.13.1)
When a user attempts to create an operational transaction affecting an account, the system checks to see if account security is defined. If it is, the system verifies that the user ID and roles associated with the user are found on the list associated with the account. If a match is not found, a message displays and the user cannot complete the transaction.
If no account security has been defined, all users and roles are permitted to update the account, within the parameters of other restrictions.
Note: Account security is not applied during Operational Transaction Post (25.13.7) or Invoice Post and Print (7.13.4). Use Role Permissions Maintain to restrict posting functions.
