RE: need to restrict approval of GL entries
The point is that there are three types of securities to be considered;
- Account Level Security: to manage the security of accounts
- Security Roles and Types: to manage the security of windows
- Field Level Security: to manage the security for fields
Just to add further illustration, You could consider the "Account Level Security" to manage the accounts permission based on an organizational chart you configure, for instance:
- AP Manager
- AR Manager
- Costing Manager
- Fixed Assets Manager
- Treasury Manager
Once you draw your own business chart, you can consider the capability of "Security Roles and Tasks" in order to grant posting permissions, as explained above by Mr. Joshua
Finally, you could consider the "Field Level Security" in order to dig into further requirements regarding specific piece of details, which can be well managed under this category.
It's worth commenting upon one point mentioned which is "
@JOESYFEEN: Example, I'll be creating a transaction but I cannot approve it. However, I can approve transactions created by other user"
Of course you can create transactions and can't approve it (for instance AP Accountant). Someone else such as (AP Supervisor or AP Manager) can approve and post the transactions you entered.
On the other hand, if you approve and post transactions for other users, this mean you have access on their accounts, and can still enter transactions on these accounts.
Let us know if this help you figure out how to manager your business case.
Your feedback is highly appreciated.
Share
Report
100
All responses (
Answers (
