> For the complete documentation index, see [llms.txt](https://docs.frase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frase.io/troubleshooting-and-faqs/invite-your-team.md).

# Invite Your Team and Set Roles

Add teammates to Frase, give each one the right level of access, and move content from draft to published together.

{% hint style="warning" %}
Only account Owners and Admins can invite teammates and change their permissions.
{% endhint %}

## Invite a teammate

{% stepper %}
{% step %}

### Open Settings

On the bottom of the left sidebar, go to **Settings → Team.**
{% endstep %}

{% step %}

### Click Invite Member

{% endstep %}

{% step %}

### Enter their email and choose a role

Pick **Admin**, **Editor**, or **Viewer**, depending on how much access they need. You can change a teammate's role later under **Settings → Team**.

<div align="left"><figure><img src="https://3311323497-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fm4GQuvaZPL4j5tqamFyy%2Fuploads%2FCtK8YqrV9dDKHigv23bo%2Fimage.png?alt=media&#x26;token=249cfe42-a498-4349-97bb-d96879acea1a" alt="Role options: Admin, Editor, Viewer"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

## Work on content together

* **Track progress.** Content moves through **Draft → Review → Published**. Filter your articles by stage or by who they're assigned to, so nothing sits waiting for feedback.
* **Assign ownership.** Assign a document, or a whole [Project](https://docs.frase.io/troubleshooting-and-faqs/using-projects), to a teammate so it's clear who's on it.
* **Review in the editor.** Leave in-line comments, check version history, and send share links to pull in reviewers from inside or outside your team.
* **Stay on brand.** Set your tone, style, Reference Documents, and Terminology once in [Brand Hub](https://docs.frase.io/feature-reference/brand-hub). Everyone's content follows them.


---

# 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.frase.io/troubleshooting-and-faqs/invite-your-team.md?ask=<question>&goal=<user_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.