# Collaboration

{% tabs %}
{% tab title="Experience level" %}
This core reference entry is suited for all experience levels<mark style="color:green;">**.**</mark>&#x20;

[Learn more about experience levels.](#user-content-fn-1)[^1]
{% endtab %}

{% tab title="In-depth articles (2)" %}
To learn about this topic more in-depth, we recommend reading the suggested articles below:

#### Collaborations and version control

* Article: [Managing collaborators](https://manual.bubble.io/help-guides/maintaining-an-application/collaboration)\
  You can invite Bubble builders into your app as collaborators[^2] and tweak their [access levels](#user-content-fn-3)[^3] to facilitate collaboration.
* Article series: [Version control](https://manual.bubble.io/help-guides/maintaining-an-application/version-control)\
  Version control lets you set up separate environments where different builders/teams can add features and fix bugs in isolation.
  {% endtab %}

{% tab title="Videos (1)" %}

* [How to add collaborators to your app](https://youtu.be/Pc-nLgsCOfY)
  {% endtab %}
  {% endtabs %}

## Users editing this app

This lists all the other users that have been added as collaborators on this app, and the permission levels they have.

### Admin

An admin can control the collaboration permissions of other collaborators.

### App

A given collaborator can have the ability to only "View" the app, or "View and edit" the app.

### Data

A given collaborator can have one of the following permission levels in relation to the database of an app:

<table><thead><tr><th width="196">Permission Level</th><th>Description</th></tr></thead><tbody><tr><td>No permission</td><td>Users cannot access any of the data.</td></tr><tr><td>View only</td><td>Users can view the data, e.g. in the App Data section, but cannot modify it.</td></tr><tr><td>View and run as</td><td>Users can view the data and "run as" a specific end-user but cannot modify it.</td></tr><tr><td>View and edit</td><td>Users have full permission to both view and modify entries in the database.</td></tr></tbody></table>

### Logs

A collaborator can either have no permission to see the app's logs, or the ability to "View and query" the logs

### Only dev. version

A collaborator can have the above permissions over only the development version(s) of the app, not the live version.

## Invite a user

#### Invite

Inviting a user as a collaborator will allow you to control the permissions that collaborator has in relation to the app, the app's data, and the app's logs, as described above.

#### Transfer

This will immediately transfer ownership of the app to another Bubble user. Be careful when using - if you are not an admin collaborator on the app, upon transfer, you will not be able to undo the transfer. If you would like to stay on as an Admin Collaborator, you must check the box on the Transfer modal.

#### Show the cursor of other editors when they modify the application

This feature will show you if any collaborators are currently actively in the editor. If you are on the same tab as a collaborator, you will see where their cursor currently is.

<details>

<summary>Video lessons</summary>

* [How to add collaborators to your app](https://youtu.be/Pc-nLgsCOfY)

</details>

[^1]: In the Bubble docs, experience levels are categorized into beginner, intermediate, and advanced.

    To assist with learning, especially for more complex topics, we'll recommend prerequisite reading where it could be beneficial.&#x20;

[^2]: Any Bubble user that you invite to view and/or edit your app and/or database is considered a *collaborator*.

[^3]: You can control what each individual collaborator has access to.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manual.bubble.io/core-resources/application-settings/collaboration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.