Platform

Admin settings

Almost everything is a setting with a default, a help text, examples, and an override chain: person, then team, then organisation, then the shipped default. Every change is audited.

The registry

Bot Behavior lists every setting by category with its type, default, allowed range, help text and worked examples. Strict, standard and relaxed presets set a whole category at once. Per-team overrides live beside the global value with a team selector; a handful of settings can also be overridden per person. Changes invalidate caches, take effect immediately, and land in the settings audit with old value, new value, scope and actor.

Sign-inkeywords, late threshold, absent warning and strike minutes, required lines, location tag, sign-off reminder
Strikesmaximum, rolling period, inactivity hours, cooldowns, critical keywords
Hours and Attendancehours per day, short-day threshold, daily ceiling, retro session limit, rest rules, tracking start date
PTOkeywords for leave and sick, approver requirement, consecutive-day cap, hand-over gate
Scoring modelweights, grace bands, strike tariffs, overtime and kudos caps, missed sign-off deduction, model choice
Goals, Work health, Neuraltargets and benchmark weeks; overwork thresholds; modes, bands, guardrails and drift windows
Presenceping cadence and windows, mobile detection and weights
AI Promptsassistant and voice prompts, manager briefing prompt, daily call budget, model lock
Team featuresblocker SLA, hand-off recap, kudos, manager digest, announcement escalation
Reports, DM, Templates, Voice, Integrations, Generaldigest cadences, quiet hours and never-DM list, every message template, voice switches, dev-activity, organisation basics

Team settings

  • Working days as a seven-day picker; a Sunday to Thursday week is one click.
  • Sign-in deadline and buffer, or flexible sign-in that grades on hours only.
  • Expected hours per day; per-person weekly hours for part-timers.
  • Holiday calendar; week start day; manager room; availability pings on or off with their cadence.
  • Rooms of each type assigned to the team and the bot that watches them.

Automations

Background jobs are listed with an on and off switch and a run-now button. Disabling one makes it a no-op without removing it. Availability pings are off by default; the AI failsafe and scheduled messages are on.

pingpong
ai_failsafe
scheduled_dms

Keys you will meet first

signin.late_threshold_minutesbuffer added to each person’s own average start
hours.min_per_daythe default expected day
scoring.hours_grace_pctfull hours credit at or above this share of expected (97)
scoring.missed_signoff_deduction_hourshours deducted on a day with no sign-off (3)
attendance.max_daily_actual_hoursdaily ceiling before a day goes to review (12); 0 switches it off
pulse.blocker_sla_hoursblocker SLA (2)
goals.target_efficiencythe on-track line (70)
neural.modeoff, shadow, assist or auto
ai.daily_call_budgetnon-essential AI calls per day (300)
dm.never_dm_userspeople the bot never messages proactively

Safety of changes

  • A stretch below its target, or a red threshold below amber, is ignored in favour of the sane value rather than silently inverting the bands.
  • Changing scoring weights or the model invalidates every cached score; the nightly rebuild recomputes them and the benchmark refills afterwards.
  • Changing a target never changes a score. Changing working days applies going forward only.
  • Self-exemption from scoring needs a superadmin, and every exemption is audited.