---
schema_version: "1"
id: 6d8adf630def7813d8f51c572b2d9958f7333fdd4bafed81411300486fc67ee6
title: Task Actions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/customize_wftasks.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.customize_wftasks.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 521381953ca521bae1b6dfb5affa315ef3634291bc9b272cc95c68f02983bcc2
description: Task actions determine the details of an assignment given to a specified user by an automated process. You can associate task actions with workflow rules, approval processes, or entitlement processes.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Task Actions

Task actions determine the details of an assignment given to a specified user by an automated process. You can associate task actions with workflow rules, approval processes, or entitlement processes.

### Required Editions

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience and Salesforce Classic</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

From Setup, enter Tasks in the Quick Find box, and select **Tasks**. Then use these settings to configure your task.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:13.003901170351103%">
          <col style="width:86.9960988296489%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d342909e87">Field</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d342909e90">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e87 ">Object</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e90 ">
              <p>Select an object for your task. Remember, tasks can only be
                associated with workflow rules or approval processes for the same
                object type. Choose an object that tracks activities. </p>
              <p style="margin-bottom:0;">Tasks
                aren’t available for article types.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e87 ">Assigned to</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e90 ">
              <p>Select an assignee for your task. An assignee can be in the form of a
                user, role, record owner, record creator, opportunity team role, or
                account team role, depending on the type of record you chose.
              </p>
              <ul>
                <li>If the assignee of a task is set to the record owner and the
                  owner of a lead or case is a queue, the task is assigned to
                  the person who triggered the rule.</li>
                <li>If a custom object has a master-detail relationship with
                  a standard object, the owner of the custom object record is
                  automatically set to the owner of the main standard object
                  record. For example, if a custom object called
                  “Expenses” has a master-detail relationship
                  with Accounts, the owner of each expense record is the owner
                  of the account for the expense.</li>
                <li>If the assignee of a workflow task is a role and more than one user belongs to that role, the
                  record owner becomes the task assignee, regardless of their role. We recommend
                  that you don’t assign tasks to roles with multiple users. Assigning tasks to
                  roles with one user allows you to easily change the user in that role without
                  modifying the workflow rule. If the assignee of a workflow task is a role and
                  that role is empty, the record owner becomes the task assignee, regardless of
                  their role.</li>
                <li><span id="customize_wftasks__WFLeadConvTask"><a name="customize_wftasks__WFLeadConvTask"><!-- --></a>When a lead is converted by someone
                    who isn't the lead owner, all workflow tasks associated
                    with the lead that are assigned to that user, except
                    email alerts, are reassigned to the lead owner. Workflow
                    tasks assigned to users other than the lead owner and
                    lead converter aren't changed.</span></li>
              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e87 ">Subject</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e90 ">Enter a subject for the task. Distinguish automated tasks from
              user-created ones by starting the subject with a specific notation, such
              as adding <kbd>(Automated)</kbd> at the end.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e87 ">Unique Name</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e90 ">
              <p>Enter a unique name to refer to this component in the API. The
                requirement for uniqueness is only within the selected object
                type. You can have actions of the same type with the same unique
                name, provided they’re defined for different objects. </p>
              <p style="margin-bottom:0;">
                <span>The <strong class="uicontrol">Unique Name</strong>
                  field can contain only underscores and alphanumeric characters.
                  It must be unique within the selected object type, begin with a
                  letter, not include spaces, not end with an underscore, and not
                  contain two consecutive underscores.</span>
              </p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e87 ">Due Date</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e90 ">
              <p dir="ltr">Choose a due date for the task. Due dates appear in the
                time zone of the assignee.</p>
              <p style="margin-bottom:0;">Configuring a task’s <strong class="uicontrol">Due
                  Date</strong> to "Rule Trigger Date" sets time triggers
                and workflow task due dates based on the date that the workflow time
                trigger’s action is executed. For example, if the task due date is
                "Rule Trigger Date plus 10 days" and the time trigger is
                executed on January 1, Salesforce sets the task due date to January
                11.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e87 ">Status</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e90 ">Choose a status for the task.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e87 ">Priority</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e90 ">Choose a priority for the task.</td>

          </tr>
          <tr class="">
            <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e87 ">Comments</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d342909e90 ">Enter comments for the task.</td>

          </tr>
        </tbody>
      </table>

Notice that all your tasks include a **Created By** field. For tasks, this field contains the name of the person who saved the record that triggered the rule to assign the task.

Tasks don't trigger task-based workflow rules if they’re created automatically, such as by clicking the **Send An Email** button or by using the Email to Salesforce BCC address field.

#### See Also

- [Associate Actions with Workflow Rules or Approval Processes](https://help.salesforce.com/s/articleView?id=platform.workflow_select_action.htm&release=264.0.0&type=5 "Associate actions that have already been created in your organization with a workflow rule and approval processes.")