---
title: Members and roles
description: Make a shared project, invite people in the right roles, and hand the project to a new owner.
updated: 2026-10-29
---

> All VIABLE docs, for people and their agents: https://developers.viablelab.org/llms.txt

# Members and roles

Decide who works in your project and what each person can do.

## Make a shared project

A project is your team's space: its agents, courses, studies, keys and logs belong to it. Open [Account → Projects](/dashboard/projects), choose **New project**, name it, and choose **Create project**. You become its owner.

Your personal project, shown with a lock, is private and can't be shared.

## Roles

| | Owner | Editor | Viewer |
| --- | --- | --- | --- |
| See keys (no secrets), logs, usage, agents and members | Yes | Yes | Yes |
| See learners' names, student IDs and personal codes | Yes | Yes | Codes only |
| Change agents, courses, question sets and studies | Yes | Yes | No |
| Invite and manage members; manage shared provider keys | Yes | If the owner allows | No |
| Create service keys, transfer, archive; pays for usage | Yes | No | No |

An editor can change every course in the project, not only their own. For a teacher who should run one course only, [share that course](/docs/teach/sharing) instead. A research assistant who only codes in **Research → Coding** can be a viewer.

The owner sets what editors may do under **Settings → Sharing permissions**.

> [!NOTE]
> Request logs keep what learners wrote to the AI, and every member, viewers included, can read and export them. Add only people who may read learners' messages.

## Invite people

In the project's **Members**, choose **Invite member**. Type a name or email address, pick **Viewer** or **Editor** as the **Role**, and choose **Invite member**.

Someone with an account gets access at once. Others show as **Pending** until they sign in with that email.

Each member's **…** menu can pause or remove them. Removing a member, or making an editor a viewer, revokes their personal API keys; if an app or course runs on one, make it a service key first.

## Transfer ownership

::: steps
1. **Start the offer.** Open **Settings → Transfer ownership**, or the member's **…** menu.
2. **Choose the new owner.** Pick an active member who has signed in as the **New owner**.
3. **Send it.** Read **After they accept** and choose **Send offer**.
:::

They have 7 days to accept, under **Review offer** on the project's **Overview**. Until then you stay the owner, keep paying, and can **Cancel offer**.

When they accept, you become an editor. Every API key moves to their account, so new requests use their credit and their personal provider keys. Past usage stays with you, and unused credit doesn't move.

> [!WARNING]
> A transfer can't be undone: the project comes back only if the new owner offers it back and you accept.

::: cards
- [Keys, credit and costs](/docs/project/keys-and-costs): give each app, course and chat page a key.
- [Sharing a course](/docs/teach/sharing): give a teacher or assistant one course, not the project.
:::