We’ve set up a custom dashboard in Analytics to track partner performance metrics, but our Partner Portal users are getting “Insufficient Privileges” errors when trying to access it. The dashboard is shared with the Partner Community folder, and we’ve verified that the sharing settings show “Viewer” access for the Partner User profile.
The confusing part is that internal users can see the dashboard without any issues, and we’ve confirmed that the Partner users have the correct Permission Set assigned that includes “View All Data” for reports and dashboards. The folder permissions look correct in the UI, but partners still can’t access it.
We’re on Summer '24 and using the Partner Community template. Has anyone successfully configured dashboard sharing for Partner Portal users? What are we missing in the permission configuration?
Partner Portal permissions are tricky because they work differently from internal users. Even if the folder shows shared access, Partner users need explicit permission sets that include not just dashboard access, but also access to all underlying report data sources. Check if your Permission Set includes read access to all objects referenced in the dashboard’s reports. Also verify that your Partner user’s profile has the “View Dashboards in Public Folders” permission enabled.
I’ve dealt with this exact scenario. The issue is usually at the report level, not the dashboard level. Each report in your dashboard needs to be shared individually with the Partner Community folder or with a public group that includes Partner users. Dashboard folder sharing alone isn’t enough. Go to each report, check its sharing settings, and make sure Partners have at least Viewer access. Also, confirm that the reports aren’t using “Run as specified user” with a user that Partners can’t access.
The “Insufficient Privileges” error for Partner Portal dashboard access typically involves three distinct permission layers that all need proper configuration. Let me break down the complete solution.
Permission Set Assignment:
Your Partner users need a comprehensive Permission Set that includes:
- “View Dashboards in Public Folders” system permission
- “View Reports in Public Folders” system permission
- “Run Reports” permission
- Object-level Read access for EVERY object used in the dashboard’s underlying reports
- Field-level security for all fields referenced in report filters and columns
Create a dedicated Permission Set called “Partner Analytics Access” and assign it to all Partner users who need dashboard visibility. The “View All Data” permission you mentioned is often too broad and may not be available for Partner licenses-focus on specific object permissions instead.
Dashboard Folder Sharing:
Folder sharing has multiple components that must align:
- Navigate to the dashboard folder in Analytics
- Click “Share” and verify the Partner Community is listed
- Set access level to “Viewer” (minimum) or “Editor” if partners need to customize views
- Check the “Run as logged-in user” option-this is critical for Partner Portal users
- Verify the folder type is “Public” not “Private”
However, folder sharing alone is insufficient. Each individual report within the dashboard needs separate sharing configuration:
- Open each report used in the dashboard
- Click “Share” on the report
- Add the Partner Community or a Public Group containing Partner users
- Grant “Viewer” access minimum
- Ensure “Run as logged-in user” is selected (not “Run as specified user”)
Partner Portal Access Configuration:
The Partner Portal itself needs proper analytics enablement:
- Go to Setup → All Communities → [Your Partner Community] → Administration → Settings
- Enable “Allow members to view reports and dashboards” under Analytics settings
- Verify “Analytics for Communities” is enabled (required in Summer '24+)
- Check Community member visibility settings-ensure Partners can see the data they need based on sharing rules
- Review the Partner Community Profile settings:
- Standard object permissions for all report data sources
- Tab visibility for Reports and Dashboards
- “View My Team’s Dashboards” if using role hierarchy
Additional Troubleshooting:
- Test with a specific Partner user using “Login As” to see exactly what they see
- Check if any reports use cross-filters or formulas that reference objects Partners can’t access
- Verify that sharing rules aren’t blocking Partner access to underlying records
- Review any custom Lightning components in the dashboard that might have separate permission requirements
- Confirm Partner license type supports Analytics (some Partner licenses have limited analytics capabilities)
Common Pitfall:
The most frequent issue is that internal users can see dashboards because they inherit permissions through role hierarchy and organization-wide defaults, while Partner users operate in a much more restricted security context. Every permission must be explicitly granted.
After making these changes, have Partner users log out and back in to refresh their permission cache. The dashboard should then be accessible with proper data visibility based on their sharing rules and role hierarchy position within the Partner Community.
Don’t forget about object-level security! Partner Portal users operate under much stricter security than internal users. Even with dashboard and report sharing configured, if the Partner profile doesn’t have Read access to the objects used in the report queries, they’ll get insufficient privileges. Check your Partner profile’s object permissions for every object referenced in your dashboard reports. You might need to create a custom Permission Set that grants specific object access.
Another thing to check: the dashboard folder type. Make sure it’s set to “Public” or “Shared” and not “Private”. Also, Summer '24 introduced some changes to Community analytics permissions. You might need to enable “Analytics for Communities” in your Community settings if it’s not already on. And verify that your Partner users have logged into the Community at least once-sometimes permissions don’t fully activate until first login.