"Not really sure what the screenshot feature is suppose to do though." It's surveillance. In an ideal world, your job performance would be measured by some co

"Not really sure what the screenshot feature is suppose to do though." It's surveillance. In an ideal world, your job performance would be measured by some combination of the amount of stories completed, balanced with the difficulty of the stories and the quality of the code delivered too. Not only would you avoid having to look over your employees' screens, you wouldn't even need to track time at all. In the real world, these decisions are made by "managers" who think that things like hours, lines of code, surveillance, and using "approved software" are all good ways to measure the quality of the resulting product. They're the same ones pushing for return-to-office culture. They'll reward a dev who introduces bugs and then "burns the midnight oil" staying late to fix it, over the dev who writes clean code that doesn't crash in the first place.