> For the complete documentation index, see [llms.txt](https://docs.inopli.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inopli.com/rpa-soar/tasks.md).

# Tasks

The <mark style="color:green;">**Tasks**</mark> <mark style="color:green;"></mark><mark style="color:green;">section</mark> within the <mark style="color:green;">Inopli RPA</mark> module serves as a <mark style="color:green;">**dedicated environment for managing and automating daily SOC routines**</mark>, combining operational visibility with workflow-based automation. Presented in a <mark style="color:green;">**kanban-style interface**</mark>, this feature is designed to streamline recurring analyst activities through structured task flows and automated execution.

***

### Operational Flow

* <mark style="color:green;">**Predefined Columns**</mark>\
  The task board follows a fixed column structure: *<mark style="color:green;">Backlog</mark>*<mark style="color:green;">,</mark> <mark style="color:green;"></mark>*<mark style="color:green;">To Do</mark>*<mark style="color:green;">,</mark> <mark style="color:green;"></mark>*<mark style="color:green;">In Progress</mark>*<mark style="color:green;">,</mark> <mark style="color:green;"></mark>*<mark style="color:green;">Under Review</mark>*<mark style="color:green;">, and</mark> <mark style="color:green;"></mark>*<mark style="color:green;">Done</mark>*. This standardization ensures alignment across teams and supports consistent operational reporting.
* <mark style="color:green;">**Card-Based Automation**</mark>\
  Each task card has it's own <mark style="color:green;">**dedicated automation workflow**</mark>, allowing routine actions such as notifications, data validation, ticket creation, or escalation to be executed automatically when the task progresses. The workflow is fully visual and built with the same no-code interface used in the main Automations module.
* <mark style="color:green;">**Recurring and Triggered Tasks**</mark>\
  Teams can schedule <mark style="color:green;">**recurring task**</mark>**s** (e.g., daily log checks, threat feed reviews) .

***

### Designed for SOC Operations

* <mark style="color:green;">**SOC-Centric Templates**</mark>\
  The module includes task templates for <mark style="color:green;">**routine SOC activities**</mark> including shift handovers, IOC hunting, asset verifications, and healthchecks enabling fast setup and standardized execution.
* <mark style="color:green;">**Status Tracking and SLAs**</mark>\
  Each task can carry metadata like <mark style="color:green;">**priority, deadline, SLA**</mark>, and assignment to specific analysts. The system tracks progress and flags overdue or blocked tasks automatically.
* <mark style="color:green;">**Integrated Audit Trail**</mark>\
  All task actions and transitions are logged and auditable, ensuring compliance with internal operational procedures and facilitating post-incident reviews.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inopli.com/rpa-soar/tasks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.