Last updated: June 9, 2026
How does bulk user management in Mitti differ from EdApp?
Feature | EdApp | Mitti |
|---|---|---|
CSV functionality | It exports and edits users with fields such as name, username, first name, last name, user groups, roles, password, external ID, and custom fields. | It exports user list to add and update users, including user details such as seat types, permission sets, groups, sites, companies, language, timezone and custom user fields. |
Password handling | Passwords for existing users can be updated via CSV. Leaving the password field blank keeps the learner's current password. | Passwords can only be set for new users being added to the organization. Bulk updating existing users’ passwords is not supported. |
Group and site membership | Admins can choose whether CSV updates to user groups and roles will add to current membership or replace them. | CSV data will overwrite existing group and site membership. |
Delimiters | Values in CSV are separated by a semicolon (;). | Values in CSV are separated by a comma (,). |
The critical gap between Mitti and EdApp is how existing assignments are updated via CSV. Mitti overwrites current group and site assignments, while EdApp lets admins choose whether User Group and Role updates should add to or replace current assignments.
Bulk manage users via CSV or Excel
CSV and Excel column headers
Email, first name, last name, and status are required for every row in your file. For all other columns, refer to each description for what happens when a value is left blank.
Column header | Description |
|---|---|
User ID | The unique ID of each user in your organization. |
Email or username | The email address or username used to sign in. Required for every row, as either type. Enter an email address for standard users. If username login is turned on for your organization, you can enter a username instead for users without an email address. Updating an existing user's email address or username isn't currently supported. |
First name | The first name of a user. |
Last name | The last name of a user. |
Status | The account status of a user. Use "active" for new users or "deactivated" for existing users. New users can only be set as active. |
Password | The password of a user, which must be at least 8 characters, containing an uppercase letter, a number, and a special character. You can only set passwords for new users. If username login is turned on for your organization, you must set passwords for new users with no email addresses. |
Language | The account language of a user. Refer to the "ISO-639 language codes" section in this article for language codes that are supported on the web app. |
Time zone | The account timezone of a user in IANA timezone or Country/Region format. For example, "America/New_York". |
Seat type | Available on Premium Plan and Enterprise Plan only. The seat type (opens in new tab) of a user. If left blank, the user will be assigned a guest seat by default. |
Permission set | The name of the permission set (opens in new tab) of a user. Users' permission sets can only be updated if you have "Platform management: Permissions" permission. If you leave the seat type column blank when you add new users, they’ll be given a guest seat and the "Guest" permission set. For username login users, the assigned permission set can't include "Platform management" or "Override permissions." |
Groups | The names of the groups (opens in new tab) of a user. If you leave the group column blank when you update existing users, their group memberships will be removed. |
Sites | The names of the sites or levels of a user. If you leave the site column blank when you update existing users, their site memberships will be removed. |
Companies | The names of the companies a user is associated with. |
Custom user fields | The custom user fields of a user. |
You can only bulk add or update up to 10,000 users per file at a time.
Need more help?
Was this page helpful?