Download PUBLIC SECTOR SECURITY
Transcript
SECURITY 55 that included any of the folders that made up that particular reporting need. This also accommodates long-term changes such as a new folder being identified as useful to the audit process by only requiring that one role to be modified. The challenge in setting up your security is to find the efficient middle ground between too few roles to accommodate change and too many roles to manage. Since this will vary from client to client there are no hard rules for finding this middle ground. Instead, this document will try to assist you in finding a good match for your needs. Menu Security One of the places where a single role might fulfill multiple security needs is in the area of Menu Security. For example, the act of processing Payroll involves multiple masks. In all likelihood, the masks are almost always granted in a group and a subset of them is rarely required. In this case, it might make perfect sense to create a "Payroll Processing Menu" Security Role that includes all of the IFAS Menu Masks required to complete that activity. Data Access Security Before trying to setup Security Roles on IFAS data it can be useful to break your data security needs into three areas. 1. Common Security Needs Identifying those aspects of your data security needs that can be addressed by Common Security filters is important because these filters have the biggest impact on data access throughout the software. In many cases access to the Common Security items is required to view the data in other tables at all. For example, without access to "Ledger Security" a user is unable to view any data in a table linked to that common item. 2. Individual Table Filters Some of your users will need access to a subset of the data in a particular table. For those tables with links to Common Security items this can be handled with that type of filtering. For some of the IFAS tables individual filters may need to be setup to allow a reduced portion of that data to be accessed based on the role assignments. Its important to identify these needs up front because, based on the concept of Inclusive Security, it is possible for one Security Role to override the filter of another role by providing unfiltered access to the table. 3. Unfiltered Data Access A significant number of the tables in the software are going to fall into this category. In some cases this will be because these tables are storing data that is either already filtered as a result of a Common Security link or your users simply require all or nothing access. For example, the tables storing the HR codes are frequently granted access to anyone with access to the other HR tables without any type of filter. Once you have the list of Data Access security needs grouped based on the type of restrictions they require the next step is to look for logical groupings within those types. For example, in the Vanilla School District the secretaries at each of the schools needed to be able to enter Purchase Requisitions as well as report against, not only their Purchase Requisitions, but the status of payments to vendors. Therefore, in their