Manage members and roles

Members are the people in your tenant: students, teachers, and administrators. What each member can do is governed by their role, and a role is a named set of permissions. This page covers adding members and tailoring roles.

Add members

You can add members one at a time or in bulk.

• Individually: in the Admin area, choose Members, then Add member, and enter their email, name, and role.
• In bulk: choose Import roster and upload a CSV with each person’s email, name, and role. Ember previews the file, flags duplicates and invalid rows, and only creates members once you confirm.

Ember sends each new member an invitation to your tenant. Email addresses are unique within your tenant, not across all of Ember, so a teacher who also keeps a personal Ember account keeps the two completely separate.

Roles and permissions

Every action in Ember is checked against a permission, never against a role’s name. A role is just a bundle of permissions. This means you can shape roles to match your institution instead of being limited to fixed labels.

Typical roles include:

• Student: practices, completes assignments, and shares progress with their teachers.
• Teacher: manages their own students, assigns and grades practice, and messages students.
• Administrator: configures the tenant, manages members and roles, sets sign-in and retention, and views usage and health.

Adjust what a group can do

To change what a set of people can do, edit the role rather than each person. For example, you might grant a lead teacher permission to manage the roster while limiting other teachers to assigning practice. Because checks are permission-based, the change applies everywhere that permission is required, in both the app and the back end, at once.

Remove a member

Open the member and choose Remove. This revokes their access to the tenant. What happens to their data afterward follows your retention policy; see data and retention.