Work with a user roster file

A user roster file is an efficient tool for managing users in bulk.

You can perform the following tasks for multiple users in bulk by uploading a user roster file into Möbius:

Create new users
Enroll users into a class
Update Möbius's existing user information
Remove (or unenroll) users from a class
Delete users from the system

User roster file details:

Must be a text file (.txt extension) or a comma-separated value file (.csv extension)
Fields must be delimited by comma or tab
File must have only one student per line
Column header strings aren't case-sensitive

User roster files are imported into Möbius using the Class User Manager menu (on the Class Homepage) or the System User Manager menu (from the System Homepage menu), depending on the task you're completing.

Create users with a user roster file

Use this table to guide you through attribute requirements while creating your user roster text file to use for creating users:

Attribute name	Accepted attribute column header strings	Column heading and attribute value required	Required to be unique	Notes
Login or Username	login username	Yes	Yes
First Name	first name first	Yes	No
Middle Initial	initial mi	No	No
Last Name	last name last	Yes	No
Email Address	email	No	Yes
Student Identification	student id student	No	Yes
Password	password	No	No	A password will be generated by the system if a password isn't provided in the user roster file. The generated passwords are displayed on the roster upload success page only when uploading a user roster file from the System User Manager.
User Role	role	No	No	Can be defined as one of the following: Guest Student Proctor Instructor Instructor + create Administrator Role will be the system role if user roster file is to be imported using the System Homepage. Role will be the class role if user roster file is to be imported using the Class Homepage. User Role can't exceed the role level of the user who'll be importing the roster. Your organization might have custom roles that you can choose from.
Require Validation Upon First Login Attempt	require user validation validate require_user_validation	No	No	Determines requirement for user validation upon first log in attempt. If defined as true, the user will be asked to validate their profile upon their next log in attempt. If defined as false, the user won't need to validate their profile upon their next log in attempt. The default value is true.

Therefore, at minimum, your user roster file for creating a new user requires these attributes:

Log in
First name
Last name

If a password for the user isn't provided, Möbius will generate one.

Enroll users with a user roster file

Only the user login attribute should be included in your user roster file when enrolling existing users into a class.

Update a user roster file

User roster files can be used to update the information of users that already exist in the system.

You can:

Make changes locally on your computer to the user roster file that you've already uploaded and upload it again
Create a new user roster file that contains only the users you want to update

Notes on updating users with a user roster file:

The system will detect the differences in non-empty attribute fields in your uploaded roster file compared to the existing user attributes in the database and overwrite them using the updated attributes.
The only mandatory attribute column heading when submitting an updated user roster file is Login or Username (all other column headings are optional).
Attribute column headings not included in the import won't be updated in the system.
Empty attribute fields (indicated by two consecutive delimiters) are ignored by the system and no data will be overwritten.
One or more consecutive spaces between delimiters will be trimmed and act as two consecutive delimiters.
A <Null> string value is used to remove an existing attribute in the system.

Remove users from a class with a user roster file

Users can be removed—or unenrolled—from a class in bulk using a user roster file.

Only the user login attribute should be included in your user roster file when removing users from your class.

Delete users from the system with a user roster file

Administrators can delete users from the system in bulk using a user roster file.

Only the user login attribute should be included in your user roster file when deleting users from the system.