Skip to main content

Users vs. People in Lebra

Understand the difference between a Lebra login (user) and an employee record (person), where each is managed, and which one staff need.

Written by Lebra

Lebra keeps two kinds of records that are easy to mix up: users (logins) and people (employee records). Knowing the difference tells you where to go when you need to add someone, change their access, or handle a departure.


At a glance

User (login)

Person (employee record)

What it is

An account someone signs in with to work in Lebra, such as an administrator or evaluator

A staff member on your roster: their profile, framework role, pathway, and evaluations

Where to manage it

Settings → Team

The Organization page and each person's profile

How it's added

Invite users

Your roster import or data sync, or Add person (admins only)

Actions

Resend invite, change permission level, Deactivate / Activate

Edit person, Archive person / Restore person, Delete person

Who needs one

People who sign in to Lebra to manage or evaluate staff

Every staff member you evaluate or track

Many leaders have both: a person record (because they're on your roster) and a user (because they sign in to evaluate others).


Users (logins)

Admins invite users from Settings → Team → Invite users. Each user has one permission level:

  • Standard — limited access; can't change organization-wide settings

  • Group Admin — admin access scoped to their assigned groups

  • Admin — full access to organization settings

From the three-dot menu next to a user, admins can Resend invite to someone who hasn't accepted yet, change their permission level, or Deactivate them.

Note: A user needs a person record before they can be made a Group Admin. If the option is grayed out, add them to your roster first.


People (employee records)

Most people come into Lebra from your district's roster, through a CSV import or a scheduled data sync. Admins can also add one person at a time with Add person from the + menu.

To change a person record, open their profile and use the three-dot menu: Edit person, Archive person, or Delete person. These options are available to admins.


Do teachers need a user?

Usually not. Teachers and other staff being evaluated use the Staff Portal, and they don't need an invitation. Staff Portal access is based on the person record: the staff member signs in with the email address on their record. To use the Staff Portal, the person must:

  • have a person record with their email address,

  • have a framework role assigned, and

  • not be archived.

Only invite a teacher as a user if they also need to sign in to Lebra to evaluate or manage other staff.


When someone leaves

  • A staff member leaves: archive their person record. Their evaluation history is kept.

  • A leader with a login leaves: deactivate their user in Settings → Team and archive their person record. Deactivating alone doesn't archive the record, and archiving alone doesn't turn off the login.

Note: If your roster comes from a scheduled feed, departures are usually handled by the sync. See Sync Status and Scheduled Roster Feeds.

Did this answer your question?