> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-user-guides/snap2snomed-user-guide/how-to-.../3-mapping-with-snap2snomed/3.5-tasks.md).
# Tasks
Tasks are the way that Snap2SNOMED manages the workflow. All work being done within a map should be done through the tasking process.
Each task has a task type, an assigned user and assigned rows. Permissions for creating tasks is determined by the user's role (see table X)\\
## Task types
There are two different task types
* Author tasks
* Review tasks
### Author tasks
Author tasks allow an assigned user to edit a source code mapping by adding or updating target codes, or adding "No Map" flags.
### Review tasks
Review tasks allow an assigned users to review mapped source codes by giving them statuses of ACCEPTED and REJECTED.
## Task assigned user
This is the user who is able to complete the task. Users who are not the assigned user are not able to access the task.
## Task assigned rows
These are the rows that are assigned to a task. They allow users to interact with these rows within the task.
Provide Feedback
---
# 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://docs.snomed.org/snomed-ct-user-guides/snap2snomed-user-guide/how-to-.../3-mapping-with-snap2snomed/3.5-tasks.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.