Control what confluence pages salesforce mentions and associations content bylines appear on?

  • 1
  • Question
  • Updated 2 years ago
We're evaluating the Salesforce & Confluence Cloud Connector add on and after installing it discovered that the add on has added two Salesforce icons to all confluence pages for all users - the Mention and Associations content byline items as described here:

https://docs.servicerocket.com/displa...

Is there anyway to filter those content byline items? For example to configure the add on so that the mentions and associations icons only only appear for pages with salesforce macros embedded, or only for certain pages, or only for certain users/groups? We don't want the salesforce icons appearing on all of our publicly facing confluence pages.
Photo of Andrew Maxymillian-Wheeler

Andrew Maxymillian-Wheeler

  • 2 Posts
  • 1 Reply Like

Posted 2 years ago

  • 1
Photo of Azwandi Mohd Aris

Azwandi Mohd Aris, Official Rep

  • 20 Posts
  • 6 Reply Likes
Hello Andrew, I hear you.

We have plans to introduce permissions to the connector. What would be an ideal permission structure that could support your usage scenario? For example:
  1. Who do you intend to be able to access the Salesforce data and who should not?
  2. How do you think it would be easier to manage the permission? i.e. anonymous vs non-anonymous, internal vs external staff, space vs global.
  3. For those who have access to Salesforce data in Confluence, is there an issue to which field/object they can access?
Photo of Andrew Maxymillian-Wheeler

Andrew Maxymillian-Wheeler

  • 2 Posts
  • 1 Reply Like
For background: Our confluence site is split up into many spaces. Some spaces are public facing and contain product documentation and some are internal and contain business operation/process documentation and notes about customers/projects. We would never mention or link any data in Salesforce on any space that is publicly accessible and even on the internal spaces there are only a couple pages where we would want/need salesforce information.

In our minds we have very specific pages that we would want Salesforce data integrated into do not want to see Salesforce icons or the ability or add Salesforce data outside of those locations.

So to answer your questions:
1) We intend for salesforce data to only be accessible by internal (Corporate) users. We have existing groups that we could leverage for this purpose.

2) For us space level permissions is exactly what we're looking for. As we intend for Salesforce data to be used on a few specific pages and nowhere else being able to enable the connector macros for only pages in that space works perfectly. We could get by with user group permissioning (internal vs external) but then we'd have salesforce icons on a bunch of pages where we don't really need/want them.

3) So far in our testing we've been able to access basic account information. Given our problem with the connector we had to disable it and haven't been able to do more complex testing, e.g., with custom fields.
Photo of Azwandi Mohd Aris

Azwandi Mohd Aris, Official Rep

  • 20 Posts
  • 6 Reply Likes
Hello Andrew, I'm pleased to let you know that we now have the first cut of permission settings in the connector. Take a look at https://docs.servicerocket.com/display/CCSFCONF/Configuring+Permissions to learn more.

At the moment we're not able to hide the byline items from pages yet, but the content of the byline items now honours the permission settings defined.

As always, we would love to hear your feedback.