> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/working-with-your-team/tasks.md).

# Tasks

How your team or accountant sends you questions and requests, and how to respond.

Tasks is how your team or accountant communicates with you inside Kick. Instead of emails back and forth, they assign you a task directly tied to the [transactions](/common-workflows/transactions.md) that need your attention.

***

### What you can do with Tasks

* **See what's assigned to you** with due dates and priorities
* **Review attached transactions** that need receipts, clarification, or a category update
* **Respond in context** using the task chat thread
* **Track status** as you work through open items
* **Create tasks** for your team or accountant when you need something from them

***

### When you receive a task

Your accountant or a teammate may assign you a task when they need something from you: a receipt, an explanation for a charge, or a decision on how to categorize a transaction.

1. Go to **Tasks** in the sidebar
2. Open the task to see the title, due date, priority, and any attached transactions
3. Use the chat thread to ask questions or share updates
4. Add a **Memo** on individual transactions when the explanation belongs on that charge (see below)
5. Set the task to **Done** when you're finished

You'll receive a daily digest at **6 AM PT / 9 AM ET** when:

* A new task is assigned to you
* Someone comments on one of your tasks
* A task is due that day

***

### Adding transactions to a task

When you need to flag specific transactions for your accountant or team, attach them directly to a task so everyone sees the same context.

1. Go to **Transactions** and select one or more transactions
2. In the footer at the bottom of the screen, click **Actions** (or press ⌘K)
3. Select **Create task** (or press T)
4. Fill in the task details and click **Create task**

The task displays the same columns shown in your Transactions view. Configure visible columns before creating the task to customize the table.

**Use this when:**

* You need a receipt or explanation for specific expenses
* You're flagging transactions for your accountant to review
* You're handing off a batch of uncategorized transactions to someone on your team

***

### Chat on a task

Each task has a chat thread for back-and-forth discussion with your accountant or team.

**Best practice:**

* Use the task chat for questions and status updates
* Add a **Memo** on the transaction when the explanation is specific to that charge

***

### Creating a task

You can also create tasks yourself when you need something from your accountant or team.

1. Go to **Tasks** in the sidebar
2. Click **New task**
3. Enter a title describing what needs to be done
4. Set the **Assignee**, **Due date**, **Entity**, and **Priority**
5. Click **Create task**

***

### Editing a task

1. Go to **Tasks** in the sidebar
2. Click any field to edit inline: Title, Due date, Entity, Priority, Assignee, Status
3. Click the task row to open the detailed view for comments and attachments

***

### Choosing the right tool

| Tool                  | Best for                                               | Where it lives              |
| --------------------- | ------------------------------------------------------ | --------------------------- |
| **Tasks**             | Questions, requests, and follow-ups tied to your books | Tasks tab                   |
| **Memo**              | A short note on a specific transaction                 | Memo column on Transactions |
| **Transaction links** | Quick questions when someone isn't in Kick             | Share via email or Slack    |


---

# 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.kick.co/working-with-your-team/tasks.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.