Chapter 11 - Security 4.0 - Revision history

Tomh: /* Document Level Security */

2014-09-23T16:54:49Z

‎Document Level Security

Tomh: /* Document Level Security */

2014-09-23T16:53:25Z

‎Document Level Security

Tomh: /* Document Level Security */

2014-09-23T16:52:33Z

‎Document Level Security

Tomh: /* Document Level Security */

2014-09-23T16:51:26Z

‎Document Level Security

Tomh: /* Document Level Security */

2014-09-23T16:47:26Z

‎Document Level Security

Tomh: /* Document Level Security */

2014-09-23T16:46:23Z

‎Document Level Security

Tomh: /* Editing an existing user set up */

2014-09-23T16:45:36Z

‎Editing an existing user set up

Tomh: /* Editing an existing user set up */

2014-09-23T15:46:18Z

‎Editing an existing user set up

Tomh: /* halFILE Active Directory Integration Set Up Procedure */

2014-07-28T22:56:10Z

‎halFILE Active Directory Integration Set Up Procedure

Tomh: /* halFILE Active Directory Integration Set Up Procedure */

2014-07-28T22:54:42Z

‎halFILE Active Directory Integration Set Up Procedure

@@ Line 59: / Line 59: @@
 [http://help.halfile.com/index.php?title=Chapter_10_-_Security_4.0#column-one Contents]
-Document Level Security defines what documents a group of users can view based on selection criteria against a database field. To set up Document Level Security, select the Configure-Security-Document Level menu in the Administrator. This displays the screen below.
+Document Level Security defines what documents a group of users can view based on selection criteria against a database field. To set up Document Level Security, select the '''Configure-Security-Document Level''' menu in the Administrator. This displays the screen below.
 Examples of document level security include:
@@ Line 66: / Line 66: @@
 * Restricting access to certain instrument types in the database. If the document is a military discharge, for example, users cannot view it.
-To set up Document Level Security, select the Configure-Security-Document Level menu in the Administrator. Select the Application and Database you want to define the security settings for then click New Profile and enter a phrase that describes the security setting. Then highlight that phrase and click NEXT to define the settings for this new security group. This displays the screen below.
+To set up Document Level Security, select the '''Configure-Security-Document Level''' menu in the Administrator. Select the Application and Database you want to define the security settings for then click New Profile and enter a phrase that describes the security setting. Then highlight that phrase and click NEXT to define the settings for this new security group. This displays the screen below.
 [[File:Doclevel_members.png]]
-The members tab is used to select the members that will be a part of this security group. Click the Add>> button to include a user in the group.
+The '''members''' tab is used to select the members that will be a part of this security group. Click the Add>> button to include a user in the group.
 [[File:Doclevel_restrictions.png]]
-The restrictions tab defines how documents are selected for this group. The selection criteria are placed into the SQL Clause box. The Field Name, Operator and Values boxes are used to help you build a validate SQL Clause. For example, we selected the Field Name “primetable.Date_Of_Filing”, the less than operator and entered the Value “08/31/2014”. Then we clicked Check SQL which posted the following SQL Clause:  (primetable.Date_Of_Filing < ‘08/31/2014’)
+The '''restrictions''' tab defines how documents are selected for this group. The selection criteria are placed into the SQL Clause box. The Field Name, Operator and Values boxes are used to help you build a validate SQL Clause. For example, we selected the Field Name “primetable.Date_Of_Filing”, the less than operator and entered the Value “08/31/2014”. Then we clicked Check SQL which posted the following SQL Clause:
 This tells the system that, for this security group, when a search is performed only show documents where the Date_Of_Filing field is less than August 31, 2014.

@@ Line 72: / Line 72: @@
 The members tab is used to select the members that will be a part of this security group. Click the Add>> button to include a user in the group.
-[[File:Example.jpg]]
+[[File:Doclevel_restrictions.png]]
 The restrictions tab defines how documents are selected for this group. The selection criteria are placed into the SQL Clause box. The Field Name, Operator and Values boxes are used to help you build a validate SQL Clause. For example, we selected the Field Name “primetable.Date_Of_Filing”, the less than operator and entered the Value “08/31/2014”. Then we clicked Check SQL which posted the following SQL Clause:  (primetable.Date_Of_Filing < ‘08/31/2014’)

← Older revision		Revision as of 16:52, 23 September 2014
Line 69:		Line 69:

	[[File:Doclevel_members.png]]		[[File:Doclevel_members.png]]
		+
		+	The members tab is used to select the members that will be a part of this security group. Click the Add>> button to include a user in the group.
		+
		+	[[File:Example.jpg]]
		+
		+	The restrictions tab defines how documents are selected for this group. The selection criteria are placed into the SQL Clause box. The Field Name, Operator and Values boxes are used to help you build a validate SQL Clause. For example, we selected the Field Name “primetable.Date_Of_Filing”, the less than operator and entered the Value “08/31/2014”. Then we clicked Check SQL which posted the following SQL Clause: (primetable.Date_Of_Filing < ‘08/31/2014’)
		+
		+	This tells the system that, for this security group, when a search is performed only show documents where the Date_Of_Filing field is less than August 31, 2014.
		+
		+	Other example SQL Clauses:
		+
		+	(Primetable.Instrument_Type <> ‘DD214’) – hides documents with an Instrumen_Type = DD214.
		+
		+	(Primetable.Official_Record = ‘N’) – if the Official_Record field is Y because there is a Social Security number on the document, then do not let users in this group see it.
		+
		+	NOTE: Be sure to set up a Group with “no restrictions” so all documents can be accessed.

	==Windows Active Directory Integration==		==Windows Active Directory Integration==

@@ Line 68: / Line 68: @@
 To set up Document Level Security, select the Configure-Security-Document Level menu in the Administrator. Select the Application and Database you want to define the security settings for then click New Profile and enter a phrase that describes the security setting. Then highlight that phrase and click NEXT to define the settings for this new security group. This displays the screen below.
-[[File:Example.jpg]]
+[[File:Doclevel_members.png]]
 ==Windows Active Directory Integration==

← Older revision		Revision as of 16:47, 23 September 2014
Line 67:		Line 67:

	To set up Document Level Security, select the Configure-Security-Document Level menu in the Administrator. Select the Application and Database you want to define the security settings for then click New Profile and enter a phrase that describes the security setting. Then highlight that phrase and click NEXT to define the settings for this new security group. This displays the screen below.		To set up Document Level Security, select the Configure-Security-Document Level menu in the Administrator. Select the Application and Database you want to define the security settings for then click New Profile and enter a phrase that describes the security setting. Then highlight that phrase and click NEXT to define the settings for this new security group. This displays the screen below.
		+
		+	[[File:Example.jpg]]

	==Windows Active Directory Integration==		==Windows Active Directory Integration==

@@ Line 62: / Line 62: @@
 Examples of document level security include:
-•	Restricting access to sensitive information such as personnel records or documents that contain a social security number.
+* Restricting access to sensitive information such as personnel records or documents that contain a social security number.
-•	Restricting access to documents based on a certification date. If the document is after a specified certification date, users cannot view it.
+* Restricting access to documents based on a certification date. If the document is after a specified certification date, users cannot view it.
-•	Restricting access to certain instrument types in the database. If the document is a military discharge, for example, users cannot view it.
+* Restricting access to certain instrument types in the database. If the document is a military discharge, for example, users cannot view it.
 To set up Document Level Security, select the Configure-Security-Document Level menu in the Administrator. Select the Application and Database you want to define the security settings for then click New Profile and enter a phrase that describes the security setting. Then highlight that phrase and click NEXT to define the settings for this new security group. This displays the screen below.

← Older revision		Revision as of 16:45, 23 September 2014
Line 55:		Line 55:

	When you click a database in the grid, the extended settings for that user and database are updated in the box at the lower right corner of the screen. These settings enable/disable addition features for the user.		When you click a database in the grid, the extended settings for that user and database are updated in the box at the lower right corner of the screen. These settings enable/disable addition features for the user.
		+
		+	===Document Level Security===
		+	[http://help.halfile.com/index.php?title=Chapter_10_-_Security_4.0#column-one Contents]
		+
		+	Document Level Security defines what documents a group of users can view based on selection criteria against a database field. To set up Document Level Security, select the Configure-Security-Document Level menu in the Administrator. This displays the screen below.
		+	Examples of document level security include:
		+
		+	• Restricting access to sensitive information such as personnel records or documents that contain a social security number.
		+	• Restricting access to documents based on a certification date. If the document is after a specified certification date, users cannot view it.
		+	• Restricting access to certain instrument types in the database. If the document is a military discharge, for example, users cannot view it.
		+
		+	To set up Document Level Security, select the Configure-Security-Document Level menu in the Administrator. Select the Application and Database you want to define the security settings for then click New Profile and enter a phrase that describes the security setting. Then highlight that phrase and click NEXT to define the settings for this new security group. This displays the screen below.

	==Windows Active Directory Integration==		==Windows Active Directory Integration==

@@ Line 54: / Line 54: @@
 [[File:User_Profiles_New_User.jpg]]
-When you double click a database in the "databases the user can access" box, the screen below is shown. You can set up the user privileges for the database on this screen.
+When you click a database in the grid, the extended settings for that user and database are updated in the box at the lower right corner of the screen. These settings enable/disable addition features for the user.
 ==Windows Active Directory Integration==

@@ Line 85: / Line 85: @@
 [http://help.halfile.com/index.php?title=Chapter_10_-_Security_4.0#column-one Contents]
-# Set up a Windows Active Directory Group for each type of User that you would have in halFILE. For example, if I have Search only users, Search and Index users and Admin users, I would set up 3 Active Directory Groups as follows:
+Set up a Windows Active Directory Group for each type of User that you would have in halFILE. For example, if I have Search only users, Search and Index users and Admin users, I would set up 3 Active Directory Groups as follows:
-## HFAD_User_Search – for users with Search only privileges.
+# HFAD_User_Search – for users with Search only privileges.
-## HFAD_User_Index – for users with Search and Index privileges.
+# HFAD_User_Index – for users with Search and Index privileges.
-## HFAD_User_Admin – for users with Admin privileges.
+# HFAD_User_Admin – for users with Admin privileges.
 # Add the Network users into the appropriate HFAD_User group(s).
 # Set up a Windows Active Directory Group for each type of Custom Search you require. For example, if you have a Custom Search for Public users and a second Custom Search profile for Employees, then you would set up the Active Directory Groups as follows:

@@ Line 95: / Line 95: @@
 # Add the Network users into the appropriate HFAD_Search group(s).
 # Change halFILE to use Active Directory Integration. In the Administrator, this is under Tools-Options / Security/Versions tab. Check the "Use Active Directory Integration" box. Note: You must check the "Use halFILE Integrated Security" box to enable this check box.
-# Set up a single User and Custom Search in halFILE for each Windows Active Directory Group, using the same name as the Windows Active Directory Group. So using the above examples, set up users named HFAD_User_Search, HFAD_User_Index and HFAD_User_Admin. Set up all the features as needed including Extended Settings and Group/Document Level Security. Then, set up Custom Search Profiles named HFAD_Search_Public and HFAD_Search_Employee.
+# Set up a single User and Custom Search in halFILE for each Windows Active Directory Group, using the same name as the Windows Active Directory Group. So using the above examples, set up users named HFAD_User_Search, HFAD_User_Index and HFAD_User_Admin. Set up all the features as needed including User Parameter Settings and Group/Document Level Security. Then, set up Custom Search Profiles named HFAD_Search_Public and HFAD_Search_Employee.
 # Now, when a user goes into halFILE, they are automatically assigned their Network user id. halFILE looks up the user id in the Windows Active Directory Groups to determine which groups the user belongs to. Then, the user's profile for halFILE security is created for the user.