Create user permissions/roles for limiting SierraDNA access
We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.
What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).
Beyond the vendor scenario it would also be fantastic to provide limited access to more of our library staff. As a consortia, we have many of our member libraries who could truly benefit from being able to work with their record data but as long as doing so also provides access to things like staff account usernames and the limit network access table we can't open that access up to more of our own users.
Jeremy Goldstein
shared this idea
This idea will be reviewed by the product management team for possible inclusion in a future release.
-
Nicole Turzillo
commented
We are in the same situation in our consortium. Vendors and library staff could benefit from SQL access, but we can't grant it due to the amount of data they would have access to.
-
Lloyd Chittenden
commented
For our consortia, we probably can't let members have SQL access without being able to limit information by scopes and account units. So this would be useful to us.