Configuration
Everything the workspace admin controls. Viewing as Isabel Larsson.
Connectors & data sources
18 vendors · 11 classes of informationWe sync from your systems of record — you never make duplicate edits. Every class has more than one option, and one vendor can feed several classes. See Levels & data sources for sync status.
Identity & HRIS
Org chart, the account graph that stitches every other source to a person, and admin scope.
IDSCIM 2.0 directory (Okta, Entra ID, Google, OneLogin…)
AI usage
Which work was AI-assisted, and the token/cost footprint — content read transiently, never stored.
Claude EnterpriseAIOpenAI / ChatGPT Enterprise
Team chat
Public-channel discussion, threads and reactions — collaboration and enablement signal (never DMs).
TeMicrosoft TeamsSlSlack
Code & delivery
PRs, reviews and deploys — what shipped, who reviewed, and the path to production.
GitHubGitLab
Incidents & on-call
On-call load, MTTR and change-failure — operational reliability signal.
PDPagerDuty
Project management
Tickets, epics and status — the planned-work spine projects are reconstructed around.
GitHubGitLabJiraLinearNotion
Docs & knowledge
Doc authorship, edits and comments — durable knowledge and design contribution.
GitHubGoogle WorkspaceMSMicrosoft 365 / OutlookNotion
Email
Work-scope threading and routing metadata (personal-scope bodies are never read).
GmailGoogle WorkspaceMSMicrosoft 365 / Outlook
Calendar
Meeting invites and pairing — coordination cost and who worked with whom.
Google CalendarGoogle WorkspaceMSMicrosoft 365 / Outlook
Experiments
Launched experiments and their measured impact — did the work move a metric.
ExIn-house experiment logLDLaunchDarkly
Availability
Time-off / working days — so load and consistency are fair, not penalized for PTO.
BHBambooHRHRIn-house HR feed
Deliberately excluded (governance, not a gap)
- Slack / Teams private DMs — 1:1 DMs are not a reliable work signal and carry NLRA / privacy risk.
- Personal-scope email bodies — Metadata only; the connector never fetches personal-scope message bodies.
- Sentiment / mood / health / competence — Out of scope by design — we reconstruct work facts, never inferred states.
System-of-record per domain (this tenant): activity: Claude · Slack · Google · GitHub · levels: Google Sheets · org_chart: Slack Enterprise Grid
Leveling rubric
View ladder →Your qualitative ladder is imported from your rubric; we map observable evidence to each expectation.
Last imported from Comp & Leveling sheet.
Governance & guardrails
These are enforced in code and can’t be switched off — they’re what makes the tool deployable.
- Health / medical data excluded from scoring🔒 Enforced
- Private DM content never ingested🔒 Enforced
- Message/content bodies never stored (metadata only)🔒 Enforced
- Human-in-the-loop required for promotion / PIP / exit🔒 Enforced
- Every view of another person's data is audit-logged🔒 Enforced