Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Service
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Post Migration Checks

            You are here:

            1. Salesforce Help
            2. Docs
            3. Agentforce Service

            Post Migration Checks

            Platform User License (PUL) users and UEL users have different sharing behavior. Without the right controls, PUL users might edit cases they do not own or view internal case comments. Review the settings below to prevent unintended access. While validation is optional, we recommend completing these steps to ensure all features function as expected after the migration.

            Required Editions

            View supported editions.

            Verify Core License And Feature Settings

            Confirm that the required baseline settings are enabled for both UEL and PUL license types.

            • Set External Org-Wide Defaults (OWD) to Private for both license types.
            • For PUL users, set Internal OWD to Private.
            • Confirm the following are enabled (True) for both license types:
              • Person Accounts
              • Network features (Enabled, Member, and Internal User)
              • Employee Linkage

            Verify Security Settings

            Configure PUL users as requestor-only users and prevent unintended access.

            • Set internal Org-Wide Defaults (OWD) to Private.
            • Enable the NetworkOnlyInternalUser profile permission for PUL users who should have requestor-only access.
            • Use custom public groups to separate requestor-only PUL users from standard internal users.
            • Configure sharing rules so requestors get access to the correct records, independent of internal user groups.
            • Use Apex to ensure Chatter feeds and Case comments created by PUL users are marked public/external only.

            Verify Employee Record Permissions

            Protect employee data by limiting visibility and edit access.

            • Remove the View Employee user button unless all users should be able to access Employee information.
            • Restrict edit access on Employee records to admins only. Otherwise, users can change their own Employee Status, Start Date, and Employee Number.
             
            Loading
            Salesforce Help | Article