There are a few things that could be going on here. Let’s start with the simplest and then move to the most complex.
Check the Date-Range Filter
Near the top of the ScoreBoard, you’ll find a date range. It defaults to just the last 30 days and it’s “non-inclusive,” meaning the start and end dates chosen are NOT included in the resulting dataset displayed in the chart/table.
So, let’s make that date range something really big, like more than a year or something. Click Search and see if the ScoreBoard comes to life with data–beautiful data.
Check the Other Filters
There are several other filters you’ll see below the date range. There is: Role, Reports to, Team, Visualize, and View By.
Start with “Visualize” and then “View By.” See if you’re just seeing the wrong chart. Otherwise, let’s get move to the next solution.
Might Be a Permissions Thing
There are essentially two kinds of permissions in SecureDB: Role Permissions and Reports To permissions.
Role Permissions are based on visibility–can a user use/see certain things. These permissions are set in the Role Manager (Accountability >> Build/Manager Roles). If you CAN’T see the ScoreBoard at all, then the user’s role has that permission. If not, just head over to the user’s role and toggle the “View ScoreBoard” permission at the bottom.
NOTE: If you enable “View ScoreBoard” for this role, ALL users in this role will also inherit this view permission.
If you CAN see the ScoreBoard, but you’re not seeing all the information you think you’re supposed to see, then it might be the other kind of permission in SecureDB–Reports To.
Head over to the person’s profile, who do they report to? Also, which employee’s information is missing? Does that employee “report to” the user with the missing data? If not, just go to that missing user’s profile and change their “Reports To” value, or add them in “Reports to Secondarily.”
Visibility as a permission was critical when we were building SecureDB.
