Summary
To customize employee monitoring by team, define a monitoring profile for each group based on what that team actually needs to measure or protect, then turn on only the features that serve that purpose. A support team may need attendance, idle time and screenshots for quality review; engineering may need little more than attendance and app usage; field teams may need GPS during shifts; and finance may need file access and USB controls. Customizable employee monitoring is more proportionate, easier to defend under privacy laws such as GDPR, and better for trust than one policy applied to everyone. Pair each profile with role-based views so managers see only their own reports, disclose the profile to the employees it covers, and review every profile at least quarterly.
E-Monitor lets you set web rules, screenshot settings and opt-in features per team or role, and its role-based reporting dashboards show each team lead only their direct reports. Start free →
Why One-Size-Fits-All Monitoring Fails
Customizable employee monitoring means configuring what is collected, how often, and who can see it, separately for each team or role, instead of applying the same settings to the whole company. The default alternative, turning everything on for everyone, causes three problems.
- It is disproportionate. Screenshots every few minutes may be justified for a payments team handling card data, but are hard to justify for a design team. Collecting data you have no use for is a liability, not an asset.
- It conflicts with data minimization. Under GDPR Article 5(1)(c), personal data must be adequate, relevant and limited to what is necessary for the purpose. A single maximal policy is difficult to defend against that standard. See our guide to GDPR employee monitoring compliance.
- It damages trust. Employees notice when monitoring has nothing to do with their work. A developer who sees keystroke counts on their profile reasonably asks what problem that solves.
Our overview of the types of employee monitoring explains each capability. This guide is about choosing among them, team by team.
How to Decide What Each Team Needs
Run every feature through a short test before switching it on for a group. If you cannot answer all four questions, leave it off.
- Purpose test. What specific problem does this data solve for this team? "Verify billable hours for client work" is a purpose. "Visibility" is not.
- Risk level. What does the team handle? Access to customer financial data, health records or source code justifies tighter controls than access to a public marketing calendar.
- Legal requirements. Do regulations, client contracts or audit standards require specific records, such as session evidence in a regulated contact center? Do local laws require notice or consultation before monitoring?
- Less intrusive alternative. Could a lighter feature achieve the same result? Activity summaries often answer the question that screenshots were meant to answer.
When a feature fails this test for every team, that is a sign it should not be used at all. Our guide on when not to monitor employees covers those cases.
Example Monitoring Profiles by Team
These monitoring profiles are starting points, not rules. Adjust them to your purpose test, risk level and jurisdiction.
| Team | Usually on | Usually off or limited | Why |
|---|---|---|---|
| Engineering | Attendance, app and website usage, productivity categories tuned for dev tools | Screenshots, keystroke intensity | Output is measured in code and tickets; screenshots add little and expose sensitive code |
| Sales | Attendance, app usage, CRM and social platforms allowed as productive | Screenshots, keystroke intensity | Social and LinkedIn use is part of the job; outcome metrics matter more than activity |
| Support and BPO | Attendance with shift policies, idle time, screenshots at a set interval with blur, web rules | Keystroke intensity unless justified and disclosed | Shift adherence and quality review are core requirements |
| Finance | Attendance, file access monitoring, USB controls, alerts on unapproved cloud storage | Frequent screenshots | Data protection risk is higher than productivity risk |
| HR | Attendance, file access monitoring, strict access to reports | Screenshots of employee records | HR handles sensitive personal data, so capture less, not more |
| Field teams | Attendance with optional GPS verification during shifts | Screenshots, web tracking on personal devices | Location matters for field work only, and only while clocked in |
| Contractors | Time and project tracking, attendance where billing requires it | Anything beyond what the contract and billing need | Contractor relationships are defined by deliverables, not supervision |
Keystroke intensity, which in E-Monitor counts typing volume and rhythm only and never captures characters, is off by default. Enable keystroke monitoring only for a role with a documented reason and written disclosure. For field groups, GPS tracking for field teams is opt-in per role group and works during work hours only.
Role-Based Monitoring Settings: Who Sees What
Customizing what is collected is half the job. The other half is controlling who can view it. Role-based monitoring settings should follow least privilege:
- Employees see their own data. In E-Monitor every employee has a personal dashboard, self-access is on by default, and managers cannot disable it.
- Team leads see their direct reports only, not peer teams or the whole company.
- Department heads see aggregated team trends, with individual detail only where their role requires it.
- HR and security get access to detailed records for defined purposes, such as an investigation, and that access should be logged.
- Admins configure profiles but should not browse individual activity by default.
Our guide to role-based access control for employee monitoring covers how to map these roles and audit them when reporting lines change.
How to Customize Employee Monitoring by Team in E-Monitor
The steps below use settings available in E-Monitor's employee monitoring software. Plan and feature availability vary by tier.
- Map teams and roles. Make sure each employee is in the right team and role, because policies and views are applied at those levels.
- Set shift and attendance policies per group. Choose shift patterns and grace windows that match how each team works, for example a strict schedule for a support desk and a flexible window for engineering.
- Configure web rules at organization, team or role level. Set organization-wide blocks for risky categories, then allow social platforms for marketing and recruiting. For detail on rule design, see how to block websites on work computers.
- Tune productivity categories by role. Classify apps for each role, since a design tool is productive for designers and a recruiting site is productive for recruiters.
- Set screenshot rules where justified. Screen monitoring can be enabled for some roles and disabled for others, with different intervals per group and on-device blur for sensitive applications.
- Enable opt-in features only where the purpose test passes. Keystroke intensity and behavioral biometrics are enabled per role. GPS verification is for field teams only.
- Configure alerts per team. Idle time alerts may suit a support queue, while file access and USB alerts suit finance.
- Set report views and schedules. Confirm team leads see only their direct reports, and schedule team-level reports by email on Professional and Enterprise plans.
- Check retention. Detailed data is kept for 30 days on Starter, 90 days on Professional, and is configurable up to 24 months on Enterprise. Keep it no longer than your purpose requires.
Proportionate Monitoring and the Law
Proportionate monitoring is not just good manners. In the EU and UK, employers usually rely on legitimate interests for monitoring, which requires a balancing test and, for higher-risk monitoring, a data protection impact assessment. A documented profile per team, with the purpose and the less intrusive alternatives considered, is exactly the evidence those assessments need.
In the United States, the rules focus on notice and consent rather than proportionality. New York Civil Rights Law section 52-c, Connecticut and Delaware require advance notice of electronic monitoring. Our employee monitoring legal guide summarizes the main requirements. This is general information, not legal advice; check your setup with counsel, especially before monitoring across multiple countries.
Document and Disclose Each Profile
Every team should know its own profile. Put the profiles in your monitoring policy as an appendix, listing for each team what is collected, when, why, who can see it and how long it is kept. The employee monitoring policy template has a structure you can extend with a per-team table.
Explain changes before they happen. If a team's profile gains a feature, say what changed and why, and give people time to ask questions. Privacy-first programs, described in our privacy-first employee monitoring guide, treat disclosure as part of the configuration, not an afterthought.
Common Mistakes When Customizing Monitoring
- Starting with features instead of purposes. Teams that switch everything on and plan to tune later rarely do. Start with every optional feature off and add only what passes the purpose test.
- Creating a profile per person. Individual exceptions are hard to explain, hard to audit and look like targeting. Keep settings at team and role level, and document any temporary exception with an end date.
- Ignoring productivity classification. A single company-wide list of productive and unproductive apps penalizes roles whose tools differ. A recruiter on LinkedIn and a designer in a design tool are both working.
- Forgetting managers' own access. A narrow collection profile means little if every manager can see every team. Collection and access need to be customized together.
- Not telling the team. A carefully proportionate profile still feels like surveillance if nobody explains it. Share the profile, the reason for each setting, and how employees can see their own data.
- Keeping data longer than needed. Retention is part of the profile. Detailed records for a low-risk team rarely need to outlive the next review cycle.
Review Monitoring Profiles Every Quarter
Profiles drift. Teams reorganize, roles change, a temporary investigation setting stays on, and a contractor group ends up with full-time settings. A quarterly review keeps monitoring policies per team aligned with reality:
- Confirm every employee is in the correct team and role, especially after reorganizations and promotions.
- For each enabled feature, ask whether anyone used the data in the last quarter. If not, consider turning it off.
- Remove temporary settings added for a specific project or investigation.
- Check that report access still matches reporting lines.
- Review alert volumes: rules that fire constantly get ignored and should be tuned.
- Record the review, including what changed and why, so the decision trail is available if questioned.
Related reading: Role-Based Access Control for Employee Monitoring Data: Who Should See What and Why, 11 Types of Employee Monitoring (With Examples), Employee Monitoring Policy Template: Free Download for 2026, Privacy-First Employee Monitoring: The Complete Guide to Transparent, Ethical, and Legal Monitoring, When Not to Monitor Employees.
Frequently Asked Questions
1. How do I customize employee monitoring by team?
Create a monitoring profile for each team based on its purpose, risk level and legal requirements. Turn on only the features that serve that purpose, such as screenshots for a support desk or GPS for field staff, restrict report access by role, disclose each profile to the employees it covers, and review profiles quarterly.
2. What are monitoring profiles?
A monitoring profile is the set of monitoring settings applied to a team or role: which features are enabled, capture intervals, web rules, alerts, who can view the data and how long it is kept. Profiles let one organization run lighter monitoring for low-risk teams and tighter controls where risk is higher.
3. Why shouldn't every employee have the same monitoring settings?
Because teams have different purposes and risks. Applying maximum settings to everyone collects data with no use, conflicts with GDPR data minimization, and damages trust. Matching settings to each team's real needs is more proportionate, easier to justify legally and easier for employees to accept.
4. Should keystroke monitoring be enabled for all teams?
No. Keystroke intensity is best left off by default and enabled only for a specific role with a documented reason and written disclosure. In E-Monitor it is off by default, counts typing volume and rhythm only, and never captures characters, words, passwords or search queries.
5. Who should be able to see employee monitoring data?
Employees should see their own data, team leads only their direct reports, and department heads mostly aggregated trends. HR and security should access detail only for defined purposes such as investigations, and admins should configure settings without browsing individual activity by default. Log access to sensitive records.
6. Is GPS tracking appropriate for office or remote employees?
Generally not. Location data is hard to justify for desk-based work and is sensitive. Reserve GPS for field teams whose work depends on location, limit it to working hours, and disclose it clearly. In E-Monitor, GPS verification is optional and intended for field teams only.
7. How often should monitoring profiles be reviewed?
At least quarterly, and after any reorganization. Check that employees are in the right team and role, remove settings nobody uses, retire temporary investigation settings, confirm report access matches reporting lines, and record what changed and why.
Monitor each team for its own reasons. E-Monitor lets you set web rules, screenshot settings and opt-in features by team or role, with role-based views and work-hours-only monitoring. 7-day free trial, no credit card. Sign up →
