> ## Documentation Index > Fetch the complete documentation index at: https://support.fieldko.com/llms.txt > Use this file to discover all available pages before exploring further. # Approvals > Add Salesforce approvals for leave requests, large FieldKo orders, and field campaign sign-off without blocking reps' syncs. Salesforce approvals route a record to one or more people for sign-off, and can lock the record while it waits. Use this page to decide where approvals fit with FieldKo: leave requests, large orders, and field campaign sign-off. Reps can't approve or submit records for approval from the FieldKo Atlas app, so approvers work in Salesforce, and approvals start automatically when rep records arrive. You can build approvals as classic approval processes, or as flow-based approvals in Flow Builder if your edition and licenses include them. For the basics, see [Approvals](https://help.salesforce.com/s/articleView?id=sf.what_are_approvals.htm\&type=5) in Salesforce Help. ## User Permissions Needed | To do this | You need | | - | - | | Create approval processes | Customize Application permission | | Create flows that submit records for approval | Manage Flow permission | ## Plan Approvals Around Sync Keep these FieldKo behaviors in mind for every approval: * **Submit automatically.** Records from the app arrive when the rep syncs, and the app has no **Submit for Approval** button. Use a record-triggered flow with the **Submit for Approval** action to start the approval when the record is created. * **Locked records can't be updated from the app.** If a rep edits a record offline while it's locked for approval, the change fails at the next sync and shows as an issue in **Sync History**. Lock only records reps don't edit after they submit them, or unlock the record in your approval process. * **Bypass integrations.** Skip the submit flow for integration users. See [Bypass Your Flows for Integration Users](/platform/automate/design-automation#bypass-your-flows-for-integration-users). ## Leave Requests The leave object isn't part of the FieldKo packages. If your org has its own leave object and you've added it to **Objects To be Fetched**, reps can submit [leave requests](/field-work/leave-requests) from the app. Reps can't edit a request in the app after they submit it, so locking it during approval doesn't affect them. To route leave for approval: 1. Create an approval process on your leave object, with the rep's manager as the approver. 2. Create a record-triggered flow on the leave object that runs when a record is created, and submits it for approval. 3. Optional: Add a field that shows the approval status, and add it to the leave layout so reps see the result after they sync. When leave is approved, hand the rep's visits for those dates to another rep with [Transfer Visits](/managers/field-campaigns#transfer-visits). ## Large Orders Use an approval when orders above a set value need sign-off, for example from a key account manager. The **Status** picklist on **FieldKo Order** comes with the values **Draft** and **Activated**, and your org can add more. In the app, reps choose a status at checkout from the values available for the order's record type, except **Sent** and **Send Failed**, which the app never offers. Follow these rules so your approval doesn't conflict with FieldKo: * **Track approval in its own field.** Add a picklist, such as **Approval Status**, and keep it off the layouts reps see in the app. If you add an approval value to **Status** instead, reps can select it themselves at checkout. * **Don't use Sent or Send Failed** in your approval steps. * **Submit on create.** Trigger your submit flow when a FieldKo order is created with **Order Amount** at or above your threshold. The app sets **Order Amount** when the rep places the order. An approval doesn't stop order emails. If you schedule `SendOrderMailsSchedular`, it emails each order's PDF to the order's contact once the PO date arrives and all its order lines have synced, whatever the order's status or approval. If customers must not receive unapproved orders, don't schedule the job, or send order emails from your own flow after approval. See [Emailing Orders](/admin/products-ordering-ranging#emailing-orders). ## Field Campaign Sign-Off FieldKo creates a field campaign's visits as soon as you assign reps, so an approval on the **Field Campaign** record itself can't hold visits back. Choose the kind of sign-off you need: | Sign-Off | How to Set It Up | | - | - | | Approve the plan before visits go out | Create your own campaign request object with an approval process. Create the field campaign only after the request is approved. | | Sign off results when the campaign ends | Create an approval process on **Field Campaign**, and submit it when **Percentage of Visits Completed** reaches your target or the **To** date passes. | Field campaigns also have a **Status** picklist with the values **Planned**, **In Progress**, **Completed**, and **Aborted**, which you can use in approval entry criteria. To learn how campaigns create visits, see [Run Field Campaigns](/managers/field-campaigns). ## See Also * [Design Automation for FieldKo](/platform/automate/design-automation) * [Flow Recipes for Field Teams](/platform/automate/flow-recipes) * [Notifications and Email Alerts](/platform/automate/notifications) * [Set Up Products, Ordering, and Ranging](/admin/products-ordering-ranging) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.