Page Comparison

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
  
  • This view shows number of unique logins for all users at the district and child accounts the user has access to within the date range
    
    • 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
  • This view shows number of unique logins for all users at the selected region(s) and child accounts the user has access to within the date range
  • 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
  • This view shows the number of unique logins for the selected building(s)
  • 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
  
  • Number of unique logins for users assigned to the selected role(s)
  • 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.
  • If all roles selected are assigned to the same building, we will show the total number of logins for the building. If roles selected belong to more than 1 building but the same region, we will show the total number of logins for the region. If selected roles belong to multiple regions, we will show the total number of logins for the entire district.

• Team Member
  • Number of unique logins out of the users selected.
    
    • This will be displayed as one line.
  • If all team members are assigned to the same building, we will show the total number of logins for the building. If team members selected belong to more than 1 building but the same region, we will show the total number of logins for the region. If selected team members belong to multiple regions, we will show the total number of logins for the entire district.
  • 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

Business Rules

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

• 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.
• 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

Business Rules

• Displays all team members at the parent and child accounts the user has access to who have logged in at least 1 time within the date range

Business Rules

• For each Region selected, we will display a separate tab
• Under each tab, we will display all team members at the region and child accounts the user has access to who have logged in at least 1 time within the date range
• Multi-Account Team Members should appear under each region they are assigned to within the date range
• Team Members who moved between regions during our date range

• should show under each region they were assigned to

Business Rules

• For each Building selected, we will display a separate tab
• Under each tab, we will display all team members at the building who have logged in at least 1 time within the date range
• Multi-Account Team Members should appear under each building they are assigned to within the date range
• Team Members who moved between buildings during our date range should show under each building they were assigned to

Business Rules

• For each Role selected, we will display a separate tab
• Under each tab, we will display all team members with the selected role at all at the buildings the user has access to who have logged in at least 1 time within the date range
• Team Members who changed roles during our date range should show under each role they were assigned to

Business Rules

• We will display all team members out of those selected who have logged in at least 1 time within the date range selected.

Business Rules

• Team Members should be organized by region/building

• 
  
  • 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

Business Rules

• Displays all team members at the parent and child accounts the user has access to who have NOT logged in at least 1 time within the date range

Business Rules

• For each Region selected, we will display a separate tab
• Under each tab, we will display all team members at the region and child accounts the user has access to who have NOT logged in at least 1 time within the date range
• Multi-Account Team Members should appear under each region they are assigned to

• within the date range
• Team Members who moved between regions during our date range should show under each region they were assigned to

Business Rules

• For each Building selected, we will display a separate tab
• Under each tab, we will display all team members at the building who have NOT logged in at least 1 time within the date range
• Multi-Account Team Members should appear under each building they are assigned to

• within the date range
• Team Members who moved between buildings during our date range should show under each building they were assigned to

Business Rules

• For each Role selected, we will display a separate tab
• Under each tab, we will display all team members with the selected role at all at the buildings the user has access to who have NOT logged in at least 1 time within the date range
• Team Members who changed roles during our date range should show under each role they were assigned to

Business Rules

• We will display all team members out of those selected who have NOT logged in at least 1 time within the date range selected.