Sample Permissions Sets from Implementing Institutions

As implementing institutions are testing their user permission setups, it would be great if they could share the permission sets that they created, to help others not have to recreate the same thing.

Please edit this page and add permission sets as you create them. Thank you!

Name of Permission Set

Description - what is the permission set intended to be used for?

Permissions that are included in the set

Apps that this permission set is intended to be used with

Your Institution

sample permission set

this permission set allows employees to log in and look at things

app1-view all records
app2 - view all records

app1, app2

Innovative University

ERM Administration

These sets are from our ERM only implementation. Feedback appreciated!

This adds a couple of settings permissions to our ERM User set. I assign all the ERM folks the User set and then a couple of people get this set. Not sure if this layered method is what is envisioned by the SIG?

I added some note and order perms in here because we were getting note and order permission errors I didn't fully understand, we aren't actually using orders yet.

eHoldings: Can create and delete custom packages and titles
eHoldings: Can edit providers, packages, titles detail records
eHoldings: Can select/unselect packages and titles to/from your holdings
Licenses: Manage license terms
Notes: Can assign and unassign a note
Notes: Can create a note
Notes: Can delete a note
Notes: Can edit a note
Notes: Can view a note
Orders: View order lines
Settings (Agreements): Can view and edit settings
Settings (eHoldings): configure EBSCO RM API credentials
Settings (eHoldings): configure root proxy setting
Settings (erm-usage): display list of settings pages
Settings (notes): display list of settings pages
Settings (Tags): display list of settings pages
UI: ui-notes module is enabled

eholdings, Licenses, Notes, Orders, Settings, UI

Cornell University

ERM User

Standard set for users of our ERM only instance, see notes above.

This set also incorporates general permissions for things users want to do to themselves. If this were not an ERM only instance, perhaps that set should have been broken out further into a generic user set?

ermusage is in here so people can see it but we aren't using it as far as i know.

Agreements: Delete agreements
Agreements: Edit agreements
Agreements: Search & view agreements
Agreements: Search & view e-resources
eHoldings: Can create and delete custom packages and titles
eHoldings: Can edit providers, packages, titles detail records
eHoldings: Can select/unselect packages and titles to/from your holdings
ermusage all
ermusage user
ermusage view
eUsage: Can view usage data providers and COUNTER reports
Licenses: Delete licenses
Licenses: Edit licenses
Licenses: Search & view licenses
Notes: Can assign and unassign a note
Notes: Can create a note
Notes: Can delete a note
Notes: Can edit a note
Notes: Can view a note
Orders: Assign acquisition units to new order
Orders: Check-in items
Orders: Create order lines
Orders: Create orders
Orders: Delete order lines
Orders: Edit order lines
Orders: Edit orders
Orders: Manage acquisition units
Orders: Receive items
Orders: Remove orders
Orders: View order lines
Orders: View orders
Organizations: Interface usernames and passwords: view
Organizations: Interface usernames and passwords: view, edit, create, delete
Organizations: View
Organizations: View, edit
Organizations: View, edit, create
Organizations: View, edit, delete
Settings (notes): display list of settings pages
UI: eHoldings module is enabled
UI: erm-usage module is enabled
UI: ui-notes module is enabled
Users: Can send create/reset password link
Users: Can view user profile

Agreements, eHoldings,ermusage, licenses, notes,orders, organizations, UI, users

Cornell University