Team onboarding

A short, opinionated path for getting a new engineer productive on DevFlow in their first day.

1. invite the engineer

The owner or an admin sends an invite from Settings → Members, or:

devflow members invite engineer@example.com --role admin

Most engineers should be Admin — Viewer-only quickly becomes a permissions tax. See account-setup for the full role matrix.

2. CLI install

Have them install and log in:

npm install -g @devflow/cli
devflow login
devflow config set workspace acme-prod

Detailed steps live in cli-install.

3. tour the existing monitors

Send them three links:

• /monitors — the live monitor list, filtered by their team's tag.
• /slos — the SLOs their service owns. slo-overview explains the model.
• /incidents — the last 30 days of incidents on their service.

4. let them break something safe

Have them create a monitor against a known-bad endpoint (your staging /__health/fail if you have one) and watch the alert fire end-to-end. The whole point of quickstart is that it should take under five minutes.

5. set the on-call schedule

Day-one hires should not be on call. Confirm they're not in the rotation in on-call-schedules. Day-30 onboarding does that explicitly.

what next

• The team's tagging conventions — tagging-strategy.
• Alert routing for noisy weekends — alert-routing and notification-throttling.
• The SLO workbook is the most-cited internal doc; have them read slo-multi-window-alerting in their first week.