If you give users access to the Table Editor, be aware that many of the views that are accessible within the Table Editor are not secured by default. (For example, the circ_parameter view is not secured by default.) Consequently, you may want to review these views and secure those whose access you want to limit. You secure a view by marking the Secured check box in the view definition (as explained in the steps under To secure views within the Table Editor). Marking the Secured check box creates a passkey privilege for the view, which you can then assign to passkeys as needed.
Search views and program-only views are secured as part of the processes in which they appear; changing the Secured check box for these views will have no effect. General views, which are the views you access in the Table Editor, may or may not be secured. Although access to the Table Editor is controlled by the ADM Table Editor role privilege, once you grant this privilege to a user, he or she has access to all unsecured views within the Table Editor (as well as any secured views for which he or she has rights).
For the self-check views, you can assign the CRC - ACS Control privilege to the user or group that you want to be able to access any of the self-check views.
You can add general views to the navigation bar for a group of users in a preference group. (For instructions, see Adding a View as a Process to the Navigation Bar.) To access these views, users still need the ADM Table Editor role privilege and the passkey privilege for the view, if any. (Note that if you secure the view with a local privilege, the local privilege replaces the ADM Table Editor role privilege.) Views that are included on the navigation bar by default (system-defined processes) are secured by role privileges only. Users can access these views (either from the navigation bar or from within the Table Editor) only if you grant them the appropriate role privilege.
To secure views within the Table Editor
1 | Follow these steps to generate a list of all the general views on your system that are not secured: |
a | Start the View Control process. |
The default location of this process is the Administration folder on the navigation bar.
Horizon displays the List Horizon View window with a search window on top.
b | In the Search window, click Cancel. |
Horizon asks you if you want to load all of the rows in the view.
c | Click OK. |
d | Choose File, Where Clause. |
e | In the Selection Criteria window, enter this text string: |
privilege_number = null and view_type = 0
Horizon updates the list to include only general views that are not secured.
2 | Review the views in the list, and complete these steps for each view you want to secure. |
a | Highlight the view you want to secure. |
b | Click Edit to display the Edit Horizon View window. |
c | Mark the Secured box. |
d | Save your changes. |
Horizon creates a passkey privilege for the view and displays the privilege number in the Privilege Number field. Now that the view is secured, users cannot access it until you grant them access. (Note that clearing the Secured box deletes the passkey privilege, removes the privilege number, and makes the view unsecured.)
3 | When you are finished reviewing and updating the security setting for your views, close the List Horizon View window. |
4 | If you want to grant the newly created privileges to users, exit Horizon, log back in, and use the Pass Key Manager to add the privileges to passkeys as necessary. |
For instructions on adding a privilege to a passkey, see Add a privilege to a passkey.
© 1998-2017 Sirsi Corporation