Restrict access to Case Central and Chat through Security Groups
We are preparing to train our Parent Volunteers on how to use NXT to manage their solicitations for the Annual Campaign. I have created a security group for these parents and restricted their view to specific Funds and specific Constituent Codes. I was surprised to learn that when the Parent Volunteers log in to NXT, they can click on the Green help icon in the upper right hand corner and then have access to our complete Case Central Library as well as initiate a Chat session with support.
I don't want them to see Case Central - and I certainly don't want them creating support tickets via Chat for things that I should be helping them with. I would like to restrict access to these areas based on the Security Group.
-
Candace Chesler
- Aug 1 2016
- Reviewed: Voting Open
Related ideas
Yes! In the days of database-only, only certain staff members had access to bb.com for Case Central (needs for researching in the KB, training, cases, etc were funneled through certain staff members). Now that other folks are set up in bb.com so that they have access to web view, we don't necessarily want just anyone opening cases.
Attachments Open full size
Has there been anymore consideration of this request. The ability to have granular ability to secure these features would be a huge help and would reduce confusion and the load on support.
Attachments Open full size
I agree with Jen: this is a brilliant idea, and there should be the option to set read/write access.
Another argument for this option: We have volunteers who help out at events and register attendees. We often have student- and donor-related information discussed in our Cases. The two must be kept separate.
Attachments Open full size
I'd love to see options to allow read/write access in the BB.com Portal. So I could say that User A can read Cases associated with our Site ID but not open (i.e. write) any. But User B can both read and write. And User C cannot do either. For me, either by Security Group or by individual User Record would work. Brilliant idea, Candace!
Attachments Open full size