Logging in to the application
Users log into the Springbrook application using the same username and password they use to log into the network of your organization. A user account must still be created in the Springbrook application using the same username set up on the security of the network (SS> Maintenance> User), but the password of the user is maintained at the network level rather than in the application. If a user is not set up in the User Maintenance window (SS> Maintenance> User), the user will not be able to log into the application. This allows you to limit which users in the network have access to the application.
Click here for user account information.
General guidelines on setting up security
When creating security, set the user and user group at the most restrictive level. Add additional permissions to the user or user group as granting access becomes necessary. Once security has been set up, review the security on a regular basis and make changes as needed.
User versus User Group security
Security within the application (enabled menu options and window fields) can be set up by user or user group. A user group is a group of user accounts and allows you to set security on a number of user accounts at once. If there is security set up on a user and the user is attached to a user group, the security set up on the user account will always override the security set up on a user group. This allows you to attach a user to a user group and then customize the security for a single user.
If a user is attached to multiple user groups, the least restrictive group security will apply. This allows you to attach a user to multiple user groups (including user groups with less security access in some areas of the application) without creating conflicts in security. If there is security set up on the user account, the security on the user will override the security on all of the user groups.
Click here for information on user groups.
Menu Security versus Database Field Security
There are two kinds of security within the application: menu security and db field security. Both can be set up by user or user group.
Menu security (SS> Maintenance> Menu Security) defines which menu options a user or user group can access. If access to a menu option is restricted, the menu option will still display but the user will not be able to select it. If all of the menu options on a palette are restricted, the user will not be able to create new batches on that palette. Menu security can also be used to specify which users or user groups have the rights to create new or delete existing process batches across the application.
DB Security (SS> Maintenance> DB Security) defines which fields and tables within the database the user or user group can access. This feature is helpful when creating security on customer personal information such as social security or bank account numbers because the security will apply to all windows that display the information. There are five levels of security that can be placed on a field or table: Full, Read/Write, Read, No access and Security Not Set. Full access grants the user full access to the field or table. Read/Write access allows the modification of the data but not the deletion of it. Read access will display the data, but the data cannot be modified. When a window is opened that contains a Read access field or table, the field will be disabled. No access security will remove the field from any window that displays the database field or table. If a window is opened that contains a No access field, there will be a blank space where the field is usually displayed. If no security is set up on a table or field, the security will default to No Security Set. This is similar to Full Access because it will not limit access, but security with the No Security Set status will be overridden by security set up on a user group.
Security that is set up on an individual field will override security that is set up on a table.
Click here for menu security maintenance information.
Click here for database field security information.
CR Module Security
Security of the Cash Entry window is set up in the Cash Receipts module. Operators and workstations are created in CR> Maintenance> Operator/Station, and the CR module is set up in CR> Utilities> Setup Cash Receipts.
Click here for an overview of Cash Receipts module security.
PM Module Security
If you are using the Project Management module, you can set up security on PM module tasks so that only certain users can create transactions for those tasks. For example, if only a certain department should be able to attach a specific PM module task code to their timesheets (PR> Timesheets), you can set up that task code to be used in the Payroll module by the employees in that department and then disable that task on all other user accounts and/or user groups.
Click here for information on the PM module Security feature.
® All Rights Reserved 2014
Toll Free Support 866-777-0069