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

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

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

| What the actors 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 doesnot exist in db, system will create records for that user.|| User name, first/last name, email, department, user type|}  '''Postconditions:''' Manage department users page.  '''Scenario 2:''' View user's meetings/lectures.  '''Preconditions:''' Manage department 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 data fields retrievedUser name, addedfirst/last name, removedemail, by the systemdepartment, user type|-| Actor chooses to view user's meetings/lectures. || System returns calendar view with selected user's meetings/lectures.|||}  '''Postconditions:''' Manage department users page.  '''Scenario 3:''' Add user to department.  '''Preconditions:''' Manage department 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 selects user and chooses to add user to department. || System adds record to db.|| User name/id, department id

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

'''Scenario 24:''' Edit meetinguser. Actor can ban, change permissions, and remove a user from the department.

'''Preconditions:''' Includes anything that has been set up before starting the scenario. It must include what Manage department 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|-| Actor chooses to edit user. || System returns page populated with chosen user's information.|| User name, first name, last name, email, user type, department info, permissions

| Actor edits user info and chooses to save. || System persists data and updates records.||

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