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 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 during September, and 9 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

• Able to view line graph by the following views:
  • District
  • Region
  • Building
  • Team Member
• Need a clear/reset button

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
  • The top of the graph reads "Currently Viewing: District"
  • There should be axis labels 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
  
  • There will be a menu listing all regions within the district
  • There should be a search feature
  • When multiple regions are selected, each region should be represented by a different colored line on the graph
  • A district average total should appear on the graph
  • There should be a key below the graph
  • The top of the graph reads "Currently Viewing: Region"
  • There should be axis labels

• ---

  Region
  
  • If an account does not have regions set up, this option will not appear
  • Able to select one or multiple regions
  • Able to select up to 10 regions
  • 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
  
  • There will be a menu listing all buildings within the district.
  • There should be a search feature
  • 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
  • There should be a key below the graph
  • The top of the graph reads "Currently Viewing: Building"
  • There should be axis labels

• ---

  Building
  
  • If regions were previously selected, only those buildings within the selected regions will appear
  • Able to select one or multiple buildings
  • Able to select up to 10 buildings
  • 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.
  • Once buildings are selected, users are unable to filter by region.

• ---

  Team Member
  
  • There will be a menu listing all team members
  • There should be a search feature
  • Team Members will be organized in the list by Building
  • Team members should be listed alphabetically by last name
  • 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
  • There should be a key below the graph
  • The top of the graph reads "Currently Viewing: Team Member"
  • There should be axis labels

• ---

  Team Member
  
  • Able to select one or multiple team members
  • Able to select up to 10 team members at a time
  • If a building is selected, only the team members from that building should be visible
  • 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.
  • Team Members assigned to more than one building within the date range (either because they moved or because they are multi-account teachers/leads) will appear under each building they were assigned to within that date range
    • Selecting the team member's name under one building will auto-select that same team member's name for all other buildings
    • De-selecting the team member's name under one building will auto-de-select that same team member's name for all other buildings
  • 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
  • Once team members are selected, users are unable to filter by building or region.

• Filter by date

• If the date range is less than two months, we will display by week. If the date range is 2-23 months, we will display by month. If the date range is 24+ months, we will display by year.

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
  • There should be a message on this screen that reads "The following users have made use of the Rethink Ed Platform from INSERT START DATE to INSERT END DATE. Please take a moment to recognize these all-star users! (Once the Messaging Center is complete, consider adding a link to message the users a congratulations message)
  • 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
  • There should be a message on this screen that reads "The following users have not logged in from INSERT START DATE to INSERT END DATE. Please take a moment to contact these users and offer some support. (Once the Messaging Center is complete, consider adding a link to message the users a support message)
  • 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

• ---

  The default view will be same view as second layer report

• ---

  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 menu listing all regions within the district
  • There should be a search feature

• ---

  Region
  
  • If an account does not have regions set up, this option will not appear
  • Able to select one or multiple regions
  • Able to select up to 10 regions
  • Selecting a region will display the team members assigned to the selected regions
  • 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 should be a menu listing all buildings within the district
  • There should be a search feature

• ---

  Building
  
  • If regions were previously selected, only those buildings within the selected regions will appear
  • Able to select one or multiple buildings
  • Able to select up to 10 buildings
  • Selecting a building will display the team members assigned to the selected buildings
  • 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 option to filter to and from date
• Do not need to show display date (week, month, year)
• Do not need cumulative vs non-cumulative at 3rd layer

• ---

  The default date range will be past 90 days