To make the transition smoother, Salesforce provisioned 100 identity user licenses for customers to patch up the gaps where any Pardot users don’t have Salesforce licenses.
We’ve been helping our clients get prepared for the changes and found there’s a trick to how you can structure your Salesforce Identity Licenses to save confusion down the line.
Every user that needs to access Pardot must have a Salesforce license.
If a user does not have a Salesforce license, you will need to create a Salesforce user record with an ‘Identity’ user license type (selecting a profile is mandatory, which we will revisit later):
With Salesforce user sync, every Salesforce profile is mapped to a Pardot user role (eg. Administrator, Marketing Sales Manager, Sales). The Pardot user record inherits the user role defined for their Salesforce profile (eg. all ‘Standard users’ could be assigned the ‘Sales’ user role for Pardot).
By default, there is only one Salesforce profile for ‘Identity User’. As Salesforce profiles and Pardot user roles are mapped one-to-one, you can find yourself facing limitations. What if you had 10 users requiring identity user licenses, however, 4 need the user role ‘Marketing’ and the rest ‘Sales’. How can you tell Pardot user sync to treat these users differently?
This can be solved by cloning the ‘Identity User’ profile in Salesforce 4 times, naming them ‘Identity – Admin’, ‘Identity – Marketing’, ‘Identity – Sales Manager’, ‘Identity – Sales’.
When mapping profiles during Pardot user sync setup, with 4 separate Salesforce profiles, you can define which level of Pardot access each should have without risking any cross-over.
Overall, this is a great way to make your account permissions set up clearer so both your team, consultants, and your future self, will thank you.
Identity profile can be cloned, you can have sales users, admins...
Then within the connector settings, specify the access for each profile.
This is what I love of Salesforce, there is always a workaround for every need :)
Hi Tom,
I found this article to be very helpful but I'm still having an issue with getting the user connected in Pardot. Does the Identity user need the additional permissions to be assigned in Salesforce that an SSO user would normally need?
Thanks for any help,
Glenn
This only half works,
After setting these up and then attaching them to Pardot users when the new users go to login to pardot this is the message "Your Salesforce login isn't connected to a Pardot user. Ask your Pardot admin for help."
... now what?
We use an app for Time & Expense logging that uses Salesforce Platform licenses (and needs access to Contact object). I've given the AE perm set and perm set license to the user, but it doesn't look like it's working (no option for AE app in LEX). Do I need to create a second login for this user with an Identity license? (That would seem excessive and would likely cause issues with SSO with Azure AD).
Comments: