---
schema_version: "1"
id: cf6bd3cb6af257d19f4b854371aacfd2056a723623302f86c80d1fef73b0690a
title: Submit a Record for Approval from a Process
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/process_action_submit.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.process_action_submit.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a97cb4b1fed1bb1263ff3c0667c66adf13552fee64e99b60e43a8bfa1f946f4a
description: Submit the record that started the process for approval.
products:
- Flow Builder
- Salesforce Platform
release: "264"
---
# Submit a Record for Approval from a Process
Submit the record that started the process for approval.
### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions
User Permissions Needed
To create, edit, or view processes:
Manage Flow
AND
View All Data
Important Support and updates for Process Builder have ended as of December 31, 2025. This means that support won't be provided for any process and bugs in the Process Builder product won't be fixed. See [Workflow Rules & Process Builder End of Support](https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US).
After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your [switch to Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow_learning_map.htm&release=264.0.0&type=5 "Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.") and use the [Migrate to Flow](https://help.salesforce.com/s/articleView?id=platform.flow_migrate_to_flow.htm&release=264.0.0&type=5 "Use the Migrate to Flow tool to convert your Process Builder processes and workflow rules into Flow Builder, including scheduled actions. The tool also supports partial migration of processes for most actions.") tool. For new automations, create flows in [Flow Builder](https://help.salesforce.com/s/articleView?id=platform.flow.htm&release=264.0.0&type=5 "Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.").
After you’ve created an action and selected “Submit for Approval” for the type, fill in the relevant fields to add the action to your process.
Only the record that started the process is submitted. You can’t submit any related records for approval.
1. Enter a name for this action. This text appears on the canvas and helps you differentiate this action from others in your process. The name truncates to fit on the canvas.
2. For Approval Process, indicate whether to submit the record through the default approval process or through a specific approval process.
The process fails if:
- The record is submitted to the default approval process, and there are no active approval processes for the record’s object type.
- The record is submitted to the default approval process, and it doesn’t meet the criteria for any of the approval processes for the record’s object type.
- The record is submitted to a specific approval process, and it doesn’t meet the entry criteria.
3. To submit the record to a specific approval process:
1. Search for and select the approval process.
2. Indicate whether to skip the entry criteria for the approval process.
4. For Submitter, identify who receives notifications about the approval request.
| Value | Description |
| --- | --- |
| Current User | The user who triggered the process by creating or editing a record. |
| User Field from a Record | The user ID that’s stored in a field value on the record that’s being submitted for approval or another record. |
| Other User | A specific user in your organization. |
If the submitter isn’t an allowed initial submitter on the approval process that runs, the process fails. Make sure that the initial submitters for the approval processes that are related to this object include all users who could trigger this process. For details about setting the initial submitters for an approval process, see [Create a Classic Approval Process with the Standard Wizard](https://help.salesforce.com/s/articleView?id=platform.approvals_creating_approval_processes.htm&release=264.0.0&type=5 "When your classic approval process is more complex and you want to define specific steps, use the standard wizard.").
Any user with the "Modify All Records" permission to the object is allowed to submit a record for approval. They’re permitted to submit the record, even if they aren’t listed as initial submitter.
5. If necessary, enter submission comments. Don’t reference merge fields or formula expressions.
Submission comments appear in the approval history for the specified record. This text also appears in the initial approval request email if the template uses the `{!ApprovalRequest.Comments}` merge field.
6. Save the action.