This is critical for consortia.

In a consortia, each library needs to be able to set their own permissions and not every staff member within a library needs to have that permission. The director should decide who should have permission to make changes.

Different staff work at different levels of permissions and as a consortia, we want each library to have the ability to set access controls for their own staff.

This is very important for a large organization. We need to be able to tie down staff who can update the homepage which differ from staff who update the locations. These staff are different from those who update the config of Vega. We also need to be able to have separate logins per person. It's not reasonable to give everyone one login/password, which we can't change ourselves.

The current way to change the admin password based on an email in the system seems problematic and slow.

This is absolutely critical for consortia, when there are multiple libraries and multiple home pages to manage by different organizations. We are not a centralized consortium, and each library needs to have the permissions to create and manage their own home pages, while still keeping system-level admin with one login.

This is critical for consortia. We need more granularity in access. We need the ability to set up accounts for member libraries that limit access to ONLY being able to edit their library's home page. These library specific accounts should have no access to another library's Collection Site or Kiosk and no access to the main admin site. We at the consortia level should be able to access all admin functions for the central site as well as be able to edit all libraries' collection sites, kiosks, and admin functions.

When it comes to showcase permissions, we also need to be able to limit which showcases admin access allows an individual library's account to edit.

This is critical for consortia since staff need to be able to have the ability to ONLY edit the home page of their own library's collection site and not have access to other libraries' collection sites or the consortium collection site. They also should only be able to edit the home page and not have access to other admin functions that we at the consortium level should only have access to. There can be levels where some staff can only create showcases and others can also publish, but our biggest need is keeping the editing of the home pages on each collection site separate and only allowing home page editing, not all admin features. Only we as admin users at the consortium level should be able to edit all libraries' collection sites and access other admin functions.

also very important for us, with so many libraries. We can't possibly maintain so many homepages. they need to be able to do it themselves, without having the full admin privs.

Granular permissions are another minimum requirement for us to consider a vendor's product. We have very granular permissions on our setup and would not be interested in going back to only two levels.

I would like to allow our marketing person to handle the Vega Homepage, with her own login/access which is limited to just the Home page, not all the other admin features. That goes against all of our security principles. Much like LX Starter allows for that (separate admin portal); otherwise, she should get a login and only see Home page. Not log in with my admin account which was suggested (!). We need some more granularity. Not at the level of Sierra obviously, but something beyond Admin vs. Staff.