> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/project-activities/collaboration.md).
# Collaboration
## Work on an exercise together
To add a collaborator means you're **adding someone from your organisation to your project so you can work on the same exercises**. Collaborators must belong to your organisation (as defined by your Conducttr licence).
{% hint style="info" %}
At the moment you can't work on the exercise simultaneously. If you try to access a project that is being worked on, you'll be told it's locked.
{% endhint %}
## How to add a collaborator
Because exercises access assets owned by the parent project (such as media and personas), **you can only add collaborators to a project**, not to a specific exercise. This means collaborators on a project will have access to all exercises in that project.
{% stepper %}
{% step %}
Find the exercise, clicked the ... and then select Add collaborators
{% hint style="warning" %}
You cannot share only an exercise, you must share a project.
{% endhint %}
{% endstep %}
{% step %}
Add the email address of your collaborator and click "send invite"
{% 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/project-activities/collaboration.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.
{% stepper %}
{% step %}
Find the exercise, clicked the ... and then select Add collaborators
{% hint style="warning" %}
You cannot share only an exercise, you must share a project.
{% endhint %}
