The Employee Experience implementation represented by this question requires three complementary access layers: Employee Experience Community Access , Employee Productivity Plus Access , and Employee Experience for Public Sector .
Employee Experience for Public Sector grants access to Public Sector employee-specific objects and capabilities. Salesforce's release documentation states that employees need this permission set to access the Public Sector objects and features associated with Employee Experience.
Employee Productivity Plus Access supplies employee productivity functionality and UI-component access. Salesforce's HR Service Center permissions reference confirms that this permission set provides read access to onboarding tasks and user-interface components and requires the Employee Productivity Plus entitlement.
Employee Experience Community Access is the package-era permission used to provide the employee with access to the digital Employee Experience environment itself. Together, these three permissions establish community/site access, employee productivity capability, and Public Sector-specific employee functionality.
Employee Productivity Plus User Data Access provides a different data-access layer used in HR Service Center scenarios and isn't one of the three permission sets identified for accessing this prebuilt Public Sector Employee Experience application. Public Sector Solutions User Access is likewise broader and doesn't replace the Employee Experience-specific permission assignment.
Salesforce's employee-product naming has evolved in current releases toward Employee Service and unified employee licensing, but B, C, and D correspond to the architecture tested by this item.
Study Guide Reference: Public Sector Solution Product Configuration – Employee Experience for Public Sector; Employee Experience Community Access; Employee Productivity Plus; permission configuration.
