Squadcast Support

The Squadcast support Developer Hub

Welcome to the Squadcast support developer hub. You'll find comprehensive guides and documentation to help you start working with Squadcast support as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Quickstart Guide

Take your first steps towards incident management using Squadcast.

Welcome to Squadcast!

Our platform helps you simplify incident management, get meaningful notifications, and enable faster incident resolutions in collaboration. Explore all the incredible SRE tools and incident response capabilities in this documentation.

Let's get started together on the mission to eliminate downtime. Begin with the basic setup guide based on your role in the organisation: Account Owner, Admin, User or Stakeholder.

Getting Started as an Account Owner

An Account Owner has all the privileges for managing an organization on Squadcast. There can be only one Account Owner for an organization. And only she can access the Billing page to manage subscription.

Learn more on how to manage your profile and other users. In case you're also responsible for setting up of incident management tools, you can see the Admin's section below.

Getting Started as an Admin

Admins on Squadcast have privileges to manage Users, Services, On-call Schedules, Escalation Policies, and so on. The only exception to an Admin's account is the privilege to manage Billing which is an exclusive privilege of the Account Owner.

Here are a few initial steps:

Manage Users on Your Organization

As an Admin, you can add or remove Admin, User, and Stakeholder accounts. This privilege is not available for User and Stakeholder roles. See how to Manage Users →

Setup Escalation Policies

Squadcast enables you to add time-based escalation rules for Users, Squads (a group
of Users) or Schedules (on-call schedules). See how to Manage Escalation Policies →

Add Services

Services on Squadcast are integrations with alert generating tools connected to your infrastructure. You need to have at least one escalation policy before you can add a Service. Squadcast provides a Webhook URL to integrate with the tools you use. See how to Manage Services →

Need more integrations?

In case you don't find an integration, email us at support@squadcast.com. Our team will reach out to you within a working day.

Setup Schedules

Schedules can be used to create on-call schedules based on different time-zones, configurable rotations, and multiple hand-offs. You can create unique Schedules for each Services, having only the relevant engineers. See how to Manage Schedules →

Setup up Service Level Objectives (SLOs)

The Service Level feature allows you to create Service Level Objectives (SLOs) for Service Level Indicators (SLIs) like latency and status codes. Any breach of SLOs for Services will trigger an incident and notify the relevant Users, Squads (a group of Users) or Schedules (on-call schedules). See how to configure Service Levels →

Incidents Response and Resolution

The Incidents Details page is where engineers can take actions and respond to the triggered incidents. Squadcast provides functionalities like War Room, Incident Timelines, and Squadcast Actions.

Getting Started as a User

A User role on Squadcast can take actions to trigger, acknowledge, and respond to the incidents. As a User, you can view all pages except the Billing page which is only accessible which can be accessed only by the Account Owner of the organization. See how to Manage Your Profile →

Getting Started as a Stakeholder

Stakeholders are other people who need to know about the site reliability efforts. These can be Customer Support representative, Product Managers, CxOs and so on. See how to Manage Your Profile →

Latest Updates

We are constantly shipping exciting feature to help you get better at achieving your site reliability goals! See the latest updates →

Quickstart Guide

Take your first steps towards incident management using Squadcast.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.