Unique Logins

Design

• Line graph showing # of unique team members logging in across the district
• Option to view cumulative vs non-cumulative data
• Date range will be last 90 days

Business Rules

• The line graph should show number of unique team members logging into Rethink Ed (site or mobile app).
• The information displayed should be based on filter selections.
  • If District is selected, we will see one line on the graph. This line will display the total number of unique logins for users assigned to at least 1 product across the entire district.
  • If Regions are selected, we will see one line on the graph. This line will display the total number of unique logins for users assigned to at least 1 product for the regions selected. For example, if 10 users in Region A and 10 users in Region B logged in in September, we should show 20 logins for September.
  • If Buildings are selected, we will see one line on the graph. This line will display the total number of unique logins for users assigned to at least 1 product for the buildings selected. For example, if 10 users in Building A and 10 users in Building B logged in in September, we would show 20 logins for September.
  • If Roles is selected, we will see one line on the graph. This line will display the total number of unique logins for users assigned to at least 1 product for the roles selected. For example, if 10 users assigned Lead Teacher and 10 users assigned to Para logged in in September, we would show 20 logins for September.
  • If Team Members are selected, we will see one line on the graph. This line will display the total number of unique logins for the members selected (any team member with at least 1 product assigned will show in the list). For example, is Team Member A logged in 5 times an Team Member B logged in 1 time in September, we would show 2 logins for September.
  • Student filter will not be an option.
  • If Students were previously selected (i.e. selected on another screen, such as Student Progress), logins box will not show on the overview.
  • Multi-account users should only be counted once, regardless of filter selections.
• There should be a toggle for cumulative vs non-cumulative
• Cumulative view will show total number of unique logins across entire time period. For example, if 10 people log in during August, 20 different people during September, and 9 different people during October, the data points would read:
  • August: 10
  • September: 30
  • October: 39
• Non-Cumulative view will show the number of unique logins for each month represented on the graph. For example, if 10 people log in during August, 20 during September, and 9 during October, the data points would read:
  • August: 10
  • September: 20
  • October: 9

Design

Options are:

• Graph
• List

Business Rules

• Default will be Graph

Design

• Able to view line graph by the following views:
  • District
  • Region
  • Building
  • Team Member

Business Rules

• The default setting is District
• If cumulative was selected at top layer, this carries over to second layer. This can be changed on the second layer if they so choose.

• ---

  District
  • One line appears on the graph

• ---

  District
  
  • This view shows total logins for the entire district
  • This view includes logins for Roles 6 & 7
  • Multi-Account team members will only be counted once. Meaning, if Team Member B is a multi-account teacher belonging to Region 1, 2, and 3, that team member's login activity will only be counted once for the entire district.

• ---

  Region
  • When multiple regions are selected, each region should be represented by a different colored line on the graph
  • A district total should appear on the graph

• ---

  Region
  • If Team Member A belongs to Region 1 in the month of September then moves to Region 2 in the month of October, Team Member A's logins will be counted for Region 1 for September and Region 2 for October
  • Multi-Account team members will be counted for each region they belong to. Meaning, if Team Member B is a multi-account teacher belonging to Region 1, 2, and 3, that team member's login activity will be show for Regions 1, 2, and 3.

• ---

  Building
  • When multiple buildings are selected, each building should be represented by a different colored line on the graph
  • A district/region total line should appear on the graph

• ---

  Building
  • If Team Member A belongs to Building 1 in the month of September then moves to Building 2 in the month of October, Team Member A's logins will be counted for Building 1 for September and Building 2 for October
  • Multi-Account team members will be counted for each building they belong to. Meaning, if Team Member B is a multi-account teacher belonging to Buildings 1, 2, and 3, that team member's login activity will be show for Buildings 1, 2, and 3.

• ---

  Role
  
  • When multiple roles are selected, each role should be represented by a different colored line on the graph
  • A district/region total line should appear on the graph

• ---

  Role
  
  • If Team Member A is assigned to Role 1 in the month of September then is reassigned to Role 2 in the month of October, Team Member A's logins will be counted for Role 1 for September and Role 2 for October.

• ---

  Team Member
  • When multiple team members are selected, each team member should be represented by a different colored line on the graph
  • A district total line should appear on the graph

• ---

  Team Member
  • Team Members assigned to more than one building (either because they moved or because they are multi-account teachers/leads) will only display one line on the graph per team member. Meaning Team Member A will only ever show one line on the graph, regardless of how many buildings they were assigned to within the selected date range

Design

• The following views exist
  
  • Team Members who have logged in
  • Team Members who have not logged in

Business Rules

• The default view will reflect any previously applied filters. If no filters were applied, we will show results for whole district.

• ---

  Logged In View
  
  • Displays the following fields:
    • Team Member Name
    • Number of logins
    • Date of last login
  • Team Members should be organized by region/building

• ---

  Logged In View
  
  • This view will display all team members who have logged in to the site or mobile app within the specified date range
  • Users should be ranked in order of logins, with those users with the most logins at the top of the list. If two users have the same number of logins, the user with the most recent login date should appear first. If this date is also the same, users in question will be ranked alphabetically by last name.
  • Multi-Account Team Members should appear under each building they are assigned to
  • If a team member moves buildings, they should appear under all buildings assigned to within the selected date range
  • There will be a sort feature that allows users to sort the table by name, # of logins, or date of last login in ascending or descending order.

• ---

  Not Logged In View
  
  • Displays the following fields:
    • Team Member Name
    • Date of last login
  • Team Members should be organized by region/building

• ---

  Not Logged In View
  
  • This view displays all team members who did not log in to either the site or mobile app within the specified date range
  • Users should be listed in order of last login date, with the user who has logged in most recently showing at the top. If two users have the same login date, the users in question will be ranked alphabetically by last name.
  • Only team members who have products assigned will appear in the list. If a team member has been added to the platform, but not assigned any products, this individual will not appear in the list.
  • Multi-Account Team Members should appear under each building they are assigned to
  • If a team member moves buildings, they should appear under all buildings assigned to within the selected date range

• ---

  Need filters for:
  
  • District
  • Region
  • Building
  • Role
  • Team Member

• ---

  District View
  
  • This is the default & displays all team members across the district

• ---

  District View
  
  • This is the default & displays all team members across the district

• ---

  Region
  • There will be a separate tab for every region selected
  • Each region tab will display team members who have/have not logged in for each region

• ---

  Region
  
  • Multi-Account Team Members should appear under each region they are assigned to
  • If a team member moves regions, they should appear under all regions assigned to within the selected date range

• ---

  Building
  
  • There will be a separate tab for every building selected
  • Each building tab will display team members who have/have not logged in for each building

• ---

  Building
  • Multi-Account Team Members should appear under each building they are assigned to
  • If a team member moves buildings, they should appear under all buildings assigned to within the selected date range

• ---

  Role
  • There will be a separate tab for every role selected
  • Each role tab will display team members assigned to the selected roles who have/have not logged in

• ---

  Role
  
  • If a user changes roles, they should appear under all roles assigned to within the selected date range

• Team Member
  
  • All selected team members will appear on one screen