1 = User and Group Permissions =
4 It is essential to understand how user and group permissions can be used to allow
5 staff to fulfill their roles while ensuring that they only have access to the
8 Permissions in Evergreen are applied to a specific location and system depth
9 based on the home library of the user. The user will only have that permission
10 within the scope provided by the Depth field in relation to his/her working
13 Evergreen provides group application permissions in order to restrict which
14 staff members have the ability to assign elevated permissions to a user, and
15 which staff members have the ability to edit users in particular groups.
19 New staff accounts are created in much the same way as patron accounts, using
20 _Circulation -> Register Patron_ or *Shift+F1*. Select one of the staff
21 profiles from the _Profile Group_ drop-down menu.
23 image::media/permissions_1a.png[Permission Group dropdown in patron account]
25 Each new staff account must be assigned a _Working Location_ which determines
26 its access level in staff client interfaces.
28 . To assign a working location, open the newly created staff account using *F1*
29 (retrieve patron) or *F4* (patron search).
30 . Select _Other -> User Permission Editor_
32 image::media/permissions_1.png[Click User Permission Editor in the Patron's Other menu]
34 . Place a check in the box next to the desired working location, then scroll to
35 the bottom of the display and click _Save_.
37 NOTE: In multi-branch libraries it is possible to assign more than one working
40 === Staff Account Permissions ===
42 To view a detailed list of permissions for a particular Evergreen account go to
43 _Administration -> User Permission Editor_ in the staff client.
45 === Granting Additional Permissions ===
47 A _Local System Administrator (LSA)_ may selectively grant _LSA_ permissions to
48 other staff accounts. In the example below a _Circ +Full Cat_ account is granted
49 permission to process offline transactions, a function which otherwise requires
52 . Log in as a Local System Administrator.
53 . Select _Administration -> User Permission Editor_ and enter the staff account
58 Retrieve the staff account first, then select _Other -> User Permission
61 . The User Permission Editor will load (this may take a few seconds). Greyed-out
62 permissions cannot be edited because they are either a) already granted to the
63 account, or b) not available to any staff account, including LSAs.
65 image::media/profile-5.png[profile-5]
67 1) List of permission names.
69 2) If checked the permission is granted to this account.
71 3) Depth limits application to the staff member's library and should be left at
74 4) If checked this staff account will be able to grant the new privilege to
75 other accounts (not recommended).
77 . To allow processing of offline transactions check the Applied column next to
80 image::media/profile-6.png[profile-6]
82 . Scroll down and click Save to apply the changes.
84 image::media/profile-7.png[profile-7]