HomeDocumentationAPI Reference
Getting StartedAPI ReferenceHelp CenterVideo Tours

Team Ownership

Have ownership and get alerted if it's relevant to your team

To set up team ownership in the Instabug dashboard, you will need to go through a couple of steps. Team ownership will help ensure every crash gets assigned to the corresponding team. Assignation can be done either manually or automatically. First, Teams are created on the account level. Then, they are automatically assigned through team definitions. These steps will ensure you create the best possible team definitions. This will automatically route the issues related to each team within your organization. It will enable you to then prioritize issues related to your team and get alerted about them.

Team Creation

The first step of team ownership is creating the team using the following steps.

To create a team, you will go through “Account management” (on the organizational level) at the top right corner of the dashboard


Go to "Account Management" from the top right corner

Then, from the left list choose “Teams”, then “Create a team”


Select "Teams"

Choose the most suitable Team name, example "Payment"


Insert your team name then create

Automatically Assign Crashes to Corresponding Teams

The following steps show how you can leverage team ownership. First, you would need to create the team on the organizational level. Next, you will need to define each team using the path/package or filename they are responsible for. Each team can then have issues related to them routed to them automatically. They can also prioritize their issue through filtering their team's issues only. Last, these teams can get alerted on their favorite tool, so they can be alerted whenever an issue occurs.


  • Team Definition
  • Prioritizing
  • Alerting
  • Insights

Team Definition

To define the team, you will need to go to “Settings” (on the app level) from the bottom of the sidebar (on the left)


Go to "Settings"

Then, choose “Team ownership”, then "Create Definition"


"Team ownership"

Choose the team that you created. For example, “Payment” Team


Choose your relevant team

Start adding paths/packages and filenames to define the team by choosing the condition

  • Path (iOS)/Package (Android)
  • Filename

Add a path and a filename

For Path/Package, you have 2 conditions to choose from

  • Matches any of
  • Don't match any of



NOTE: Whenever you type the path/package you need to press Enter in order to lock it in

For Filename, you have 4 conditions to choose from

  • Equals any of
  • Doesn't equal any of
  • Contains any of
  • Doesn’t contain any of



NOTE: Whenever you type the filename you need to press Enter in order to lock it in

Manually Assign Crashes to Corresponding Teams

You can also assign the team manually from within the crash itself without defining it.

Go to crashes from the left sidebar of the dashboard and then click on the crash that does not have a team assigned to it


Crash is not assigned to a team

Navigate to the right sidebar “Actions” and change the Team to the corresponding team. For example, choosing the “Payments Team”


Assigning the crash to a team


Prioritizing crashes related to your team can be done through the Team filter at the top bar of the "Crashes" main page
Select your team from the dropdown list, you can even search by the team’s name. For example, “Payment” Team


Prioritize your crashes according to teams

As you can see below, you can prioritize the crashes related to your team only and get more granular with the options to filter. For example, Payment Team wants to focus on crashes seen in a certain app version. Also, you will be able to save those filters and you can access them from the right side of the filter bar.


Team ownership


If you’d like to get alerted as soon as you receive any crash related to your Team, you will be able to do that through our “Alerts and Rules” engine.

Go to “Alerts and Rules” and "Create" a new Alert


Start creating a rule

Use Case:
Regressing crash assigned to team “Payment”
Choose the condition (Regression) you want to be alerted to whenever it is assigned to “Payment” team


Regression detection with team ownership

For more details on the different use cases of Alerting, please refer to Alerts & Rules product guides.

Then, Forward it to your favorite tool (Ex: Slack, MS Teams, PagerDuty, … etc). Thus, Payment Team will be notified about this regression through that tool.


Forward the crash to your integrated tools

For more details on the different integrations that is supported, please refer to Instabug's Integrations Docs


Insights will help you get a closer look on the performance of each and every Team. To navigate to the insights you will need to go to the crashes on the left sidebar of the dashboard and go through the crashes insights at the top right corner


Crashes Insights

These are the insights you see before choosing a certain Team, now select the team whose performance you would like to monitor. For example, "Payment".


Crashes Insights, select your team

Now you can see all the related information to the “Payments Team” only. This will highlight the number of crashing sessions, the number of non-fatal, the number of OOMs or ANRs and a graph of occurrences over a certain period of time. All of this information will be related to the chosen team.