You can assign actions or playbook blocks to a specific user or SOC role in the
playbook designer. The assignee decides the outcome of the manual action or
playbook block for the playbook run. You have the option to include a message
about the action that needs to be taken by the assignee. You can also enable
Time to respond and add in the time they have to complete the action.
The timer starts the countdown from when the playbook reaches that part of the
flow.
If they don't respond in the time allotted to the action, the action will fail.
When you build your playbook, make sure to use If Step fails to decide
whether to stop the playbook entirely at this stage or skip this step. You can
also use the conditional step If previous Step failed in order to push
the playbook flow in a different direction.
Select the user or SOC role from the Assign To list.
Add a message explaining what needs to be done. You have the option to
insert a placeholder in your message. This message will be displayed to the
user in the Pending Actions widget in the case overview and in
Your Workdesk
Optionally, enable Time to respond and enter the time that the action
needs to be completed by.
If the user does not respond in the time selected here you can choose to use
the If Step fails together with If previous action fails in the
next playbook conditional step in order to control the flow.
Click Save.
After a playbook is triggered, usually following an alert being ingested into
the platform, it runs until it gets to the manual action. This action appears
in the Pending Actions widget in the case overview and in
Your Workdesk. The user needs to execute or skip the action.
Assign playbook blocks
Open the required playbook with an existing block.
Double-click the playbook block. Note that the block is displayed in green.
Select Manual Action from the Action Type list.
Select the user or SOC role from the Assign To list.
Add a message explaining what needs to be done. You have the option to insert a
placeholder in your message. The user will receive a message when their input is
required.
If required, enable the Time to Save field and enter the time for the
assignee to approve or decline the playbook block.
Click Save.
After a case has been ingested into the platform and an alert triggers the
playbook, it runs until it gets to the manual action. The manual action appears
in the Pending Actions widget in the case overview and alert overview or
on Your Workdesk. If the Time to respond field has been filled
out, then a ticker will appear with the time the user has left to respond to
this action.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eActions or playbook blocks within Google SecOps SOAR can be assigned to specific users or SOC roles via the playbook designer.\u003c/p\u003e\n"],["\u003cp\u003eWhen assigning actions, a message can be included to explain the required task to the assignee, with the option to insert placeholders.\u003c/p\u003e\n"],["\u003cp\u003eA "Time to respond" can be set for manual actions or playbook blocks, with the ability to define how the playbook should proceed if the time limit is exceeded.\u003c/p\u003e\n"],["\u003cp\u003eManual actions in playbooks will appear in the "Pending Actions" widget and the "Your Workdesk" section, prompting the assigned user to execute or skip the action.\u003c/p\u003e\n"],["\u003cp\u003eThe "If Step fails" and "If previous Step failed" conditional steps can be used to control the playbook's flow based on whether a manual action or playbook block was successfully completed within its designated timeframe.\u003c/p\u003e\n"]]],[],null,["# Assign actions and playbook blocks\n==================================\n\nSupported in: \nGoogle secops [SOAR](/chronicle/docs/secops/google-secops-soar-toc) \n\nYou can assign actions or playbook blocks to a specific user or SOC role in the\nplaybook designer. The assignee decides the outcome of the manual action or\nplaybook block for the playbook run. You have the option to include a message\nabout the action that needs to be taken by the assignee. You can also enable\n**Time to respond** and add in the time they have to complete the action.\nThe timer starts the countdown from when the playbook reaches that part of the\nflow.\n\n\nIf they don't respond in the time allotted to the action, the action will fail.\nWhen you build your playbook, make sure to use **If Step fails** to decide\nwhether to stop the playbook entirely at this stage or skip this step. You can\nalso use the conditional step **If previous Step failed** in order to push\nthe playbook flow in a different direction.\n\n\nFor more information on assigning actions to end users, refer to\n[Assign Approval Links in Actions](/chronicle/docs/soar/respond/working-with-playbooks/assign-approval-\nlinks-in-actions).\n\nAssign an action in a playbook\n------------------------------\n\n1. Double-click the required action in the playbook.\n2. Select **Manual** from the **Action Type** list.\n3. Select the user or SOC role from the **Assign To** list.\n4. Add a message explaining what needs to be done. You have the option to insert a placeholder in your message. This message will be displayed to the user in the **Pending Actions** widget in the case overview and in **Your Workdesk**\n5. Optionally, enable **Time to respond** and enter the time that the action needs to be completed by. \n If the user does not respond in the time selected here you can choose to use the **If Step fails** together with **If previous action fails** in the next playbook conditional step in order to control the flow.\n6. Click **Save**.\n\n\nAfter a playbook is triggered, usually following an alert being ingested into\nthe platform, it runs until it gets to the manual action. This action appears\nin the **Pending Actions** widget in the case overview and in\n**Your Workdesk**. The user needs to execute or skip the action.\n\nAssign playbook blocks\n----------------------\n\n1. Open the required playbook with an existing block.\n2. Double-click the playbook block. Note that the block is displayed in green.\n3. Select **Manual Action** from the **Action Type** list.\n4. Select the user or SOC role from the **Assign To** list.\n5. Add a message explaining what needs to be done. You have the option to insert a placeholder in your message. The user will receive a message when their input is required.\n6. If required, enable the **Time to Save** field and enter the time for the assignee to approve or decline the playbook block.\n7. Click **Save**.\n\n\nAfter a case has been ingested into the platform and an alert triggers the\nplaybook, it runs until it gets to the manual action. The manual action appears\nin the **Pending Actions** widget in the case overview and alert overview or\non **Your Workdesk** . If the **Time to respond** field has been filled\nout, then a ticker will appear with the time the user has left to respond to\nthis action.\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]