Kordano Founding 25 for teams of 6+: $3/user/month, month to month, locked for 24 months
Kordano
Kordano Insights

Practical guidance for running clearer, more accountable teams.

Privacy & Trust

Employee Screenshot Access After a Manager Changes Teams

By Haris Ali D. · Published October 27, 2026

Share

A manager's transfer between client teams should trigger an access decision. Can that person still open screenshots from the old team? Can they open images captured before they joined the new one? The answer affects client confidentiality and the employees whose screens were captured.

Changing the manager's team label is not proof. The decision has to hold for archived images, direct viewing links, and copies already exported from the tool. For an agency or BPO, the useful output is a short transfer receipt: the access you intended, the access you tested, and the person who approved any exception.

Decide what happens to old screenshots

Choose the history rule before changing permissions. Two reasonable policies produce different answers:

History ruleWhat a newly assigned manager seesWhat a departing manager loses
Current team scopePast and future screenshots of employees now in scope, subject to the tool's permissionsPast and future screenshots of employees no longer in scope
Capture-time scopeScreenshots captured while the manager was responsible for that teamNew screenshots after responsibility ends; older access needs its own expiry or removal rule

These are policy choices, not promises about a particular product. Current vendor documentation shows why the choice needs a test. Clockify's Activity Monitoring role guide says a team manager removed from a member's group immediately loses access to that member's historical monitoring data, including screenshots. Insightful's org-group guide says adding an org group to a manager's scope exposes historical employee data from the employee's start. The two documents describe different products and configurations; neither proves how your own workspace behaves.

Write down whether a new manager needs old client images to resolve a specific review, and whether a departing manager has a remaining duty that truly requires them. If the answer is yes, name the image set, purpose, viewer, approver, and end condition. Do not leave a broad role in place as a substitute for a narrow exception.

Run one transfer test before real client work moves

Use harmless sample images for two fictional clients. Give one manager access to Client A and another to Client B. Keep a screenshot from before the transfer and create another afterward. Then move the first manager to Client B.

  1. Record the starting state. Note the manager's role, team or group membership, screenshot-view permission, and the old image they can open. Save an object identifier or test timestamp, not the image itself.
  2. Change the assignment. Remove Client A scope and grant only the approved Client B scope. Record the effective time and who made the change.
  3. Check both directions. As the transferred manager, try Client A's old image and a new Client A image. Try Client B's old image and a new Client B image. Compare each result with the chosen history rule.
  4. Check the paths outside the list view. Reopen an old thumbnail or direct application URL. Repeat with a previously issued clear-image link, then after its expiry. Test download and export rights separately.
  5. Close the copies. Find any screenshot already downloaded, emailed, or placed in a client folder. Changing a role inside the application does not retrieve a file someone exported earlier. Assign a named owner to remove or retain each copy under the client policy.

The decision is pass when every tested path matches the approved scope and any retained copy has an owner and purpose. Otherwise hold the transfer's screenshot access, fix the configuration or handling rule, and repeat the failed test. Record the attempted viewer, object, action, expected result, actual result, and time. Keep sensitive image content and live access links out of the receipt.

This is narrower than a general screenshot privacy buying test. It checks one change event: whether a manager's old authority ends and new authority begins at the intended boundary.

Keep the protection layers separate

Stored-media encryption protects a different problem from viewer permissions. Cloudflare R2 encrypts stored objects and metadata with AES-256 and supports TLS for transfers. AES-256 protects the media at rest. TLS protects it while it travels. Neither decides whether this manager should see this employee's screenshot.

The application must make that access decision. OWASP recommends checking permission on every request, including paths that bypass a dashboard list. A temporary clear-image link has another boundary: Cloudflare describes presigned URLs as bearer access until expiry. A manager who already holds one may still be able to use it during its remaining lifetime. Test that interval and avoid placing the link in tickets or shared notes.

Blur addresses the content an authorized person receives. It does not grant or revoke that person's access. The employee monitoring notice template helps explain the actual viewer policy to workers. For UK employers, the ICO's worker-monitoring guidance calls for access limited to those who need it and for workers to understand and challenge monitoring information. Apply local requirements to each team; the operational test remains useful wherever the team works.

What KordanoTime will carry into Early Access

KordanoTime's December 1, 2026 first release includes time tracking and screenshot review. Its planned default media path stores screenshots and recordings in Cloudflare R2. The inspected screenshot-viewing flow requires a signed-in viewer with screenshot permission, checks organization and target visibility, and gives clear images a five-minute link. When screenshot blur is enabled, an authorized viewer receives a blurred image through an authenticated route. Stored-media AES-256, TLS in transit, permissioned access, expiring links, and blur each protect a different part of the path.

Early Access limits are explicit: teams have 500 screenshots per month, and working-product and deployment checks remain part of launch readiness. A team-transfer rule still needs a real configuration test. The inspected controls do not establish that every previously issued clear-image link is revoked at the instant a role changes, nor do they bring back exported copies. Your team sets the history policy and verifies the result with harmless images before using client data.

When a manager changes teams, make the transfer receipt part of the handoff. Review KordanoTime's first-release approach, then ask the person responsible for screenshot access to show the old and new viewer results, not just the updated role label.

Privacy & Trust
Become a founding member

Companies with teams of 6 or more can lock $3 per person per month for 24 months.

Claim your spot
Limited to 25 qualifying companies
Haris Ali D.
Haris Ali D.
Co-Founder at Kordano
Get in touch

Haris Ali D. is the Founder of Kordano, a workforce operating system for modern teams. He focuses on building practical tools for time tracking, attendance, productivity visibility, and team operations.

He also brings experience in branding, digital strategy, and software development through FullStop, a company he co-founded in 2012.

World-class productivity advice

Practical tips in your inbox. No spam.