People & profiles

Open People from the app sidebar. The directory lists every worker seat in your org with search, status, and integration filters.

• Search — match display name or email.
• Status — active vs paused monitoring (enabled flag).
• Services — filter by linked Slack, GitHub, Jira, or custom app identities.

New workers appear when integrations discover accounts or when you invite members who map to seats. Plan limits cap total worker count — see Billing & retention.

Click a row to open the person profile. Admins and the worker themselves (when applicable) can edit:

• Display name, email, and avatar.
• Worker type — Human vs AI agent (affects SPACE weights and Satisfaction eligibility).
• Role profile — Developer, Designer, Manager, and other presets that drive SPACE dimension weights.
• Team memberships (assignment only; team definitions live under Organization).

From the profile you can jump to Monitoringfor that person’s day, week, or month timeline.

Each integration links external accounts to one worker. Auto-match runs on first sync; unmatched accounts need manual linking in the profile.

• Slack — user picker maps Slack user IDs. Required for presence and message metadata events.
• GitHub — login association for commits, PRs, and reviews.
• Jira — account linking for issue transitions and story points.
• Custom apps — Ingest API resolves actors by workerId, externalId, or email. See Identifying workers.

Integration profile cards on the person page summarize linked services and last-seen activity per module.

Teams are defined under Organization → Teams (name, slug, membership). Person profiles only assign workers to existing teams — they do not create teams.

Team membership drives the team= filter on monitoring and reports. A worker can belong to multiple teams; filters include anyone in the selected team.

Any worker (or an admin on their behalf) can pause monitoring by toggling Monitoring paused on the profile. While paused:

• New ingestion for that worker stops appearing on the shared dashboard.
• The pause state is visible to everyone — ICs and leads see the same label, not a silent gap.
• Use it for focus blocks, PTO, parental leave, or personal time without implying disengagement.

Resume monitoring when the worker is ready to rejoin the shared view. Historical data within your plan retention window remains stored.

• “Deleting a person erases Slack history.” WePeople only drops linked metadata in your org; it does not delete data in Slack, GitHub, or Jira.
• “Unlinked GitHub means no commits.” Events may exist but sit unattributed until you link the login.
• “Pause hides me from my manager only.” The dashboard is symmetric — pause is visible to all org members with access to People and Monitoring.