> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/decide/decision.md). # Decision You can send a customized message to a recipient, asking to choose between one and four options. The workflow execution waits for the recipient to select an outcome before proceeding, and then branches out to new actions depending on the recipient's decision. You can send the decision request for a user’s action via one or more of these platforms: * [Email](#decide-by-email) * [Slack](#decide-in-slack) * [DoControl](#decide-in-docontrol)

A Decision action with several options

## **Add a decision** 1. From the **Actions** left pane, select **Decide > Decision**. Drag the **Decision** action to the canvas, and connect it to the previous action. 2. Click the action to open its settings. 3. Enter an appropriate description for the action (optional). 4. Enter between 1-4 decision actions, and click **Enter** after each option. \ For example: Remove sharing, Keep for 1 month, Notify actor.\ You can enter up to **30 characters** for text in action buttons.

Each decision action is indicated with a different color

5. Write the [decision message.](#write-the-decision-message) 6. In the workflow, connect each decision option to its relevant action.\ For example: * **Remove sharing** > Remove collaborator * **Keep for 1 month** > Wait * **Notify actor** > Notify in Slack * You can also create a [loop](/docontrol-user-guide/workflows/define-workflow-settings/action-settings.md#loops) connection between a **Decision** action and any previous action in the workflow. * After adding new actions, click on each action to open its settings, and enter values in the relevant fields. 7. Once the user chooses a specific option, you'll be notified in Slack:
## Write the decision message You can send more than one decision request via email, Slack or DoControl, but the recipient can decide only once. {% hint style="info" %} * The **decision** buttons are displayed automatically in the message. * If the decision message is sent to more than one recipient, a notification message is displayed to a recipient who tries to choose an option for a step that was already decided: \ `Your request has already been handled.` {% endhint %} ### **Decide by email** Use a predefined template or the default email template to send a decision request.
1. In the Decision action, click the **Email** tab. 2. Enter the required fields in your email: subject, to, message, and timeout duration. The other fields are optional.
Email fieldRequiredDescription
SubjectRequiredSubject line of the email.
To (recipients as bcc)RequiredPeople receiving the email (blind carbon copy).
From (sender name)OptionalPerson sending the email: You can customize the displayed name, but the email address remains unchanged: <no-reply@docontrol.io>
MessageRequired

Edit mode - Type the content for your email.

Preview mode - View how your email will be displayed.

3. If you wish to allow recipients outside of your trusted domains to decide, turn on the **Allow external responses** button. If you disable this option, the option buttons won't appear in the email. 4. Click the **Plus** icon to add [dynamic values](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings#dynamic-data) to include details from the event, workflow, or select input and output fields from previous actions. 5. Click [Templates](/docontrol-user-guide/system-management/settings/email-templates.md) to use a predefined email template. 6. Enter a timeout duration (required). If the recipient ignores the email, you need to define after what interval to run the timeout logic. The default timeout is 1 day. {% hint style="info" %} * To configure customized templates for email notifications, see [email templates](https://docs.docontrol.io/docontrol-user-guide/system-management/settings/email-templates). * For security reasons, you cannot use hyperlink tags \ in an email message except for supported [hyperlink tags.](#hyperlink-tags) If you use a DoControl [email template](/docontrol-user-guide/system-management/settings/email-templates.md), you can insert any hyperlink tag. {% endhint %} ### **Decide in Slack** You can send a decision request via a Slack message to specific Slack channels or users. If you wish, you can enable any member in a Slack channel to decide the course of action.
{% hint style="info" %} For security reasons, you cannot use hyperlink tags \ in a Slack message except for supported [hyperlink tags.](#hyperlink-tags) {% endhint %} 1. In the Decision action, click the **Slack** tab. 2. To send a Slack message to a **public** channel: select a Slack public channel from the dropdown list. 3. To send a Slack message to a **private** channel: * Go to your private channel, and click the channel name to view the channel details. * Scroll to the bottom and copy the **channel ID**. * Enter the channel ID for a private Slack channel. * Make sure to invite the **DoControl app** to each private channel. 4. To send a Slack message to **users**: Select Slack users in your organization to whom to send the decision message. 5. Write your decision message: ![](https://docs.docontrol.io/~gitbook/image?url=https%3A%2F%2F3236294211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MesrnyDMZGYg1V-tOBo%252Fuploads%252F25lV4ove5X8jg9huISiO%252FEdit%2520icon%25202.png%3Falt%3Dmedia%26token%3D6e9ca545-9678-4764-979a-997823fa8c72\&width=300\&dpr=4\&quality=100\&sign=3901bb81\&sv=1) **Edit** mode - Type the content for your message. ![](https://docs.docontrol.io/~gitbook/image?url=https%3A%2F%2F3236294211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MesrnyDMZGYg1V-tOBo%252Fuploads%252FOrawP5hA8I90zytiW2D2%252FPreview%2520icon%25202.png%3Falt%3Dmedia%26token%3Dbfa02140-326e-4b3e-9bac-0494af74723a\&width=300\&dpr=4\&quality=100\&sign=250d8e89\&sv=1) **Preview** mode - View how your message will be displayed. 6. Click the **Plus** icon to add [dynamic values](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings#dynamic-data) to include details from the event, workflow, or select input and output fields from previous actions. 7. Click **Allow direct decision in Slack** if you wish to enable any member in the Slack channel to decide the course of action. 8. Enter a timeout duration (required). If the recipient ignores the message, you need to define after what interval to run the timeout logic. The default timeout is 1 day. The selected channels or users receive a link for deciding the course of action. Recipients can select the relevant option directly from the Slack message. ### **Decide in DoControl** The DoControl app is the default method for sending the decision request. The decision request is displayed inside the workflow activity waiting for you to take action.
1. In the Decision action, click the **DoControl** tab. 2. Write your approval message:\ ![](https://docs.docontrol.io/~gitbook/image?url=https%3A%2F%2F3236294211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MesrnyDMZGYg1V-tOBo%252Fuploads%252F25lV4ove5X8jg9huISiO%252FEdit%2520icon%25202.png%3Falt%3Dmedia%26token%3D6e9ca545-9678-4764-979a-997823fa8c72\&width=300\&dpr=4\&quality=100\&sign=3901bb81\&sv=1) **Edit** mode - Type the content for your message.\ ![](https://docs.docontrol.io/~gitbook/image?url=https%3A%2F%2F3236294211-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-MesrnyDMZGYg1V-tOBo%252Fuploads%252FOrawP5hA8I90zytiW2D2%252FPreview%2520icon%25202.png%3Falt%3Dmedia%26token%3Dbfa02140-326e-4b3e-9bac-0494af74723a\&width=300\&dpr=4\&quality=100\&sign=250d8e89\&sv=1) **Preview** mode - View how your message will be displayed. 3. Click the **Plus** icon to add [dynamic values](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings#dynamic-data) to include details from the event, workflow, or select input and output fields from previous actions. 4. Enter a timeout duration (required). If the approver ignores the message, you need to define after what interval to run the timeout logic. The default timeout is 1 day. ## Hyperlink tags in messages For security reasons, you cannot use hyperlink tags \ in an email, Slack message or DoControl webhook, except for these HTML tags: * \ and \ - italics * \ - strikethrough * \
    and \
  • - unordered list * \
      and \
    1. - ordered list * \
      - line break * \

      - paragraph * \

      - heading 1 * \

      - heading 2 * \
      - section * \ - inline element {% hint style="success" %} If you wish to insert any other HTML tag, you can do so from a DoControl [email template](/docontrol-user-guide/system-management/settings/email-templates.md). {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/decide/decision.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.