Guide

Workspace Setup

Onboard a Drumbeats workspace — onboarding flow, projects and roles, member invitations, project-level 2FA enforcement, and the first-project checklist.

This guide is the operational setup that happens before your first monitor — Drumbeats onboarding, projects, members, roles, and two-factor authentication. The steps below are the recommended order; each one takes a couple of minutes.

For the actual first-monitor walkthrough, see Quickstart. For billing semantics, see Billing lifecycle.

1. Complete onboarding

After signup, Drumbeats walks new users through onboarding before they land in the full app. Onboarding collects:

Name
Company
Title
Legal acceptance for Terms and Privacy
Optional marketing consent

A first project is created automatically as part of onboarding so the user is not staring at an empty dashboard.

2. Create or select a project

Projects are the main working boundary in Drumbeats. Monitors, members, notification groups, and status pages all belong to a project.

3. Understand the four roles

Drumbeats supports four project roles. The role assigned to a member determines what they can do everywhere in the dashboard and REST API.

Role	What it can do
`OWNER`	Full control, including billing settings and project deletion.
`MANAGER`	Manage monitors, notification channels, notification groups, and members. Create and revoke API keys.
`MEMBER`	Work with monitors and acknowledge / resolve incidents within their granted access.
`READONLY`	View-only access. Cannot acknowledge incidents.

Use READONLY for stakeholders who need visibility into current status but should not change alerting or configuration.

4. Invite teammates

Invite teammates from the project's settings panel.

Open the project settings.
Choose Invite Member.
Enter the user's email.
Select the role from the four options above.
Send the invitation.

Managers and owners can manage invitations. Invitations are project-scoped — accepting one adds the user to that project only, not the workspace at large.

The Invite Team Member dialog in Project Settings, with the email field, role dropdown, and the "Unlimited teammates" banner

5. Enforce 2FA where needed

Drumbeats supports per-user TOTP and project-level 2FA enforcement.

When project-level enforcement is enabled:

Members without TOTP configured are blocked from access.
The REST API returns TOTP_REQUIRED_FOR_PROJECT for those members until they enroll.

Enable enforcement on production projects and customer-facing environments.

6. Connect notification channels and groups

Before relying on any monitor in production, wire up notifications. The shape recommended is:

Add at least one notification channel (Notifications: channels).
Click Test on the channel to verify delivery.
Create a notification group for the responsible team (Notifications: groups).
Attach the group to each production monitor.

A monitor with no notification group does not page anyone, no matter how many alerts fire — see Alert logic.

Recommended first-project checklist

A pragmatic short list before you ship the project to production users:

Finished onboarding.
Project name and members confirmed.
TOTP enabled on your own account.
Decision made on project-level TOTP enforcement.
Notification group created for the owning team, with at least one channel tested.
First monitor created and an end-to-end alert tested with a manual failure ping.

Quickstart — create your first monitor end-to-end.
Billing lifecycle — how owner-wide billing works after Pro / Business upgrade.
REST API — project- and account-scoped API keys (account keys are minted under Account → API Keys) and their permission scopes.
REST API — Projects — programmatic access to project and member metadata.
Trust Center — the security-relevant behaviour described in role assignments.
Notifications hub — channels, groups, alert logic.