Plex Security
Autor: docakitty • February 22, 2013 • Case Study • 409 Words (2 Pages) • 1,112 Views
Currently Plex offers security permission setting on the Base Account of the Chart of Accounts GL code structure. This restricted access blocks access to GL account information within the accounting module to all users without granted permission access as defined in the User’s permissions setting. Security settings are a fundamental function in most software, so to find that Plex does not have security permission setting across all of the modules is a concern.
What we have found is that even though GL accounts are restricted, this only applies to accounting functions such as Accounts Payables and Financial Reports such as Income Statement and Trail Balance and various accounting reports such as Account Activity. They are not restricted in the Accounting Job module.
The company primarily uses project accounting based reporting company-wide for financial information. So the use of Accounting Jobs is instrumental in reviewing budgets and expenditures on a project by project level. Each project is assigned to a budget owner’s who is responsible for ensuring correct allocation of expenses and justification of expenses exceeding budgets. Therefore, they need to have information at a summary level and also have the ability to drill down on the details of a given transaction.
Accounts that we have masked for confidentiality purposes have been set up under specific accounting jobs, so that the budget owner of those accounts can manage their activities. As an example, we have all GL Accounts associated for legal matters assigned to accounting job: Legal. Another example, we have payroll, recruiting, and personnel GL accounts assigned to accounting job: Personnel
Plex has offered several options that require 200+ hours of programming on their part and one option that may require 40-50 hours of programming in order to provide security permission setting in the Accounting Job Modules.
Ideally,
...