> ## Documentation Index > Fetch the complete documentation index at: https://support.parker.work/llms.txt > Use this file to discover all available pages before exploring further. # How Parker acts on your behalf > Learn which Salesforce changes Parker asks you to confirm, which it makes straight away, how email drafts work, and how Test and Live mode work. Parker reads your data freely. What happens when it changes something depends on the kind of change: * **Creating a Salesforce record** shows a card with **Confirm** and **Reject**. Nothing is written until you select **Confirm**. * **Updating fields on an existing Salesforce record** has no card. In **Live** mode, Parker makes the change as soon as you ask. * **Email** arrives as a draft card. Nothing is sent until you choose a send option. Your **Agent mode** decides whether Salesforce changes are real. In **Live** mode, they're written to Salesforce. In **Test** mode, they're only simulated. ## What does a confirmation look like? When Parker is ready to create a record, it lists what it will create. A line describes the exact change, such as "Create Task in Salesforce", followed by the field values. Under it are two options: * **Confirm** carries out exactly the change described. * **Reject** cancels it. Nothing is written. A proposed Salesforce task with subject, related opportunity, due date, and status, followed by Confirm and Reject buttons. After you decide, the buttons are replaced by a single line. It reads **Cancelled** if you rejected the change, followed by the description of the change. ## What happens when I ask Parker to update a record? Parker makes the change straight away. There's no **Confirm** card for a field update on an existing record. In **Live** mode, the change is written to Salesforce as you. Parker then shows the record, with the changed field highlighted, and the line **Updated by you; confirmed in Salesforce.** An opportunity card with Next Step set to Book site visit, highlighted, and the line Updated by you; confirmed in Salesforce. Be specific when you ask for an update. Name the record, the field, and the new value. In **Live** mode, Parker doesn't ask again before it writes. See [Create and update records](/chat/updating-records). ## How does sending email work? When you ask for an email, Parker shows a draft card with **To**, **From**, **Subject**, and the message. You can edit the subject and message. Select **Shorter**, **Warmer**, or **Formal** to have Parker rewrite it. Email draft card with To, From, Subject, and body, a Compliant badge, and Save to drafts and Send buttons. Then choose what happens: | Option | What happens | | - | - | | **Send** | Parker sends the email from your connected mailbox. | | **Save to drafts** | Parker saves the email to your mailbox's Drafts folder. Nothing is sent. | | **More send options** (the arrow next to **Send**) | Choose **Send now**, **Send in 1 hour**, or **Send tomorrow at 9:00am**. Or choose **Open in Outlook**, **Open in Gmail**, or **Open in Mail** to finish the email in your mail app. | | **More actions** (**…**) > **Discard draft** | Parker drops the draft. | The badge on the card, such as **Compliant · 1 rule**, shows the result of your workspace's compliance check. For more, see [Draft and send email](/email/drafting-email). ## Test mode and Live mode Each person has their own Salesforce **Agent mode**, with two settings: * **Test:** Parker only simulates Salesforce changes. Nothing is sent to Salesforce. * **Live:** Parker writes changes to Salesforce, as you, under your own Salesforce permissions. Every write is audited. Go to **Settings** > **Connections**, and then select the **Salesforce** row. Under **How Parker works in Salesforce**, set **Agent mode** to **Test** or **Live**. How Parker works in Salesforce section with Agent mode set to Live, a Writes row listing Case, Lead, Opportunity, CaseComment, and Task, and Sync. The **Writes** row under **Agent mode** lists the Salesforce objects Parker can change in your workspace. ## Which actions are confirmed, and which aren't? | What Parker does | How it checks with you | | - | - | | Reads Salesforce, email, files, or knowledge | No confirmation. Reading changes nothing. | | Creates a Salesforce record | **Confirm** and **Reject**. | | Changes fields on an existing Salesforce record | No card. In **Live** mode, Parker writes the change straight away. In **Test** mode, it's simulated. | | Sends an email | The draft card. Nothing sends until you choose a send option. | ## What can my admin change? Admins decide some things for the whole workspace: * **Org-wide test mode.** In the **Salesforce** settings, under **Admin**, this setting forces every user to **Test** mode, regardless of their own setting. * **Send mode.** In **Settings** > **Agent** > **Autonomy**, an admin chooses how far Parker can act without a person checking first. The options are **Review**, **Auto when confident**, and **Auto all**. Each reply is labelled **Draft** or **Auto-sent**. See [Autonomy](/admin/autonomy). * **Rules and compliance.** Admins set the rules Parker follows and the compliance checks emails must pass. See [Rules](/admin/rules) and [Compliance](/admin/compliance). ## Related Create and change Salesforce records from chat. Write, edit, and send email with Parker. Check what your automations drafted and did. For admins: set how replies are sent. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.