Quick Start

Get Batida up and running for your team in five steps. This guide walks you through creating an organization, inviting your team, setting up an on-call schedule, and declaring your first incident.

Step 1 -- Sign Up

1. Go to app.batida.io and click Sign Up.
2. Create your account using email and password, or sign in with Google/GitHub.
3. Verify your email address if prompted.

INFO

You can sign up with a personal email and configure your organization's identity later. The org-level settings are independent of your account email.

For all available sign-in methods, see Authentication.

Step 2 -- Create Your Organization

1. After signing in, you'll be prompted to create an organization.
2. Enter your Organization Name (e.g., Acme Engineering).
3. Select your Timezone -- this is the default for all schedules and incident timestamps.
4. Click Create Organization.

For detailed configuration options, see Creating Your Organization.

Step 3 -- Invite Your Team

1. Navigate to Settings > Members from the sidebar.
2. Click Invite Members.
3. Enter the email addresses of your teammates.
4. Assign a role to each invite:
   • viewer -- read-only access to incidents and schedules
   • responder -- can acknowledge and resolve incidents
   • admin -- full management access
5. Click Send Invites.

You can also share an invite link that lets people join with a predefined role.

TIP

Start by inviting your immediate on-call rotation. You can add more members as you expand incident coverage across teams.

For more details, see Inviting Members.

Step 4 -- Create Your First On-Call Schedule

1. Navigate to Schedules in the sidebar.
2. Click New Schedule.
3. Give it a name (e.g., Backend On-Call).
4. Select the timezone for this schedule.
5. Add a rotation:
   • Choose the rotation period (daily, weekly, custom).
   • Select the team members who will rotate.
6. Click Save Schedule.

Your schedule is now active. Team members can view their on-call shifts and request swaps from their profile.

WARNING

Make sure all team members in a rotation have notifications enabled (Slack, email, or push) so they receive alerts when an incident is assigned.

For a full walkthrough, see Your First Schedule.

Step 5 -- Declare Your First Incident

1. Navigate to Incidents and click New Incident.
2. Fill in the incident details:
   • Title -- short description of the problem (e.g., Payment API returning 500 errors)
   • Severity -- select from P1 to P4
   • Description -- provide context, affected services, and initial observations
3. Click Create Incident.

Batida will notify the on-call responder based on your active schedules and escalation policies.

TIP

Use the mock incidents toggle in your organization settings to create test incidents without triggering real notifications. This is useful for onboarding and演练 (drills).

What's Next?

• Configure escalation policies so incidents are automatically reassigned if no one responds.
• Set up Slack integration to manage incidents directly from your channels.
• Write your first AI-powered postmortem after resolving an incident.