Creating Your Organization
The organization is the top-level container in Batida. It holds your teams, schedules, escalation policies, and incidents. Every user belongs to exactly one organization.
Creating an Org During Sign-Up
When you first sign up, Batida prompts you to create an organization automatically. You just need:
- Organization Name -- the display name for your org (e.g.,
Acme Engineering) - Timezone -- the default timezone used for schedules, incident timestamps, and reports
This is sufficient to get started. You can configure additional settings at any time.
Organization Settings
After creating your org, you can access and modify its settings from Settings > Organization.
General
| Setting | Description |
|---|---|
| Organization Name | Display name across the platform. Visible to all members. |
| Slug | URL identifier (e.g., acme-engineering). Used in links and API references. Set once at creation. |
| Default Timezone | Applied to schedules and incident timestamps unless overridden at the schedule level. |
| Language | Interface language for all members. Currently supports English and Portuguese (BR). |
Notifications
Configure how and when your organization sends notifications:
- Default notification channels -- set preferred channels (email, Slack, push) for the entire org. Individual members can override this in their profile.
- Quiet hours -- optionally suppress non-critical notifications outside business hours. P1 incidents always bypass quiet hours.
Danger Zone
| Action | Description |
|---|---|
| Mock Incidents | Toggle this on to allow creation of test incidents that do not trigger real notifications or escalation policies. Useful for onboarding new team members and running incident response drills. |
| Delete Organization | Permanently removes the organization and all associated data. This action requires confirmation and cannot be undone. |
WARNING
Deleting an organization is irreversible. All incidents, schedules, and member data will be permanently removed. Export any data you need before proceeding.
Best Practices
- Choose a descriptive org name. This helps when team members belong to multiple organizations or when referring to the org in incident communication.
- Set the correct timezone. This is the foundation for accurate on-call scheduling. If your team spans multiple timezones, pick the one where most responders are located.
- Enable mock incidents during onboarding. Let new team members practice incident workflows without creating noise in production.
Changing Your Organization
If you need to join a different organization or were invited to one, navigate to Settings > Organization and click Transfer Account. You will need an invitation from the target organization's admin.
INFO
Organization transfers remove you from the current org. Your incidents, notes, and assignments in the old org will remain but will no longer be accessible under your account unless re-invited.