Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-921

Add Salesforce.com integration into Crowd

XMLWordPrintable

    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Salesforce use delegated auth, and APIs are available.

      http://blog.sforce.com/sforce/2005/07/sforce_single_s.html

            [CWD-921] Add Salesforce.com integration into Crowd

            Aakrity Tibrewal added a comment -
            Atlassian Update - 27 April 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Crowd Data Center, please check our public roadmap.

            Kind regards,
            Crowd Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 27 April 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Crowd Data Center, please check our public roadmap . Kind regards, Crowd Data Center

            Peter Rush added a comment -

            It appears that Atlassian applications in their user management data structures consider all users to be part of the same organization, which makes sense for the "internal team collaboration" use case.  But if the use case is "client collaboration" then there is no OOTB concept of a client organization.  So no data structure to support "Organization" and a variety of meta-data you would want associated with a given user's "Organization", like "Products/Services Licensed" or other classifications.  We are currently solving for all of this using direct and nested groups, but it's clunky.  Let me know if you want to chat more.  Is anything like this in the works with Confluence/Crowd?

            Peter Rush added a comment - It appears that Atlassian applications in their user management data structures consider all users to be part of the same organization, which makes sense for the "internal team collaboration" use case.  But if the use case is "client collaboration" then there is no OOTB concept of a client organization.  So no data structure to support "Organization" and a variety of meta-data you would want associated with a given user's "Organization", like "Products/Services Licensed" or other classifications.  We are currently solving for all of this using direct and nested groups, but it's clunky.  Let me know if you want to chat more.  Is anything like this in the works with Confluence/Crowd?

            Marcin Kempa added a comment -

            peter.rush149336707 what exactly is this concept of "customer organization" how it is used and what do you imagine could be the representation in Confluence and Crowd?

            Marcin Kempa added a comment - peter.rush149336707 what exactly is this concept of "customer organization" how it is used and what do you imagine could be the representation in Confluence and Crowd?

            Peter Rush added a comment -

            We are using Confluence to power a B2B customer portal.  In addition to Salesforce integration, it would be ideal of Confluence and Crowd both had native concepts for "customer organization".

            Peter Rush added a comment - We are using Confluence to power a B2B customer portal.  In addition to Salesforce integration, it would be ideal of Confluence and Crowd both had native concepts for "customer organization".

            Dennis L. added a comment -

            Salesforce is big player. still need sso support for salesforce

            Dennis L. added a comment - Salesforce is big player. still need sso support for salesforce

            František Špaček [MoroSystems] added a comment -

            I wonder why this is still overlooked.

            František Špaček [MoroSystems] added a comment - I wonder why this is still overlooked.

            David Waelder added a comment -

            We would really need this one. In fact we purchased additional licenses as we thought that the integration was possible.

            David Waelder added a comment - We would really need this one. In fact we purchased additional licenses as we thought that the integration was possible.

            josteink added a comment -

            This would be a great benefit for our company as well.

            josteink added a comment - This would be a great benefit for our company as well.

            Dustin Windibank added a comment -

            This could also be done either exposing Crowd as a LDAP source, or by supporting generic SAML connections.

            Dustin Windibank added a comment - This could also be done either exposing Crowd as a LDAP source, or by supporting generic SAML connections.

            Paul Dale added a comment -

            We are very big on SF. Built in integration would be a reason to buy crowd for us.

            Paul Dale added a comment - We are very big on SF. Built in integration would be a reason to buy crowd for us.

              Unassigned Unassigned
              doflynn David O'Flynn [Atlassian]
              Votes:
              30 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: