> For the complete documentation index, see [llms.txt](https://help.seoutils.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.seoutils.app/guide/team/inviting-your-team.md).

# Inviting Your Team

Invite a person, choose their role and workspaces, decide whether they can use your machine and paid accounts, and keep track of seats.

You invite each person by email from **Settings → Team**. The invitation carries the role, the workspaces and the machine access you choose, so the person has everything the moment they accept. Make sure your plan includes team logins first; see [Before You Start](https://help.seoutils.app/guide/team.md#before-you-start).

## Roles

A role is a set of permissions. Inside the workspaces they can open, a team member sees what you see; the role decides what they can change.

| Role        | What the person can do                                                                                                                                                                                   |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Viewer**  | View reports in their workspaces. A Viewer never uses your machine or accounts.                                                                                                                          |
| **Analyst** | Everything a Viewer does, plus run and re-run reports, export data, cancel their own runs, and add tags and annotations.                                                                                 |
| **Manager** | Everything an Analyst does, plus create and edit reports, import files, move reports between their workspaces, publish reports to clients, delete reports, and cancel anyone's runs in their workspaces. |
| **Custom**  | You pick each permission yourself.                                                                                                                                                                       |

<details>

<summary>Custom permissions</summary>

Choose **Custom** to tick exactly the permissions you want.

| Permission                  | What it allows                                            |
| --------------------------- | --------------------------------------------------------- |
| **Run reports**             | Run and re-run existing reports with their saved settings |
| **Create and edit reports** | Create reports, change their settings and keyword lists   |
| **Delete reports**          | Delete reports and their data                             |
| **Import files**            | Upload keyword files and import data into a workspace     |
| **Move reports**            | Move reports between the workspaces they can open         |
| **Publish to clients**      | Share reports in the client portal                        |
| **Export data**             | Download CSV and PDF exports                              |
| **Cancel their own runs**   | Stop runs they started                                    |
| **Cancel any run**          | Stop runs anyone started in their workspaces              |
| **Add tags**                | Create tags and attach them to rows                       |
| **Add annotations**         | Write annotations and edit their own                      |

Machine access is a separate box; see the next section.

</details>

## Machine and Accounts Access

**Can use the owner's machine and accounts** is the one switch for everything that spends your resources: runs that fetch data or spend credits use this computer, its proxies and your paid accounts (DataForSEO, AI providers). You see each person's spend in the [Spend tab](https://help.seoutils.app/guide/team/activity-and-spend.md#spend).

* It is **ticked by default for Analyst and Manager**, and you can untick it.
* A **Viewer never has it**. The box is greyed out for a Viewer.
* Without it, an Analyst or Manager shows a **No machine access** badge in People. Their run buttons and lookups are greyed out with **Ask {your name} for run access**.

{% hint style="info" %}
Lookup tools such as Keyword Explorer are visible to every team member, but using them, and reading their saved results, needs machine access.
{% endhint %}

## Workspace Access

Choose which workspaces the person can open:

* **All workspaces, including future ones.** A workspace you create later is open to them too.
* **A list of workspaces.** Tick the ones they need. **Select all** and **Clear all** help with long lists.

If you pick none, the person can sign in but sees nothing until you add a workspace. They get a waiting page that opens by itself as soon as you do.

## Invite Someone

Open **Settings → Team** and go to the **Invite** tab.

{% stepper %}
{% step %}

#### Enter the email address

Type the address the invitation goes to. The person must use a cloud account with this address to accept.

<figure><img src="https://1176579443-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2DwV6sJBiKjUHMDggb4d%2Fuploads%2Fgit-blob-737e33b6040fc4e24ba4a14d2a84a885cd15dafd%2Fteam-invite-form.png?alt=media" alt="The Invite tab with an email address, the four roles, the machine access box and the workspace picker"><figcaption><p>The Invite tab: 1 email, 2 role, 3 machine access, 4 workspaces</p></figcaption></figure>
{% endstep %}

{% step %}

#### Choose a role

Pick **Viewer**, **Analyst**, **Manager** or **Custom**. The line under the roles lists what the chosen role can do.
{% endstep %}

{% step %}

#### Set machine access

Leave **Can use the owner's machine and accounts** ticked, or untick it. See [Machine and Accounts Access](#machine-and-accounts-access).
{% endstep %}

{% step %}

#### Choose workspaces

Switch on **All workspaces, including future ones**, or tick the workspaces they can open.
{% endstep %}

{% step %}

#### Send the invitation

Click **"Send invite"**. SEO Utils emails the person a link and shows the invitation in **People** with the status **Invited**.
{% endstep %}
{% endstepper %}

The invitation is valid for **7 days** and holds a seat until it is accepted, revoked or expired. To cancel it, open the row's **...** menu, choose **Revoke invitation** and confirm with **Yes**. The person can then no longer use the link.

What happens next is described in [For Employees](https://help.seoutils.app/guide/team/for-employees.md).

## Seats

The top right of the Team page shows two lines:

* **{n} of {total} seats.** Each team member and each pending invitation uses one seat. A suspended or removed person does not.
* **{n} of {total} browsers signed in, {n} of them yours.** The same total also limits how many browsers can be signed in at the same time, your own included.

Both lines use the same total. Every plan includes 1 seat, so buy extra seats for your team on the **Remote Access** page of your cloud account; see [Adding or Removing Seats](https://help.seoutils.app/guide/remote-access.md#adding-or-removing-seats).

When every seat is in use, the Invite tab says **All seats are in use** and the form is switched off. Buy more seats, revoke an invitation or remove someone to invite another person.

{% hint style="warning" %}
If every browser seat is taken when a team member signs in, they see a page asking them to ask you to free one, and you get an email naming them. Sign out a browser on the Remote Access card to free a seat.
{% endhint %}

## Best Practices

* Start people as **Viewer** or **Analyst**, and move them to **Manager** when they need to create or publish reports.
* Untick machine access for an Analyst or Manager who should not spend your credits. Their runs that fetch data then stay switched off.
* Give each client-facing person only the workspaces they work on.
