Team Roles and Custom Resource Roles

Team Roles and Custom Resource Roles

In Rocketship, each Team can be assigned a default Autotask Role, which is automatically applied to every Resource (technician) within that Team when they are assigned to a ticket. However, Rocketship also allows for flexibility, as you can override this default Role on a Resource-by-Resource basis to meet specific needs.

Follow the steps below to assign a default Role to a Team and update Roles for individual Resources if needed.

Step 1: Log into the Rocketship Admin Portal

  1. Navigate to the Rocketship Admin Portal using your designated admin credentials.

Step 2: Access the Teams Page

  1. From the main navigation menu, go to Dispatch & Escalations.
  2. Click on Teams to open the Teams management page, where you can view and manage existing Teams and their associated Resources.

Step 3: Assign a Default Role to a Team

  1. Find the Team you want to configure and select it.
  2. Within the Team settings, locate the Default Role option.
  3. Select the Autotask Role that best fits the work your Team will handle. This Role will be assigned to every Resource in the Team as a default.

Note: The default Role is used as the initial Role when assigning Resources from this Team to tickets. You may later override this Role for individual Resources as necessary.

Step 4: Override the Default Role for an Individual Resource (Optional)

To set a different Role for specific Resources in the Team:

  1. On the Teams page, locate the Resource you want to update.
  2. Click on the Resource’s name to open their details.
  3. Under the Role field, select the desired Role from the dropdown list. Changing this from “BLANK” to a specific Role will override the Team’s default Role for this Resource only.

Tip: If you’re unsure which Role to assign, consult with your Service Manager or refer to your organization’s Role guidelines.


    • Related Articles

    • Autotask vs Custom Teams

      In Rocketship, our dispatch & escalation engine uses tiers composed of “Teams”. Understanding a Rocketship Team A Team is a group of users that all share an Autotask Role. For example, you may have a Team called “Level 1 Helpdesk” that has several ...

    • Why does the same Autotask Resource keep getting escalated tickets?

      If you have a ticket routing rule that manages an escalation and you find that the same team member keeps getting assigned escalated tickets, there are a two common reasons why: Other team members are blocked due to external appointments. No ...

    • Customizing Ticket Routing with Team Workflows

      Rocketship allows you to create custom workflows for specific teams to control how tickets behave, particularly when default behaviors might not work as expected. Example: Rocketing Forward When you forward a ticket using Rocketship, the Escalation ...

    • Mark a Resource as Unavailable for New Tickets

      In Rocketship, the Escalation engine will bypass any Resource that is set inactive. This can be useful in scenarios where a Resource is sick, on extended leave, etc. This can be done via the DispatchBoard by a service coordinator. Log in to Autotask ...

    • Stop a Resource from getting some tickets but not others

      There are times you want a resource to stop getting tickets in some situations while getting tickets in others, at the same time. For example, let’s say you have a tech who is going on a two-day vacation. You do not want them getting any helpdesk ...