> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/integrations/teamwork-projects.md).
# Teamwork Projects
Connect Luciq to Teamwork Projects so reported issues land in the right project, task list, and assignee with the details devs need.
Integrating Luciq with Teamwork Projects helps your team receive all the details they need about issues reported by testers and users from your mobile app using our SDK.
{% stepper %}
{% step %}
**Enter credentials**
Enter your *Token* and *Account URL*
{% endstep %}
{% step %}
**Choose project settings**
Choose your *Project*, *Task List*, and *Assignee*. You can also choose which details get forwarded as well.
{% endstep %}
{% step %}
**Test the integration**
At this point, we just need to test your integration so that we're sure everything is working smoothly.
{% endstep %}
{% step %}
**Finish and enable forwarding**
All done! Your integration is now set up and ready to go. From this final page, you can allow automatic forwarding (this can be reconfigured at any time).
{% endstep %}
{% step %}
**Example forwarded issue**
Issues forwarded to Teamwork Projects should look something like this.
{% endstep %}
{% endstepper %}
---
# 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.luciq.ai/product-guides-and-integrations/integrations/teamwork-projects.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)