> For the complete documentation index, see [llms.txt](https://docs.activist.org/activist/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.activist.org/activist/product/planned-features/integrations.md).

# Tasks

Kanban boards for organizing the work to be done

Users will be able to attach kanban boards to every organization, group and event. This will allow those involved to easily plan and keep an overview of progress while templates guide organizers with best practices from our community.

<figure><img src="https://1976788605-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaUnVQ5LV2g7mX7KfnX0A%2Fuploads%2FDmsDJnYAQNY0uxjVFftz%2FEvent%20Tasks.png?alt=media&amp;token=b2c3e387-279c-47d1-a155-09dc74835428" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please keep in mind, that these designs might be out of date and do not always reflect the current state of development – if you want to help us with your design skills, please consider joining our [Design group](https://docs.activist.org/activist/organization/community/circles-and-groups.md#design).
{% endhint %}

### Getting done what is to be done

We hope to improve on our beloved pads. You want to know what is to be done? And who you can collaborate with? And where you can get help? Chatrooms simply are not great project management tools.

#### Kanban for activists

Agile development has changed how global teams collaborate on software – and we think activists can learn from this. Managing political projects is complex. A wide array of dependencies have to be handled in parallel with scarce resources and shifting priorities.

Who needs to to do what until when to ensure a successful campaign – or even simply a decent assembly?

#### See the work

Boards are giving you and your collaborators a visual representation of all the work packages, making it easier to understand the flow of tasks. To do, in progress, review, done.

This visual aspect helps teams quickly see the progress of each task, identify bottlenecks, and understand the overall workload.

#### Assign responsibilities

Organizations, groups and events will have dedicated boards that allow them to collaborate on their work – even across organizations and movements.

Tag users without sharing their email, phone number or other personal data and receive notifications if someone else needs your help.

#### Ask for help

There is a job that nobody in your organization can take care of?

Ping your supporters and if any of them have the necessary skill verified, they will receive a notification and will be linked up with you.

#### Keep an overview

Every organization, group and event can use a board to organize their tasks, but you don’t have to keep an eye out for all of the projects you are working on.

Every ticket you are tagged in will show up in your personal board, so you can quickly check-in what you still have to take care off – today.


---

# 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.activist.org/activist/product/planned-features/integrations.md?ask=<question>&goal=<user_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.
