--- title: "Send SignNow Template as the current user" url: "https://docs.signnow.com/docs/apex-send-template-current-user" type: "page" section: "Integrations" slug: "apex-send-template-current-user" --- # Send SignNow Template as the current user # Send SignNow Template as the current user Send invites from Salesforce in each user's own name, so recipients see the person they work with, not a shared admin. SignNow Apex actions send invites on behalf of the integration user set in the **SignNow Settings** custom settings. To send an invite as the user who triggers the flow, add an **Update Records** element before the [Send SignNow Template](/docs/apex-send-template) action that sets **Integration User ID** to the running user's ID. The invite is then sent from that user's SignNow account: their email appears as the sender in the [Invites Status widget](/docs/salesforce-invites-status-widget), and recipients get the invite email from their name. > [!NOTE] > Before configuring this flow, review the [prerequisites](/docs/salesforce-apex-actions#prerequisites) for SignNow Apex actions and the [Send SignNow Template](/docs/apex-send-template) action. ## Before you start To configure the flow, use a Salesforce user with the System Administrator profile or a custom profile with equivalent permissions. Make sure that every Salesforce user who triggers the flow: - Has a Salesforce user license that allows Visualforce page access. - Has the **SignNow Set** permission set assigned. See [Assign the SignNow permission set](#assign-the-signnow-permission-set). - Has logged in to SignNow at least once through the [Invites Status widget](/docs/salesforce-invites-status-widget) on a Salesforce record page. Each user logs in to Salesforce with their own credentials, opens a record with the widget, clicks **Log in**, and grants access with their own SignNow account. - Has a SignNow account in the same workspace as the template that the flow sends. If you add a SignNow document flow to the action, configure it to send without sender input: hide all sender screens and set an email address or tag for every recipient. See [Document flows](/docs/document-flows). ### Assign the SignNow permission set Go to **Setup > Users** and open the user. Click **Permission Set Assignments**. ![User detail page with the Permission Set Assignments link highlighted](/reference-assets/images/SignNow_Salesforce/apex_actions/apex_current_user_permission_set_assignments.png) Click **Edit Assignments**, move **SignNow Set** to **Enabled Permission Sets**, and click **Save**. ![SignNow Set in the Enabled Permission Sets list](/reference-assets/images/SignNow_Salesforce/apex_actions/apex_current_user_enable_permission_set.png) To assign the permission set to several users at once, go to **Setup > Permission Sets > SignNow Set** and click **Manage Assignments**. ## Step 1. Configure the flow trigger Create a record-triggered flow as described in [Send SignNow Template](/docs/apex-send-template#step-1-configure-the-flow-trigger). In this example, the flow runs when the name of an Account is changed: - **Object**: Account - **Trigger the Flow When**: A record is updated - **Entry condition**: Account Name, Is Changed, True - **Optimize the Flow for**: Actions and Related Records ![Configure Start panel of a record-triggered flow on Account with the Account Name Is Changed entry condition and Actions and Related Records selected](/reference-assets/images/SignNow_Salesforce/apex_actions/apex_current_user_flow_trigger.png) ## Step 2. Set the current user as the integration user Click the **+** icon after the trigger and add an **Update Records** element. Configure it as follows: - **How to Find Records to Update and Set Their Values**: Specify conditions to identify records, and set fields individually - **Object**: SignNow Settings - **Condition Requirements to Update Records**: None—Update All cuda_signnow__universal_signnow_helper__c records - **Set Field Values**: Integration User ID ← Running User > Id ![Update Records element setting Integration User ID to Running User > Id in SignNow Settings](/reference-assets/images/SignNow_Salesforce/apex_actions/apex_current_user_update_records.png) ## Step 3. Add the Send SignNow Template action Click the **+** icon after the **Update Records** element and add the **Send SignNow Template** action. Specify the input values: - **Record ID**: Triggering Account > Account ID - **SignNow Template ID**: the ID of the template to send. Copy it on the **SignNow Admin Tools > Templates** page. - **SignNow Document Flow ID** (optional): the ID of a document flow configured to send without sender input. Copy it on the **SignNow Admin Tools > Document Flows** page. ![Flow with Update custom records followed by the Send SignNow Template action and its input values](/reference-assets/images/SignNow_Salesforce/apex_actions/apex_current_user_send_template.png) Click **Save**, then **Activate**. ## Step 4. Check the result Before the flow runs, **Setup > Custom Settings > SignNow Settings > Manage** shows the admin's ID in **Integration User ID**. ![SignNow Settings with the admin's ID in Integration User ID](/reference-assets/images/SignNow_Salesforce/apex_actions/apex_current_user_settings_before.png) After a user triggers the flow, the same field shows that user's ID. ![SignNow Settings with the triggering user's ID in Integration User ID](/reference-assets/images/SignNow_Salesforce/apex_actions/apex_current_user_settings_after.png) Open the record in Salesforce. In the **Invites Status widget**, each invite shows the SignNow account of the user who triggered the flow as the sender. Recipients get the invite email from the name and email address of that user. ![Invites Status widget showing two invites of the same template from different senders](/reference-assets/images/SignNow_Salesforce/apex_actions/apex_current_user_widget_senders.png) > [!WARNING] > The Integration User ID keeps the last triggering user's ID after the flow finishes. Every SignNow Apex action that runs after the **Update Records** element, in this flow or in other flows, sends as that user. If other flows must send as the admin, add an **Update Records** element that sets **Integration User ID** back to the admin's user ID before their SignNow actions. To see which flows run on the same object and in what order, open **Flow Trigger Explorer** from **Setup > Flows**. ## Send a document group that already exists **Send SignNow Template** creates a document group from the template and sends it in one step. To send a document group created earlier, for example with [Create SignNow Document Group from Template](/docs/apex-create-document-group-from-template) or [Generate Document via SignNow](/docs/apex-generate-document), use one of the following: - Call [`POST /documentgroup/{document_group_id}/groupinvite`](/docs/doc-group-field-invite/operations/invite-to-sign-document-group) from Apex to send it without opening SignNow. - Use [Get SignNow Send Invite URL](/docs/apex-get-send-invite-url) to let the user review and send it in SignNow. ## Troubleshooting | Issue | Solution | | --- | --- | | The invite stays in **Draft** in the Invites Status widget. | The document flow waits for input from the sender. In **SignNow Admin Tools > Document Flows**, hide all sender screens and set an email address or tag for every recipient. Check that recipient tags point to fields with values on the triggering record. | | Salesforce shows *Can't assign permission set SignNow Set to user. The user license doesn't allow Visualforce Page Access.* | In **Setup > Users**, edit the user and select a user license that allows Visualforce page access, then assign the permission set. | For other issues, see [Troubleshooting](/docs/salesforce-troubleshooting). --- View the full list of [SignNow Apex actions](/docs/salesforce-apex-actions). --- *Full page: https://docs.signnow.com/docs/apex-send-template-current-user*