> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/~/changes/eaCuYFhybbREuBouwZp6/client-profile/client-profile-settings/task-settings.md).
# Task Settings
Admins can configure the settings for the Tasks feature
## What is Task Settings?
Task Settings allows admins to set the name of task statuses that appear in the kanban view of the [tasks feature](/~/changes/eaCuYFhybbREuBouwZp6/tasks.md).
{% hint style="info" %}
**Why should you use Task Settings?**
*Unify your workflow: Make sure all tasks are categorized in a way that makes sense for your companie workflow, creating consistency and making it easy to track all work in progress.*
{% endhint %}
## How to configure Task Settings?
1. Navigate to: **Client Profile => Settings => Task Settings**
Task Settings
2. **Configuration options:**
👉 Tasks can have a name assigned to them, such as ‘in progress’ or ‘completed’, you can customize the task statuses from a preset list of options or set your own custom names:
Task Settings - Status Options
The statuses you configure in Task settings will appear as the statuses in the Tasks feature (eg. Draft, Ongoing, Complete, Onhold, Cancelled):
👉 You can also choose to “**Limit Sample Briefs"**:
Sample Briefs
Once you click 'Limit Sample Briefs' you can select which of the sample briefs you would like to appear in the [Briefs feature](/~/changes/eaCuYFhybbREuBouwZp6/briefs.md):
For example, only selecting 'Marketing Campaign' and then clicking 'Save Changes' will limit the available briefs that are selectable and useable in the [Briefs feature](/~/changes/eaCuYFhybbREuBouwZp6/briefs.md) to only the marketing campaign template brief:
If you have any questions about “Task Settings" or other features, don't hesitate to ask, we're always here to help!
---
# 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, and the optional `goal` query parameter:
```
GET https://support.hivo.co/~/changes/eaCuYFhybbREuBouwZp6/client-profile/client-profile-settings/task-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
.png?alt=media&token=50ddddc6-4f70-44d6-80f7-b3255c8e5f93)
.png?alt=media&token=c3a8caed-96e1-4f6d-b7db-8d31965f686f)
