--- title: "Configuring Assigned Form Task Assignees" slug: "assigning-form-interactions-as-tasks" description: "This document demonstrates how to assign a Form interaction as a task. This will in turn cause this Form interaction, to appear under a user's Task list, and that user will be sent the task via Email as well." tags: ["Forms", "Inbox", "assignments"] updated: 2025-06-18T16:19:46Z published: 2025-06-18T16:19:46Z --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring Assigned Form Task Assignees ## Overview By creating [**Assignments**](https://documentation.decisions.com/v9/docs/creating-a-task-from-a-flow), **Administrators**can assign **Forms**and **Tasks**to specific **User****Accounts**or **Groups**for completion. The principal effect of assigning a Form is that it appears in the **Tasks**list (**Inbox**in the **Decisions****Studio**/**Portal**) of every person to whom it is assigned. Additionally, by default, the **Assignee**is sent an **Email**to that task to their respective **Email****Address**associated with their Account. By utilizing the **Properties**provided in an **Assignment**, users may declare a designated **Assignee** by inputting an **Email****Address**, **Group****Name**, or an **Account****Name**that matches an existing Account in a Decisions environment. The following document discusses the options for Assignee configuration within a **Flow**. --- ## Assignment Type **Assigned****Forms**in **Flows**offer four primary **Assignee**configurations via the **Assignment****Type**Input found in the **Properties**tab of a **Form**. | **Option** | **Function** | | --- | --- | | InSession | Assigns the Assignment automatically to the current user of the Flow running the form. This is useful in processes involving multiple Forms; the first Form could be set to Assigned and then subsequent forms could use an InSession Assignment Type, which would direct the assignment to the initial Assignee. | | Assigned | Assigns the Form to a user-defined Assignee. This can be a specific Account(s), Group(s), Permission(s), Email(s) or Role(s). These assignees are added via the Assign To Input that appears upon selection of this type. The Assigned Assignment Type enables the Assignment Setup (see following section) category of settings, allowing users to specify more detailed aspects of the Assignment. | | [AssignedToGuest](https://documentation.decisions.com/v9/docs/using-guest-account-for-tasking-enabling-non-portal-users-to-interact-with-flow) | Assigns the Form to a Guest Account via Email. This particular option is helpful in situations that require an anonymous response to a task. | | AssignedToNamedSession | Assigns the Form to a designated Named Session allowing the ability to pass in user credential without exposing their respective Account information. Named Sessions are selected via the Named Session Entity Picker. | --- ## Assignment Setup Selecting the **Assigned**from the **Assignment****Type**options,****provides the [**Assignment****Setup**](https://documentation.decisions.com/v9/docs/assignment-settings#assignment-setup)****category in the**Properties**tab. Selecting the EDIT button beside the Property provides some additional configurations relating to **Assignment****Data**, **Assignees**, and **Assignment****Dates**. The **From Data** **Properties**allow the ability to map in specific **Accounts**, **Groups**, and **Roles**as recipients of an **Assigned****Form**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-18_12h15_11(1).png) ### Assignment Using an Array of Users/Groups From the **Accounts and Groups** **Input** in the **Assignment Setup Properties**, a combination of **User****Accounts**and/or **Groups**, can be specified as the origin of the **Assignment**. This option can be used to pass in variables representing an **Email****Address**, even for a single user. If desired, by changing the mapping to **Build****Array**, multiple **Email****Addresses**may be mapped as an individual **List of String**; this mitigates the limitations of only being able to provide a single **String**value as input; subsequent addresses may be added to the List via the ADD link. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-18_12h17_26.png) ### Assignment Roles The [**Assignment Roles**](https://documentation.decisions.com/v9/docs/creating-and-using-assignment-roles)****option allows for a **Task**to be assigned to any **User****Account**or **Group**defined as having a designated **Role**. These Roles are specified in the **Decisions****Studio**via **System > Common Data Elements >****Assignment Roles**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-18_12h18_17.png) ### Exclude Accounts and Groups If a specific **Group**is designated by the **Accounts**and **Groups****Input**, but a user wants to exclude a part of that Group, they may use the **Exclude Accounts and Groups** Property. For example, if a group called "TestGroup" containing a specific user and others is designated in **Accounts and Groups** and that user is designated in the **Exclude Accounts and Groups** setting, all users within the Group besides the specified exclusion will receive the **Assignment**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-18_12h19_16.png) --- For further information on Forms, visit the [Decisions Forum](https://community.decisions.com/categories/Forms).