The Security level setting on the SystemWeaver server as a whole goes hand-in-hand with item access set via libraries to set item security. This article describes the Security level setting of the server that is available in the swAdmin client. 


Prerequisites

  • Assigned the Root role in the server 
  • Installation of the swAdmin2 client


Note: Admin users must have the "Root" role to be able to modify the Security level. This role should be used restrictively and only be assigned to special, dedicated user accounts.


The password requirements/policy is set on the Security tab. 



By default, Security level is set to 0. To set a new security level, enter one of the follow values (0-3) and click Save.

  • Level 0: Level 0 is equivalent to level 1 (see below). 
  • Level 1: In security level 1, any library or item may be freely accessed by any user unless an access right of the library or item has been limited to a user or group, in which case access will be limited to this setting. However, all users always have Read rights regardless of library access rights settings.
  • Level 2: In security level 2, access to libraries or items is limited to the explicit access rights of the library which applies to all items in that library. This means that no users have rights to a library without those rights being set up in the library. Still, on level 2 all users always have Read rights regardless of access rights settings, similar to level 1.
  • Level 3: Security level 3 is equivalent to level 2, with the addition that Read rights now also need to be explicitly set for the libraries. See Examples for Security Level 3 below.


Users currently logged in to the server would need to log out and back in for the new security level setting to be applied to their session.


Note: When changing the system-wide Security Level setting, any mirror servers must be restarted for the change to take affect in the mirror server.


Examples for Security Level 3

  • If users are to be able to modify items created by other users, they will need "Items Write" rights to the libraries where those items reside. 
  • If users are to be able to take out new versions of or release items created by other users, they will need "Items Change" rights to the libraries where those items reside. 
  • Users without a minimum of Read rights to a library will see a "No access" status if they were to search for a particular item ID for an item in a library that they do not have explicit access rights to. The only information provided is the item Name: