Roles

Every user belongs to an Instance and carries one or more roles within that instance. A role determines what the user can do - which features they see, what they can create, and whether they can manage other users.

The four role levels

Internally, every role in an Instance maps to one of four permission levels, ordered from least to most privileged:

API value	Customer-facing label	Typical use
user	Student	An end user — creates content, but does not manage others.
lead	Teacher	A power user — can manage groups of users' assigned to them, manage assignments and review student submissions.
admin	Admin	An instance administrator - manages users, roles, billing-bound settings, and Instance-wide configuration.
owner	Owner	The instance's top-level owner. Not assignable through the API.

The labels above reflect the EDU vocabulary the WeVideo product uses by default (a school's teacher is, internally, a lead). For non-EDU deployments the same levels still apply — read lead as "team lead" or "manager", and user as "individual contributor".

Naming

The API always uses the lowercase, internal names (user, lead, admin). The product UI shows the customer-facing labels (Student, Teacher, Admin). Both refer to the same thing.

Filtering Users by role level

GET /public/users accepts a role query parameter that filters by level:

curl 'https://www.wevideo.com/api/5/public/users?role=lead' \
  -H 'Authorization: WEVSIMPLE your-api-secret-here'

Accepted values: user, lead, admin. owner is not exposed through this filter.

The filter is by level, not by named role — ?role=lead will return every user assigned to any lead-level role in the Instance.

See also

• Core entities — how users, instances, and roles relate
• List users — GET /public/users reference, including the role filter
• Create user — POST /public/users reference