> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/feature-templates/assign-tasks/my-tasks-screen-team-tasks-screen-completed-screen.md).
# My Tasks Screen, Team Tasks Screen, Completed Screen
The Assign Tasks Feature Template was designed for a property manager to offload tasks to a facility manager or outside vendors that help with upkeep of the properties. The Home Screen, Team Tasks Screen, and the Completed Screen each contain the same elements but the lists are filtered differently.
This configuration is controlled by the custom-made horizontal navigation.
## The Components
### **Tabs Group**
This group appears on each screen, however, the bold & underlined phrase is different depending on the screen the user is on.
⚡ Each phrase is linked to the related screen:
* My Tasks is linked to the ‘My Tasks’ Screen.
* Team Tasks is linked to ‘Team Tasks’ Screen.
* Completed is linked to ‘Completed’ Screen.
### List Group
Each list has a unique filter depending on the screen it appears on.
* My Tasks Screen
* Logged In User > Tasks > Completed is False and Name Contains Search Term - tasks.
* Team Tasks Screen
* All tasks > Completed is False and Name Contains Search Term - team.
* Completed Screen
* All tasks > Completed is True and Name Contains Search Term - completed.
⚡ **List Actions**
* Link Action to ‘Task Detail’
### Search Bar
The search bar is an input component and will filter the list items by the search term if the search term is used in the ‘Name’ field of the Task Property.
### Button
This button appears on the ‘Home’ Screen & the ‘Team Tasks’ Screen. It will be used to create a new task.
⚡ **Button Actions**
* Create Task
* Link Action to ‘Edit Task’ Screen
---
# 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://help.adalo.com/feature-templates/assign-tasks/my-tasks-screen-team-tasks-screen-completed-screen.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.