'''Brief Description:''' This is a template to copy and paste into other pagesThe process of managing users in the system.

'''Scenario 1:''' Create new meetingSearch for user.

'''Preconditions:''' Includes anything that has been set up before starting the scenario. It must include what Manage users page the user is on before the scenario starts.

| What the actors doesActor types user name into search box and chooses to search. || What the system System searches db then LDAP for user and returns user information if found. If user does not exist in responsedb, system will create records for that user. || The data fields retrievedUser name, first/last name, addedemail, removeddepartment, by the systemuser type|}  '''Postconditions:''' Manage users page.  '''Scenario 2:''' View user's meetings/lectures.  '''Preconditions:''' Manage users page.  {| class="wikitable" border="1" cellpadding="5"|-! Actor !! System !! Data Used

| Actor types user name into search box and chooses to search. || System searches db then LDAP for user and returns user information if found. If user does not exist in db, system will create records for that user.|| User name, first/last name, email, department, user type|-| Actor chooses to view user's meetings/lectures. || System returns calendar view with selected user's meetings/lectures.||

'''Postconditions:''' The final results of the scenario running (ex. A record has been created, edited, etc.). It also includes the Manage users page that the user ends on.

'''Scenario 23:''' Edit meetingCreate user.

'''Preconditions:''' Includes anything that has been set up before starting the scenario. It must include what Manage users page the user is on before the scenario starts.

| What the actors doesActor chooses to create a user. || System returns page with editable fields related to user info.|| User name, first name, last name, email, user type, department info, permissions|-| Actor fills in fields and chooses to save.||System persists data and writes record to db. System sends email notification to provided email address for password setup. |||}  '''Postconditions:''' Manage users page.  '''Scenario 4:''' Edit user. Actor can ban, change permissions, and assign department heads.   '''Preconditions:''' Manage users page.  {| class="wikitable" border="1" cellpadding="5"|-! Actor !! System !! Data Used|-| Actor types user name into search box and chooses to search. || What the system System searches db then LDAP for user and returns user information if found. If user does not exist in responsedb, system will create records for that user. || The User name, first/last name, email, department, user type|-| Actor chooses to edit user. || System returns calendar view with page with editable fields filled in with data fields retrievedrelated to user.|| User name, first name, last name, email, user type, addeddepartment info, removedpermissions|-| Actor edits user info and chooses to save. || System persists data and updates records.|| |}  '''Postconditions:''' Manage users page.  '''Scenario 5:''' Delete user.  '''Preconditions:''' Manage users page.  {| class="wikitable" border="1" cellpadding="5"|-! Actor !! System !! Data Used|-| Actor types user name into search box and chooses to search. || System searches db then LDAP for user and returns user information if found. If user does not exist in db, by the systemwill create records for that user.|| User name, first/last name, email, department, user type|-| Actor chooses to delete user. || System returns prompt asking for confirmation.||

| Actor accepts (chooses to delete). || System deletes user record from db.||

'''Postconditions:''' The final results of the scenario running (ex. A record has been created, edited, etc.). It also includes the Manage users page that the user ends on.