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

# Roles in the school

> Who is who in a school: the owner, team members, course editors, curators and students — how they differ and how they are assigned

A school has an owner, their team and students. Exode has no fixed list of roles like “administrator” or
“methodologist”. A staff member's role is made up of the set of permissions you granted them and of assignments:
which courses they are an editor of and in which groups they are a curator. The list of permissions and what each one opens is on the
[Access rights](https://faq.exode.biz/en/general/roles-permissions/access-rights.md) page.

## Who is who

| Role | Who it is | Where it is set up |
| - | - | - |
| **School owner** | The person who created the school. Has all permissions | Assigned when the school is created |
| **Team member** | A staff member with access to the control panel. Can do everything their permissions allow | **My school → Team** (in a corporate school — **Company → Administrators**) |
| **Course editor** | A staff member who has access to a course whose visibility is limited for the rest of the team | **Courses → course → Settings → Authors and editors** |
| **Curator** | A staff member with the “Course curator” permission assigned to a course group | **Courses → course → Groups → group → Settings** |
| **Student** | Any user of the school. Studies the courses they have access to | **People → All users** |

One person can combine roles. For example, a staff member is still a user of the school: you can give them access
to a course, and they will study as a student.

## School owner

The owner gets all school permissions when the school is created. In the **My school → Team** / **Company → Administrators** list, they are marked with a crown and
the tooltip “Organization owner”.

The owner is protected from accidental changes:

* They can't be removed from the team or deactivated. Only the owner can change the owner's permissions.
* In **People**, the owner can't be blocked or deleted. Other staff members can't change their
  name, phone number, email or Telegram.
* The owner can remove only three permissions from themselves: “School sales”, “School refunds” (both commercial schools only) and “Course curator”.
  The other permissions are marked as “Mandatory for the owner”.

Only the owner sees **My school → For developers → API keys** (in a corporate school — **Company → For developers → API keys**) and can copy another
staff member's password in their card.

> [!NOTE]
>
> You can't hand over the school to another person yourself — Exode support changes the owner. The new
> owner gets all permissions, and the previous one stays on the team.

## Team members

A team member is a user of the school who has been added to **My school → Team** / **Company → Administrators** and granted permissions.
Without permissions, a person has no access to the control panel, even if they are on the team.

How it works:

* You can add to the team only someone who already has an account in the school. If the staff member doesn't have one yet, first
  create them in **People → All users** or ask them to sign up on the school's website.
* Each member has a status: “Active” or “Not active”. An inactive member immediately loses access to the
  control panel but remains a user of the school.
* The number of active members is limited by the “Staff members” limit of the school's tariff. The owner counts toward this
  limit. See [Subscription and tariffs](https://faq.exode.biz/en/online-schools/getting-started/subscription-plans.md) for details (commercial schools only).
  In a corporate school, support raises the limit — the **Request a tariff upgrade** button.

Typical permission sets for different tasks:

| Staff member's task | Which permissions to grant |
| - | - |
| School administrator | All permissions in the list |
| Course author and methodologist | “Course management”, “Course browsing”, and “Task database management” if needed |
| Curator | “Course curator”, and “Course student management” if needed |
| Sales manager (commercial schools only) | “School sales”, “Product management” |
| Student relations manager | “School user management” / “Company user management”, “Course student management” |

## Course editors

By default, a course is visible to all staff members who have course permissions. If a course should be shown only to
part of the team, limit its visibility. In a corporate school, a new course is visible by default only to its
editors — see [Roles and permissions in a company](https://faq.exode.biz/en/corporate/roles.md).

**1. Open the visibility settings**

Go to **Courses → course → Settings → Authors and editors**. Find the **Visibility for the team** block.

**2. Turn off visibility for everyone**

Turn off the **Available to all editors according to their roles** toggle. The **Editors** list appears
below.

**3. Add editors**

Choose people in the **Employee search** field. The list includes only staff members with the “Course
management” permission. Click **Save**. While the list is empty, the setting won't be saved.

After that, only the owner and the editors in the list see and edit the course. Other staff members won't see
the course, even if they have the “Course management” or “Course browsing” permissions. This
setting does not affect students' access.

The staff member who created the course automatically becomes its editor. The list of editors can be changed by
staff members with the “School organization management” or “School team management” permission (in a corporate school —
“Company management” or “Company employees management”).

## Curators

A curator checks students' practice and answers their questions. To make a staff member a curator:

1. Grant them the “Course curator” permission in **My school → Team** / **Company → Administrators**.
2. Add them to the **Group curators** block in the settings of the course group you need.

When a student joins a group, the platform automatically assigns one of the group's curators to them.
Curators are assigned in turn: a new student goes to the curator who has gone the longest without getting students.

Which practices a curator sees depends on the course setting **The practices are reviewed by all school curators**
(**Courses → course → Settings → Authors and editors**):

| Setting | Which practices the curator sees |
| - | - |
| On (by default in a commercial school) | Practices of all students of the course |
| Off (by default in a corporate school) | Only practices of students from the groups where they are a curator, and practices already assigned to them for checking |

See [Practice checking](https://faq.exode.biz/en/general/lessons-modules/checking-practice.md) for more about checking.

## Students

Any user of the school counts as a student. They join the school themselves — by signing up or buying a course — or
a staff member adds them. Access to courses is granted separately: by buying a tariff (commercial schools only),
enrolling in a free course or manually. How company employees get into a course is described in
[Courses in a company](https://faq.exode.biz/en/corporate/courses.md). See [Adding users](https://faq.exode.biz/en/general/users/adding-users.md) and
[Course access](https://faq.exode.biz/en/general/users/adding-to-course.md) for details.

## Frequently asked questions

> **Can I create a role with a name, for example “Methodologist”?**
>
> No. Exode has no named roles — only a set of permissions for each staff member. To give several
> people the same access, check the same permissions for them in **My school → Team** / **Company → Administrators**.

> **How do I hand over the school to another person?**
>
> Contact Exode support. You can't change the owner yourself. After the change, the new owner gets
> all permissions, and the previous one stays a team member.

> **How do I give a staff member access to only one course?**
>
> Grant the staff member the “Course management” permission. Then, in every course they shouldn't see, turn off
> **Available to all editors according to their roles**. In the course they need, do the same and add the staff member
> to the **Editors** list. They will see courses that are visible to everyone in any case.

> **How is a curator different from a course editor?**
>
> An editor changes the course content: lessons, modules, practice. A curator checks the practices of students in their groups
> and communicates with them. Curators can't access the course content unless they have the “Course management” or
> “Course browsing” permission.

> **I added a curator to a group, but students don't have them. Why?**
>
> A curator is assigned to a student only at the moment the student joins the group. Students who were already in the group
> don't get the curator automatically. Assign them manually in the student's card: the **Learning** tab →
> course → the **Curator** field.

> **Can a staff member also study in the school?**
>
> Yes. A team member is a regular user of the school with extra permissions. Give them access to a course,
> and they will study as a student.

> **Why can't the owner remove some permissions from themselves?**
>
> The owner must keep control over the school and the team. So they can remove only “School
> sales”, “School refunds” (both commercial schools only) and “Course curator” from themselves. For example, without “School sales” they will stop receiving notifications
> about new payments, and without “Course curator” they won't be in the curator queue.

> **How many staff members can I add to the team?**
>
> As many as the “Staff members” limit of your tariff allows. Only active team members count,
> including the owner. Inactive members don't count toward the limit.

> **What happens if I remove a staff member from the team?**
>
> They immediately lose access to the control panel but remain a user of the school with all their courses.
> You can add them to the team again later with a new set of permissions.

***

*Updated: 2026-10-15 18:08 UTC*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.