> For the complete documentation index, see [llms.txt](https://guide.form.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.form.gov.sg/user-guides/basic-guide/add-or-remove-collaborators.md).
# Add or Remove Collaborators
Upon creating a form, the creator will become the **owner** and the only collaborator on the form. We recommend adding more collaborators to prevent sudden loss of access to the form.
These are three different access levels (owner, editor and viewer).
Rights
Owner
Editor
Viewer
Delete form
✅
❌
❌
Edit form
✅
✅
❌
Edit settings
✅
✅
❌
View results
✅
✅
✅
Add/remove collaborators
✅
✅
❌
Share form
✅
✅
✅
* **Owner**: Full rights
* **Editor**: Same rights as form owner, but is unable to **delete** the form or make someone the owner.
* **Viewer**: Can only view **results** and **share** form.
Learn how to edit collaborators below:
{% tabs %}
{% tab title="Video Tutorial" %}
### Video Tutorial: Edit Collaborators
{% embed url="" %}
{% endtab %}
{% tab title="Text Tutorial" %}
### Text Tutorial: Edit Collaborators
**Step 1: Click on this button**
You can add/remove collaborators on the **top right hand corner** of each form by clicking on this button below.
**Step 2: Enter collaborator's email and choose** [**access**](#access-levels) **levels**
{% endtab %}
{% endtabs %}
---
# 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://guide.form.gov.sg/user-guides/basic-guide/add-or-remove-collaborators.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.
Text Tutorial: Edit Collaborators
**Step 1: Click on this button** 
You can add/remove collaborators on the **top right hand corner** of each form by clicking on this button below.
Video Tutorial: Edit Collaborators
{% embed url="