> ## Documentation Index
> Fetch the complete documentation index at: https://docs.raykoi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Team & Roles

> Four roles, invite-based membership, and exactly what each role can do.

## Roles

Four roles, each strictly containing the permissions of the one below it:

| Role       | Can do                                                                                                                    |
| ---------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Owner**  | Everything — plus workspace deletion and billing/plan changes. Exactly one per workspace, non-transferable.               |
| **Admin**  | Everything below, plus manage members, [API keys](/dashboard/api-keys), and [webhooks](/essentials/integrations/webhook). |
| **Editor** | Everything below, plus create/edit forms and their settings.                                                              |
| **Viewer** | Read-only — view forms, submissions, and analytics. Can't change anything.                                                |

There's no custom/granular permission system beyond these four — a role either can or can't do a given action, checked server-side on every request, never just hidden in the UI. A viewer hitting an editor-or-above action gets this regardless of what the UI shows:

```json 403 theme={null}
{ "error": "Access denied: Insufficient permissions." }
```

## Inviting someone

<Steps>
  <Step title="Send the invite">
    From **Team** settings, enter their email and pick a role — `admin`, `editor`, or `viewer` (there's no `owner` invite — ownership belongs permanently to whoever created the workspace, see below).
  </Step>

  <Step title="They accept">
    The invite email links to an acceptance page. Until accepted, it shows as **Pending** in your Team settings — you can resend or revoke it from there.
  </Step>

  <Step title="Done">
    They now have that role's access to every form in the workspace — roles aren't currently scoped per-form.
  </Step>
</Steps>

<Frame>
  <img src="https://mintcdn.com/raykoi/OUWOqoE2CmHs9Dj9/images/dashboard/team-members.png?fit=max&auto=format&n=OUWOqoE2CmHs9Dj9&q=85&s=2b95fd1f45f0fe19d3566320948261d9" alt="Members & permissions page in the Raykoi dashboard" width="1564" height="580" data-path="images/dashboard/team-members.png" />
</Frame>

## Changing or removing someone's access

Change a member's role or remove them entirely from **Team** settings — requires `admin` or `owner`. Removing someone takes effect immediately; any session they have open stops working on their next request.

<Note>
  Ownership isn't transferable — it belongs to whoever created the workspace, permanently. Workspace deletion and billing/plan changes are the two things only that one account can do, even an `admin` can't.
</Note>