SS> Security> DB Security

DB Security Maintenance

 

Summary

 

DB Security allows you to set the security on a database field or table for a user or user group. This feature is helpful when creating security on personal customer information such as social security or bank account numbers because the security will apply to all windows that display the information.

 

DB Security can be set up by user or user group. If there is security set up on a field at both the user and user group level, the security set up at the user level will override the security set up on the user group. This allows you to customize the user group settings for each user that is attached to a user group. If a user is attached to multiple user groups and there is no DB security set up at the user level, the least restrictive user group security will be applied.

 

If you would like to view the DB security that will be applied to a user, open the user in the DB Security Maintenance window and select the field in the data grid. The security that will be applied to the user will display next to the field name. All of the groups and security settings that are attached to the user will display next to the database field.

 

DB Security can be set up at the field level or the table level, and individual field level security will override all of the security set up on the table level. As with field security, table security set up on the user will override table security set up on groups that a user is attached to.

 

There are five levels of database 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 on a user account will be overridden by security set up on a user group.

 

Use Menu Security (SS> Security> Menu Security) to control access to a menu option if you would like a user or user group to have access to a field in one window but not another.

 

Here are a few fields you may want to set security on in the overview document of each module.

 

  • SS module, Users table, User Name field – This will affect the security on the User Name drop-down menu on the Jobs Viewer. Users with access to this drop-down menu can view the reports generated by other users. If other users are creating reports with sensitive data, users with access to this drop-down menu will have access to that data.
  • SS module, Customer table, SSN field – This will affect the security on the social security number displayed in maintenance and search windows throughout the application. This will not only affect the social security number that displays on the Customer Maintenance window, it will also affect how the SSN will display on the maintenance windows that display information pulled from the customer record such as the People tab on the Account Master Maintenance window in the UB module (UB> Maintenance> Account).

 

Related Links

 

Click here for information on Menu Security.

 

Step by Step

 

1     Open the DB Security Maintenance window (SS> Security> DB Security). 

 

  • The DB Security Maintenance window allows you to set up security on database fields by users or user groups.
  • Select if you would like to modify the security of a user or user group. By default the user group security is selected.
    • Setting DB security at the User level is not currently supported. This functionality will be added in an upcoming service pack.
  • If you have selected to modify user group security settings, the DB Security for User Group drop-down menu will display all of the user groups that have been created in SS> Security> User Groups.
    • Users can be added to user groups from either the User Group Maintenance window or the User Maintenance window.
    • You can view all of the users attached to a user group in the User Group Maintenance window in SS> Security> User Groups.
  • If you are modifying user settings, the DB Security for User drop-down menu will display all users accounts that have been created in SS> Security> Users.
    • Select a user or user group to modify.
  • The Module drop-down menu is used to select which module DB tables/fields will be displayed in the data grid below.
    • Security on the tables in the System Wide Access group will generally affect multiple windows throughout the Springbrook application. For example, the Customer table is used to store the customer record (SS> Maintenance> Customer) and is used by all of the modules that display customer information.

 

2     Set the security on a table or field. 

 

  • You can set up security on a an entire module, a table withing that module, or on the fields within that table.
    • To set the security on an entire module, use the buttons at the top of the data grid.
      • Click FULL ACCESS to allow full access to all tables and fields in the module.
      • Click READ/WRITE to allow read and write access to all tables and fields in the module. Users will be able edit the data, but not delete it.
      • Click READ to allow only read access to all tables and fields in the module.
      • Click NO ACCESS to block access to all tables and fields in the module.
      • Click CLEAR SECURITY SETTINGS to remove all security settings on the tables and fields in the module and change the tables and fields to Security Not Set status.
    • To set the security on an entire table, use the icons in the Modify Security column at the table level. The security set on the table will be applied to all of the fields in the table.
      • Click the Full Access button to allow full access to the table and fields.
        • Full Access is different than the Security Not Set status because it is an active way of granting complete access to the table. Full Access security on an individual field will override all security access set up on the table containing the field. Full Access security set on a user account will override any security set up on user groups the user is attached to.
      • Click the Read/Write button to allow read and write access to the table and fields. Users will be able edit the data, but not delete it.
        • If a table is set up as Read/Write status, the delete button on the maintenance window that maintains the table will be disabled.
      • Click the Read Only button to allow only read access to the table and fields.
        • When a window containing the fields in the table is opened the value in the fields will display, but the fields will not be enabled for modifications.
      • Click the Block button to block access to the table and fields.
        • When a window containing the fields in the table is opened a blank space will appear where the fields usually display.
      • Click the Clear button to remove all security settings on the selected table and fields and change the table to Security Not Set status.
    • To set DB security on individual fields within the table, click the Expand button next to a table.
      • Field level security will override all table level security inherited by fields within the table.
      • For example: If a table is set up as Full Access and a field within the table is set up as No Access, the field security of No Access will override the table security and the user will not have access to the field. If the security on the field is not set, the inherited table security will not be overridden.
      • Click the Full Access button to allow full access to the field.
        • Full Access is different than the Security Not Set status because it is an active way of granting complete access to the field. Full Access security set on a user account will override any security set up on user groups the user is attached to.
      • Click the Read/Write button to allow read and write access to the field.
        • Users or user groups will not be able to delete data in a field set up as Read/White.
      • Click the Read Only button to allow only read access to the field.
        • When a window containing the field is opened the value in the field will display, but the field will not be enabled.

      • Click the Block button to block access to the field.

        • If a window is opened that contains the field, a blank space will appear where the field usually displays.

      • Click the Clear button to remove all security settings on the selected field and change the field to Security Not Set status.
    • Click the Save button when complete. The Save button will only be enabled if there has been modifications to the user or user group security settings.