> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/get-started/your-bravo-app-projects/add-an-editor-to-your-app.md).
# Add an editor to your app
{% hint style="info" %}
This feature is only available on **Team plan**
{% endhint %}
Add someone as an editor of the app that you are doing. The Teams plan provides you the flexibility to **up to 10 collaborators** and grant them **Editor permissions** allowing effective teamwork on your app development.
## How to add an Editor to your app?
Here are the steps to add an Editor to your app:
1. Open your app in Bravo.
2. Click on the three dots at the top right of the screen and select the "**Share**" option.
3. In the pop-up, enter the email of the person you want to invite as an editor.
4. By default, the next tab is set to "Preview only". Change it to "**Editor**".
5. To share this app with other Editors, move the collection to the app. Go to [User API collection section](https://projects.bravostudio.app/api-bridge) to change it or simply click on "**Make this app shareable**".
5. Finally, click on "**Invite".**
6. Et Voilà! :mailbox\_with\_mail: The invitee will receive an email notifying them of the app invitation. We recommend checking their spam folder to ensure they don't miss it.
8\. Once on Bravo Vision, they will see your app under "Apps".
## Manage invitees
The emails you have shared the app with will appear below in a list. If the invitee does not have an account with Bravo, the circle icon will appear grey. Once the editor has logged in, the circle icon will turn into a coloured icon.
### **How to remove Editor permissions?**
* Click the **`X`** next to the email.
* A confirmation modal will appear. If you confirm, the Editor will no longer see your app in their Bravo projects list.
---
# 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.bravostudio.app/get-started/your-bravo-app-projects/add-an-editor-to-your-app.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.
.jpg?alt=media&token=4852d33f-9e6b-450e-ab84-a6fc2a6ff505)
