> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.faaaster.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What roles can you assign to a collaborator on Faaaster?

Three roles are offered when you invite someone: **Admin**, **Member** and **Viewer**. The **Owner** role can't be assigned — it belongs to the holder of the account or the site.

> ⚠️ **Don't rely on the old documentation on this topic**: it mentions "Developer" and "Editor" roles that no longer exist.

## Roles you can assign when inviting

| Role | |
| --- | --- |
| **Admin** | Can manage the team: invite collaborators, change their role and revoke them. |
| **Member** | Collaborative access to the relevant scope. |
| **Viewer** | View-only access. |

## Who can invite?

Only the **Owner** and **Admins** can invite, change the role (**Change role**, in the row menu) or revoke collaborators. This control applies at two levels:

- at the **organization** level, to give access to the whole account;
- at the **site** level, to open up just one project.

An admin of a site can therefore manage that site's team, without having any rights over the rest of the account.

## Other roles you'll come across

Two more labels appear in the interface without being assignable:

- **Owner** — the holder of the account or the site. They're the one who holds the subscription.
- **Invited** — this isn't a role but a **state**: it indicates an invitation that has been sent and not yet accepted.

## Alerts by role

The **Settings** page of the **Account** section, **Alerts** card, lets you choose which roles receive alerts for the organization's sites: **Owner**, **Admin**, **Member**. For a single site: **Tools** tab, **Notifications** row.

## What each role can do

These rights are enforced by the server, not just by the interface: a grayed-out button is grayed out because the action would be refused.

- **The Viewer** views the site and performs harmless actions: **Clear cache**, **Restart PHP / Nginx** or **Restart server**. They have no access to any credentials (database, SSH / SFTP, WordPress login) and can't change anything else.
- **The Member** makes all changes to the site: plugins and themes, server configuration, security, domains and DNS, backups and restores, import and export, environments. They have access to the site's credentials.
- **The Admin** and the **Owner** also manage the project: the team, archiving, cloning and transferring the site, canceling its subscription, buying a domain name.

| | Viewer | Member | Admin | Owner |
| --- | --- | --- | --- | --- |
| View the site and its data | ✅ | ✅ | ✅ | ✅ |
| Clear the cache, restart PHP / Nginx or the server | ✅ | ✅ | ✅ | ✅ |
| Access credentials (database, SSH / SFTP, WordPress) | ❌ | ✅ | ✅ | ✅ |
| Change the site, its domains and its DNS | ❌ | ✅ | ✅ | ✅ |
| Invite collaborators, change their role and revoke them | ❌ | ❌ | ✅ | ✅ |
| Archive, clone or transfer the site, cancel its subscription, buy a domain | ❌ | ❌ | ✅ | ✅ |
| Hold the subscription | ❌ | ❌ | ❌ | ✅ |

> **An Admin invited to a single site** manages that site's team, but archiving, cloning, transferring the site, its subscription and purchases remain with the organization's owner and admins.

The AI assistant follows the same rights: a Viewer can ask it to clear the cache, a Member to change the site.

One last label, **Creator**, appears on some screens: it refers to the person who created the site and gives them the **Owner**'s rights.

👉 [How do I invite a collaborator?](https://help.faaaster.io/en-us/article/invite-a-collaborator-1l73v2k/) · [How do I transfer a site to my client?](https://help.faaaster.io/en-us/article/transfer-a-site-7836dh/)