Hi Scott,





Thanks for rolling out Sally to your entire customer success organization! As of now, the permissions are the same for licensed and non-licensed users.





Regarding CTA, the only action we permit right now in Sally is 'Close CTA' and only the owner of the CTA can close it from Sally. CTAs cannot be assigned to non gainsight license users hence they would not be able to act on the CTAs.





Posting to timeline is currently possible for non gainsight license users as well. We are planning to roll out feature level permissions in the future and will provide an option to restrict access.





Thanks,


Rajesh

---

Thanks for the prompt response, Rajesh!





Do you have an idea when feature level permissions will be rolled out?  I'd like to give a rough timeline for the executives.





Will these feature level permissions restrict access based on SFDC profile? Or would it be based on users in the Administration - Slack section?





I'm not sure if this is posted elsewhere in the community, but Sally assignment/permissions based on SFDC profile would be huge for us.  This is a daunting task in change management to ensure new employees have access.

---

Hi Scott,





Access to Sally is based on MDA OAuth user's SFDC permissions. On top of this, we can enforce Gainsight User permissions at the feature level (not available right now). The ETA for feature level permissions is not available right now. Will update you once we have better clarity.





Thanks,


Rajesh

---

@rajesh_gande Any farther updates/ETA? We're looking to roll Sally out farther as well, but the manual updating/managing of permissions and access is starting to get a little daunting.

---

@katie_b Can you please explain your concern one more time? I'd like to know the exact issue you're facing.

---

Your response to this article (https://community.gainsight.com/conversations/automatically-enable-sally-5bc73e1be4b04588aaf86cb0) for auto enable will help a ton since we won't need to manually enable those with Gainsight licenses (which should be our primary Sally users anyway). Our concern is that we add all employees to the Gainsight Users object so that we can social tag anyone in the company on timeline entries where they may need to be notified. Without pulling an external list of employees by department/SF permissions we could potentially enable Sally for a user that otherwise wouldn't have any access to Salesforce data. In the Account Summary widgets, we include information like S&S and could include other sensitive Salesforce fields that would then be visisble to anyone with Sally access. From a security standpoint, it would be nice if the only information visible via Sally would be fields/information that user already had permission to directly OR if we could at least enable/disable based on Salesforce permission sets so we could ensure no one could be given access to information they wouldn't otherwise have.

---

@katie_b Implementing salesforce permissions is not in the immediate roadmap for Sally. I will keep you posted when we pick it up in the future.

---

Is there any cost for enabling a non-Gainsight User for Sally?  e.g. licensing, etc.?

 

Thanks.

JJ

---

Is there any cost for enabling a non-Gainsight User for Sally?  e.g. licensing, etc.?

 

Thanks.

JJ

I was informed by our COM today that at a minimum, each Sally for Slack user must have a Viewer license, and therefore there is a cost involved.

---

This was changed recently to allow Sally for All at no cost. 

---