> For the complete documentation index, see [llms.txt](https://docs.impler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.impler.io/platform/manage-project.md). # Manage Project Group your Imports into projects to make managing multiple imports easy Projects in Impler play a vital role in organizing imports effectively. You can invite your peers to the team and collaborate on Imports. ## How Projects Work? ### Open Projects Modal Click on your project name on the top left corner of the Impler platform below the Impler logo to open Projects Modal.

### Create Project You can create unlimited projects in Impler. To create a new project write the project name in text input and click on `Create`. Upon creating a project you will be switched to a new project automatically.

### Switch Project Once the project is created it will be shown on the projects menu. As `Owner` only you can delete the project.

{% hint style="info" %} Only the **Project Owner** can delete the project. {% endhint %} *** If you have any questions, suggestions, or comments. Feel free to reach out to us over [**Discord**](https://discord.impler.io). We’re constantly improving to deliver the best Data Importer for your product, and we value your input. --- # 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.impler.io/platform/manage-project.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.