Monitoring

Open Monitoring from the app sidebar after you connect at least one integration. The board lists every monitored worker for the selected period, with a strip chart or table depending on view mode. Click a person to open their detail timeline for the same day, week, or month.

For a visual walkthrough, see the Monitoring feature page.

• Day— one organization-local calendar day. Shows presence strips, per-integration activity, and same-day SPACE dimensions in the sidebar. Best for standups and “who is around today?”
• Week — seven columns starting from your org week-start day (Organization → Schedule). Compare daily patterns across the team without leaving the board.
• Month — calendar grid per worker. Useful for spotting rhythm changes, PTO-shaped gaps, and end-of-sprint delivery clusters.

Period navigation uses the organization timezone — not the browser’s local zone. See organization calendar.

Filters are URL-stable query params so you can bookmark or share a view. They appear in the filter bar (desktop) or bottom sheet (mobile).

• Integrations — integrations=slack,github (legacy filter= still works). Limits which module events contribute to tiles and totals. Default is all connected modules.
• Sort — sort=name|score|active. Reorders the worker list by display name, overall SPACE score, or recent active time.
• Workers — workers=human|agent|all. Human vs AI agent split. Agents appear on the same timeline but use different scoring weights.
• Team — team=<teamId>. Restricts the board to members of one org-defined team.

When Slack is connected, WePeople samples presence (active / away) for monitored workers. The day strip shows contiguous active spans and breaks — away periods inside the day’s active window, not calendar midnight-to-midnight sleep.

Presence is a capacity signal, not a productivity score. A long break during deep work is normal; the timeline still shows delivery events from GitHub or Jira even when Slack says away.

Aggregated numbers on monitoring and reports can apply your org’s logged totals policy from Organization → Schedule:

• Exclude weekdays you do not credit (e.g. Friday off-site).
• Drop days below a minimum activity threshold (noise control for partial PTO or travel).
• Optionally hide excluded weekdays in week/month grids while still storing raw events.

Fair totals affect rollups and comparisons — not whether events exist on a person’s timeline. A dashed underline on a total opens the policy explanation in-app.

Each person detail page streams typed events: slack_message, github_commit, github_pr_merged, Jira transitions, and custom eventType values from the Ingest API. WePeople stores metadata only — timestamps, channel/repo ids, event subtypes — never message bodies or source code.

Custom developer apps appear as custom:<app-slug> modules in integration filters alongside Slack, GitHub, and Jira.

• “Monitoring ranks my team.” Sort by score is optional and symmetric — everyone can see it. SPACE is dimensional, not a league table. See SPACE scoring.
• “Away means not working.” Delivery events can land while Slack presence is away. Use the full timeline, not presence alone.
• “Fair totals deleted my data.” They adjust denominators for reports; raw events remain on the person timeline within your plan retention window.