Privacy-safe time context
Use effective assigned time for planning and review while keeping the detailed application and browsing context that Lumen observes out of the shared Kato workspace.
Connect a personal Lumen account and select a workspace without exposing application names, window titles, or URLs.
Use effective assigned time for planning and review while keeping the detailed application and browsing context that Lumen observes out of the shared Kato workspace.
Each member connects the Lumen account they are permitted to use rather than sharing one person's credentials across an entire Kato workspace.
Supported manual time changes can be written back to Lumen, helping the connected systems agree without making Kato the owner of raw automatic tracking data.
Each member installs OAuth application credentials supplied by an authorized Lumen owner or admin, then personally authorizes the Lumen account they want to connect. Recent effective segments are cached with interval replacement, and manual changes are written back to Lumen.
Compare assigned effective time with the task estimate during a project review and adjust future planning without exposing an individual's detailed computer activity.
Authorized owners and admins can use mapped workspace time as one input when discussing workload, estimates, and delivery patterns with the team.
Add or adjust supported manual entries when work needs a clearer assignment, then keep Lumen as the source for the resulting effective-time history.
No. The integration is designed around effective assigned time and does not expose application names, window titles, or URLs in the Kato workspace.
Yes. Members authorize the personal Lumen account they intend to connect. Owner or admin involvement may still be needed to supply application credentials or map team views.
Lumen remains responsible for automatic tracking and its detailed private context. Kato consumes the effective time needed to support connected work and planning.
Last updated Aug 21, 2026