WePeopleDocs
IntegrationsPricingDocsSign inGet started
Get started
Docs home

Getting Started

  • What is WePeople
  • First week checklist
  • Core concepts

Product

  • Monitoring
  • Reports
  • People & profiles
  • SPACE scoring
  • Organization settings
  • Statistics
  • Billing & retention
  • Privacy model

Integrations

  • Overview
  • Slack
  • GitHub
  • Jira
  • Trust model

Developers

  • Platform overview
  • Quick start
  • Ingest guide
  • Custom statistics
  • Hosted MCP
  • TypeScript SDK

API Reference

  • Overview
  • Auth & headers
  • GET ping
  • POST events
  • POST snapshots
  • Apps statistics
  • Error codes
  • OpenAPI & SDK

Browse docs

Getting Started

Core concepts

A short glossary of the nouns WePeople uses everywhere — in the UI, Ingest API, and MCP tools.

Workers

A worker is a person (or AI agent) WePeople monitors. Workers can have linked Slack, GitHub, Jira, and custom identities. Human vs agent changes scoring weights and whether Satisfaction applies.

In the Ingest API, every event carries an actor resolved by workerId, then externalId, then email. See Identifying workers.

Teams

Teams are org-defined groups used to filter monitoring, reports, and some MCP queries. Rename and membership live under Organization → Teams; person profiles only assign membership.

Organization calendar

All “today / this week / this month” math uses the organization’s IANA timezoneand week-start day — not the browser’s local zone. Frequency-style KPIs typically count weekdays Mon–Fri and exclude future weekdays in that timezone.

Fair totals

Reports can exclude days below an activity threshold or weekdays your org does not credit. That is intentional noise control, not data loss — activity can still appear on the person timeline.

Integrations & modules

Each connected system is a module (slack, github, jira, or custom:<app-slug> for developer apps). Monitoring filters use the integrations query param with those ids.

Timeline events

The monitoring timeline is a stream of typed events — for example slack_message, github_commit, github_pr_merged, plus your custom eventTypevalues. Presence (active / away) comes from Slack samples; breaks are contiguous away spans inside the day’s active window.

Next: Monitoring guide.

On this page

  • Workers
  • Teams
  • Org calendar
  • Integrations
  • Timeline events
WePeople

Team insight, not surveillance. A lead's-eye view built on metadata from the tools your team already uses — never source code, never messages, never DMs.

Product

  • Monitoring & Reports
  • SPACE scoring
  • Pricing

Docs

  • Docs home
  • Getting started
  • Developer platform
  • API reference
  • MCP

Integrations

  • Browse integrations

Company

  • Support
  • Status

Legal

  • Brand
  • Privacy
  • Terms

© 2026 WePeople. Built with care.

Metadata only. No source code, no message bodies, no DMs — read the policy.