Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Table of Contents
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
          Considerations for Approval Objects

          Considerations for Approval Objects

          This section covers considerations and limitations for approval objects and related records.

          Required Editions

          Available in: Lightning Experience
          Available in: Enterprise, Unlimited, and Developer Editions where Advanced Approvals is enabled
          • An approval request can be triggered only from supported objects. To check or request support for your object, contact your Salesforce admin.
          • The Approval Submission object controls the access to other approval objects. For example, if a user is given access to the Approval Submission object, they get access to a submission’s child records, such as submission details and work items.
          • By default, all approval records are set to Private to restrict their visibility to relevant users.
          • If a related record’s access is set to Public Read Only, all users automatically get access to its approval submissions and work items. However, if it's set to Private, you can share temporary access to the related record using Apex triggers. See Share Temporary Access to Records in Advanced Approvals.
          • You can't manually share access to approval submission records.
           
          Loading
          Salesforce Help | Article