Get started as an Account Owner
Start building your teams, integrate your tools and create on-call schedules, with Squadcast
Your Role as an Account Owner
You are responsible for the management of the overall configuration, workflow, user permissions, and billing. You are the root user of the organization.
Your Permissions as an Account Owner
You have access to all functionality across the platform including scheduling, integrations, teams, user permissions, and billing.
To begin, configure your profile:
Explore the mobile and web platforms to get comfortable before beginning your configurations.
Next, start adding users and stakeholders to your organization. You can manually add each user or bulk import them using a .csv file. Alternatively, you can automatically provision them using an SSO.
Once you have added users to your organization, you can customize their access to the account by adding additional permissions. These are additional levels of permissions, on top of the User Type that they have been added as. You can only customize permissions for users and not stakeholders.
Next, create teams to segregate data and have different environments for different functional teams. By default, all the users are added to the default team. The default team cannot be deleted.
Next, assign roles in a Team from within Squadcast Roles: Admin, Users, and Observers, or create custom roles.
Squads are sub-groups that can refer to folks handling a specific functionality, service, or project within the team. Squads are handy when you need to notify the whole group together. For instance, when a coordinated response is required for high-urgency high-complexity incidents, or at the end of an escalation policy when nobody has acknowledged it.
- Payment gateway Squad
- Backend Squad
- Frontend Squad
- All Hands
Once teams are created, you can set up your on-call schedules. An on-call schedule is used to determine who is on-call at a given time. They are based on different time zones and configurable rotations.
Next, create escalation policies, and add your on-call schedules to them. This will automatically notify your on-call engineers when an incident is triggered.
- Website Monitoring
- Payment Portal Monitoring
- Backend Issues
Next, set up Services within Squadcast.
Services are at the core of Squadcast. A service represents an application or component that is crucial for your product or service. Services are created with an alert source integration through which incidents are triggered. Squadcast provides a Webhook URL to integrate with the tools you use.
You can search through our documentation to find helpful alert source integration guides to walk you through any particular integration.
Extensions are deeper integrations with tools where actions can be taken from within the platform to reflect on the tool as well. Within Squadcast, these are called Extensions and can be found on the navigation sidebar.
Typically, extensions augment your incident management process by connecting with other tools where actions are required. ITSM, Communication, Web conferencing, Version Control, CI/CD, and SSO tools would typically act as extensions.
Incident Tags are used to add more context to your incident and help classify incidents. You can configure tags from Tagging Rules associated with a service. You can configure tagging rules with an incident JSON to automatically add tags when incidents are triggered or you can manually create and update them.
Alert Routing allows you to configure rules to ensure that alerts are routed to the right responder with the help of event tags attached to each alert. Routing is a part of the rules engine associated with each service. You can access routing rules from a service’s options dropdown. Note that this rule will override the escalation policy attached to the service. This is typically used in cases where severities are configured via tags and each severity type is to be handled by a different level of on-call user.
Alert Deduplication can help you reduce alert noise by organizing and grouping relevant alerts. This also provides easy access to similar alerts when needed. You can configure deduplication rules with an incident JSON to automatically deduplicate and group similar incidents and can see this reflected on the incident dashboard.
Suppression Rules is a part of the Squadcast Rules Engine that allows you to configure rules to automatically suppress non-actionable alerts such as warning, informational, or test alerts. All suppressed data will still be available on the platform.
Status Page helps you communicate status updates of your services to your customers and stakeholders about outages and scheduled maintenance.
Status Pages can either be public (accessible by everyone) or private (accessible by just your team on Squadcast) on Squadcast. You can also add a subscription option for your public status page so customers are automatically informed of any updates on the Status Page.
An Incident Postmortem is a post-incident review that allows users to learn from major incidents by providing a summary of events that transpired, how the response was handled, and what steps were taken to resolve the incident.
You can create an incident postmortem from within an incident page once the incident is resolved. You can choose from several popularly used postmortem templates or create custom templates for your Organization.
SLOs are used to define and track your service’s performance delivery. Any breach of SLOs will trigger an incident and notify the relevant Users, Squads, or Schedules.
Analytics help you view the performance of your Organization/Team, for a given period. It helps gain insights into how your system is functioning and what shape your responders are in.
You can also filter reports based on specific services, tags, and users.