RELATED IDEAS
Associate the Salesforce Account ID with Aha! ideas portal users via SSO
Some of my customers work for large organizations that we have broken down into many accounts in Salesforce. The customers who access the idea portal are associated directly with the Salesforce account and that account might have the same email domain associated with it as other Salesforce accounts. In these examples, mapping the SF email domain to the Aha! org email domain doesn't work as it pulls in all portal users for the larger organization, rather than those directly associated with the account. In these instances, I'd like to tie the portal user directly to their Salesforce account by syncing over the account ID.
-
-
-
-
-
-
-
- +1
This is critical to our organization. Again, because using domain, rather than a salesforce/account ID leads to inaccurate linking of users to accounts where there is a govt/natl dept or NGO involved that can use a common domain - but have many different branches, and offices, and therefore multiple accounts. Specific examples include the NHS in the UK, or branches of US military - both examples may have unique domains, but also have employees utlilizing a generic domain (ie "nhs.net").
Similar to the comment below, our users are set up associated to the correct account - and we need that account (and only that account) to reflect when we pull reports for ideas revenue, or more importantly when our CRMs pull customer specific reports for customer calls - they need to be confident they're speaking to the correct contact/account about the correct issues.
Happy to provide specific examples, or further detail on use cases as needed.
This request is very important to my organization as well. We are unable to pull accurate reporting for ideas based on the business value / ACV of the requesting customers because the linking to the correct Salesforce organization via domain is inaccurate for us.
Rather, we know each user (login is required to participate in our ideas portal) and would like to be able to reliably associate the contact to the correct organization (based on mapping the organization ID and from the contact's account). Without this ID-based contact to org mapping, our aha! idea reporting is wildly inaccurate for PMs to report on # of organizations and corresponding ACV associated with the newly requested feature/idea.