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

Integrations

Slack

Slack supplies presence bands and lightweight collaboration metadata for the monitoring timeline. WePeople polls on a fixed cadence and never reads message bodies or direct messages.

Setup

  1. An Admin or Owner connects Slack from Organization → Integrations via OAuth.
  2. Link each monitored worker to their Slack user under People.
  3. Select the public channels that reflect real team work (see Channel selection).

Step-by-step marketing walkthrough: Slack integration page.

Presence

WePeople polls Slack presence every 5 minutes and stores active vs away samples for each linked worker. Those samples drive the day-view presence strip, active-minute totals, and break detection (three consecutive away minutes inside a work session).

Presence events use types such as slack_presence on the timeline. If Slack is unreachable or a worker is unlinked, gaps are visible — we do not interpolate missing minutes.

Org-local day

Presence buckets align to your organization timezone and schedule, not each person’s browser locale.

Messages & reactions

Message posts and reactions in selected channels become metadata events — who, which channel, and when. Thread replies appear as message events too; content stays in Slack.

Timeline types include slack_message and slack_reaction. Reports aggregate counts per effective hour as an engagement signal — density, not a “most talkative” leaderboard.

Channel selection

After OAuth, Admins choose which public channels WePeople monitors. The integration bot joins only channels you select — noise channels and company-wide announcements can stay out.

Channel IDs are used to validate scope and compute breadth signals (how many distinct channels a person touched). Private channels and DMs are outside the product surface unless explicitly supported in a future release.

Practical tips

  • Prefer team engineering channels over org-wide social feeds.
  • Revisit selection when teams reorganize — stale channels add noise without improving signal.
  • Disconnecting Slack deletes encrypted tokens immediately; data enters your retention-based deletion flow.

What we do not read

The Slack connector is scoped to metadata. WePeople never requests or stores:

  • Message bodies or thread content
  • Direct messages or private channel messages
  • File attachments or uploads
  • User-level Slack analytics beyond your monitored worker set

Full read / do-not-read matrix: marketing detail page and trust model.

On this page

  • Setup
  • Presence
  • Messages & reactions
  • Channel selection
  • What we do not read
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.