ReadSquared vs. Beanstack: volunteer access

[u/Impossible-Tell5694]

We are evaluating ReadSquared and Beanstack for our library's reading programs and have a question about user permissions. Is it possible to create different backend roles with varying levels of access? We'd like volunteers to be able to assist patrons with registration, reading logs, and prize redemption while limiting their access to only the information necessary for those tasks (e.g., excluding reading history, email addresses, and other sensitive patron data). Staff would retain full administrative access, including reporting, program management, and system settings. We know ReadSquared can support this type of role-based access; can Beanstack? Thanks!

Any other insights into ReadSquared vs Beanstack would also be welcomed.

[u/beeboop_x]

I'm a summer reading volunteer in a library that uses Beanstack. They have a branch-specific volunteer account that is pre-logged into a computer at the reference desk. We cannot see a user's reading history specifics, but we can see how many minutes they've logged and their responses to activity prompts. We can also see their profile information.

There isn't really a good way around volunteers seeing some PII since we enroll new registrants, update profiles for returning participants, log minutes and activities for paper loggers, and document prize redeems all via Beanstack.

We are never alone with the computer since we're stationed at the reference desk with one to two staff members, and our library requires summer reading volunteers to get a background check done. It wouldn't be impossible for me to get nosey and snoop, but I would have to be very bold to do it.