Feedback from a user: I wanted to request a feature on the mobile app. We’re getting ready to host an event, and we have a large group of volunteers that will be checking guests in. It would be really amazing if users did not have to be a campaign, editor or administrator to use the mobile app to scan tickets. I was hoping That I would be able to allow volunteers to scan tickets with their own phone without giving them access to our entire campaign data. It doesn’t look like that’s an option at this point in time, so I wanted to request that feature be added in the future. Thank you for considering.

We would love the ability to have a user permission level that allows them to see a specific campaign but not the others.

We would like the ability to give view only access by campaign and show tickets purchased/contributions made. Our concern is that some people who are requesting access to view the campaigns might start changing settings and mess up the tickets/campaign settings.

a role for "check-in only" or "event volunteer" on a campaign by campaign basis would be great. Our event volunteers do not need access to all of our campaigns, transactions, customer lists, etc. Just check-in and on-site purchases/donations for that specific event.

This is a key feature need. We are exploring other platform options as we dont want volunteers to have any other access than the ability to check in or sell tickets for specific campaigns.

Can we get an update on this? It is very much needed in our organization to share information with Event Coordinators. Thanks!

While you're implementing an updated permissions capability (a non-trivial task!), please make it as granular as possible. Ideally, with field-level access controls (e.g., allow some users to have arbitrated access to each field in a record.) Also, allow authorized users to create custom roles.

Something important is the ability to control who can create tags or at least a subset of tags. A category of tags (I'll call them curated tags) that is centrally managed must exist. These would be things like Volunteer Class (Volunteer, Volunteer-Transport Coordinator, Volunteer-Transport Driver) - things that would be used at the organization level to filter/segment the contacts. Without curated tags, you wind up with things like Vol-Trans Coord, Volunteer-Trans Coord, and Vol-TC. These can be fixed, but it's best to start with clean data when you have hundreds (or thousands) of contacts.

Jordan Patrick & GiveButter Team: Can you be more specific than "IN PROGRESS"? I asked about this many months ago and was told it's in progress. This is an essential needed feature -- i.e., restricted access to revenue and bank account information: critical. Thank you.