Roles with Custom Permissions
planned
Jordan Patrick
The ability to create custom user roles on the Givebutter Dashboard with customizable permissions so that organizations can create their own roles with their own specific permissions.
Log In
S
Shiella
Can we allow CRM Managers to acknowledge transactions?
A user shared that in their workflow, CRM Managers handle donor communications and then mark transactions as acknowledged to track what has been processed. Currently, they need additional roles to do this, which provides more access than necessary.
Allowing CRM Managers to acknowledge transactions would better align permissions with their actual workflow.
Since CRM Managers already have access to the Transactions tab, it makes sense for them to be able to perform this task, ensuring their permissions match the responsibilities they are expected to manage.
A
Amanda Moller
Yes! We have someone who needs access only to our Engage function but shouldn't be seeing financial transactions. Or someone who can access entering contacts only.
K
Kelly McMahon
Yes, we definitely definitely need more granular permissions and also the option to create a view-only user account that can be limited to certain campaigns.
Ruthie
From user: I have a suggestion. I would love to see a feature as an administrator; I could give an account user a general role such as "Team Member". This role would have general access without the ability to edit campaigns and contacts, view transactions or issue refunds, use outboard engage features, and access to the mobile app. I would like the ability to assign tasks to account users in order to track progress on campaigns, however I'd prefer them to not have access to most features. Maybe even the ability to customize a role so that it fits my needs as an administrator. Hoping to see a feature like this in the future!
K
Kristen Werner
Ruthie This would be fantastic I agree!
Jordan Patrick
marked this post as
planned
N
Nate Smith
Jordan Patrick Please include the ability to assign users to specific donors so that they only see donor information assigned to the user. Also prohibit limited users from deleting data (notes created by another user, transactions, etc).