> 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/exporting-projects-and-exercises.md).
# Exporting projects and exercises
The need to export a project or exercise is rare because **you can add collaborators to the project** to work together.
The **benefits** of exporting a project are:
* Offline backup
* The person you share the project with can't break your original project as they can if you add them as a collaborator
Exporting an exercise will share the project assets and that one exercise.
Exporting a project will share all the assets and all the exercises.
{% hint style="danger" %}
Two important points to note:
1. Exported projects are not backwards compatible with the legacy Editor
2. Teams tables with email addresses used in the exercise will be included in the project file
{% endhint %}
### How to
To export an exercise, navigate to the home page of your Editor. Click the three dots next to the exercise/project you want to export and click `Export exercise`:
---
# 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/exporting-projects-and-exercises.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.
