Could we split the Special Permission Set so that the permission to load to MDA in rules engine is a separate permission than load to SDFC in rules engine? I have a couple customers that loading to SFDC will never be an option but they need the ability to load to MDA for the joins. So because the Special Permission Set currently handles both they are unable to utilize the join functionality.
In the meantime, is there any way around this in order to give them the ability to load to MDA from rules engine without that permission?
Special Permission Set
+4Love the idea of splitting the permission set, Jessica- hope that Product adds it to the list of features to develop.
In the meantime though, with some help from the Salesforce Admin, you can get them rolling with Load to MDA:
1. The permission set gives access to the Configure section of RE where you decide what Objects and Fields are allowed to be updated by rules engine rules.
2. Once that access is given, all the rules engine users can create "Load To" rules for those objects and fields, SO,
3. If you can ask the SFDC Admin to go into Configure and make all the MDA Subject Areas and Fields available, but not any of the SFDC fields, then your Gainsight admin is good to go from there.
Note that if fields get added, they'd have to ask their SFDC Admin to pop in and add the field, but if their MDA structure is pretty stable, it should be too much of a problem.
Hope that helps!
PS - we want to make sure there's never actually a workaround that would allow someone to start loading to native SFDC objects without somebody actively assigning the permission set allowing that to be set up (and since only Admins or designated semi-admins can do that, it keeps the SFDC admin comfortable).
A permission set that only allows MDA access vs SFDC access would be pretty cool, though - easier to convince the SFDC Admin to assign that one to the Gainsight admin(s).
In the meantime though, with some help from the Salesforce Admin, you can get them rolling with Load to MDA:
1. The permission set gives access to the Configure section of RE where you decide what Objects and Fields are allowed to be updated by rules engine rules.
2. Once that access is given, all the rules engine users can create "Load To" rules for those objects and fields, SO,
3. If you can ask the SFDC Admin to go into Configure and make all the MDA Subject Areas and Fields available, but not any of the SFDC fields, then your Gainsight admin is good to go from there.
Note that if fields get added, they'd have to ask their SFDC Admin to pop in and add the field, but if their MDA structure is pretty stable, it should be too much of a problem.
Hope that helps!
PS - we want to make sure there's never actually a workaround that would allow someone to start loading to native SFDC objects without somebody actively assigning the permission set allowing that to be set up (and since only Admins or designated semi-admins can do that, it keeps the SFDC admin comfortable).
A permission set that only allows MDA access vs SFDC access would be pretty cool, though - easier to convince the SFDC Admin to assign that one to the Gainsight admin(s).
Scott Drost, Gainsight -- Principal Customer Success Architect
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.