Account setup

DevFlow has three nesting levels: workspace → project → monitor/SLO/channel.

workspace

A workspace is the billing boundary. Most companies have one, occasionally two (production vs lab). Name it after your company. Workspace settings live at Settings → Workspace, and only workspace owners can change them.

projects

A project groups related monitors, SLOs, alert channels, and dashboards. Most teams create one project per service or per team — for example payments-api, web-frontend, internal-admin. Projects are the boundary for alert-routing rules and for our roll-up reports.

members and roles

Three roles, simple on purpose:

• Owner — billing, members, plan. One required, multiple supported.
• Admin — everything except billing/members. Most engineers should be Admin.
• Viewer — read-only. Use sparingly; alert acknowledgement requires Admin.

Invite via the dashboard or:

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

SSO + SCIM are available on Scale tier. See rest-api-authentication for service-account creation, and team-onboarding for our recommended day-one walkthrough for new joiners.

tag inheritance

Tags applied at the workspace or project level are inherited by every monitor inside, unless the monitor overrides the tag. We use this to enforce team, env, and owner tags everywhere — tagging-strategy documents the convention we recommend.