RBSSetupDefineHierarchy < Main

Tags: view all tags
---+ Defining Your Databases, Departments, Workgroups, Roles & Users

_The first step in setting up RBS is to define your company's structure._

%TOC%
---++ Overview:

The first step required when implementing a security management scheme is to define the five-level Security Hierarchy for Database, Department, Workgroup, Role, and User. This is done by running the 'Security Hierarchy Maintenance' process on the 'Security' tab of the RBS menu.

A configuration setting controls whether or not users can belong to more than one Role at a time. You may wish to set that (without activating RBS) before defining your hierarchy. See [[RBSSetupSetConfiguration][Setting RBS Configuration]].

After defining the hierarchy, you may want to print it via [[RBSSecurityList][Security Hierarchy List/Export]] on the 'Reports' tab of the RBS menu.

You can copy the Hierarchy, so if you have a multiple databases, it is not necessary to define each database individually. Define the first hierarchy, then use the [[RBSCopySecurity][Copy Security]] program on the 'Utilities' tab of the RBS menu to set up your other databases.

There are also utilities to [[RBSExport][export]] and [[RBSImport][import]] the hierarchy, which can be used to transfer the hierarchy to another machine.

Here is an example of how a simple Security Hierarchy might look.
   1 <p align="LEFT">Database : ACME Insurance, Inc. (APPX Database AAA)</p>
      1 <p align="LEFT">Department: Sales</p>
         1 <p align="LEFT">Workgroup: New Sales</p>
            1 <p align="LEFT">Role: Manager</p>
               1 <p align="LEFT">User: John Rogers (APPX User JR)</p>
            1 <p align="LEFT">Role: Inside Rep</p>
               1 <p align="LEFT">User: William Smith (APPX User WS)</p>
               1 <p align="LEFT">User: Samuel Adams (APPX User SA)</p>
         1 <p align="LEFT">Workgroup: Administration</p>
            1 <p align="LEFT">Role: Manager</p>
               1 <p align="LEFT">User: Mary Jones (APPX User MJ)</p>
            1 <p align="LEFT">Roles: Clerical (APPX User BS)</p>
               1 <p align="LEFT">User: Brenda Starr</p>
      1 <p align="LEFT">Department: Claims</p>
         1 <p align="LEFT">Workgroup: Administration</p>
            1 <p align="LEFT">Role: Manager</p>
               1 <p align="LEFT">User: Bruce Williams</p>
            1 <p align="LEFT">Role: Clerical</p>
               1 <p align="LEFT">User: Wanda Scott</p> <p align="LEFT"> </p> <p align="LEFT"> </p>
---++ Description:

When you run 'Security Hierarchy Maintenance' you will see the following screen:

<img alt="hierarchyDatabase.png" src="%ATTACHURL%/hierarchyDatabase.png" />

The Database Id must refer to a Database you have defined in Appx System Administration. You can also set the Timeout and Inactivity settings here. When you press Enter, you will be taken to the 'Department' level:

<img alt="hierarchyDept.png" src="%ATTACHURL%/hierarchyDept.png" />

Here you define the Departments within the selected Database. Department names must be unique within the Database. A Timeout and Inactivity setting can also be specified at this level. When you press Enter, you will be taken to 'Workgroups' for the Department:

<img alt="hierarchywg.png" src="%ATTACHURL%/hierarchywg.png" />

As with Departments, you can specify the Timeout and Inactivity settings. Workgroup names must be unique within the Department. When you press Enter, you will be taken to the 'Roles' for the Workgroup:

<img alt="hierarchyrole.png" src="%ATTACHURL%/hierarchyrole.png" />

Again, we have options for the Timeout and Inactivity settings. Roles must be unique within a Workgroup. When you press Enter, you will be taken to 'Users':

<img alt="hierarchyuser.png" src="%ATTACHURL%/hierarchyuser.png" />

This is the lowest level in the hierarchy and the timeout/inactivity settings here will take priority over higher levels. The user must be defined in Appx System Administration.

---++ Comments:

_Read what other users have said about this page or add your own comments._

<br />%COMMENT%

-- Main.JeanNeron - 2012-10-31
Topic revision: r3 - 2012-11-01 - JeanNeron