Every ticket, project task, and appointment in Autotask PSA eventually lands with a resource. That makes resource setup one of the most important configuration jobs an MSP can get right. When resources are set up correctly, the right people have the right permissions, schedules are accurate, and work flows to the right queues. It's also the foundation that makes helpdesk automation work, because automation can only route tickets as well as your resource data allows.
In this guide, we'll cover who needs to be a resource in Autotask, how to set one up, how to handle team changes, and how clean resource data improves MSP help desk efficiency and dispatch.
In Autotask, a resource is anyone on your team who will be assigned or scheduled work. That includes employees, consultants, and contractors who work on project tasks, tickets, or sales to-dos.
It also includes people who don't necessarily do the hands-on work but are involved in managing it. Anyone who needs to report on, approve and post, or manage those activities should be set up as a resource too. For most MSPs, that means technicians, dispatchers, service managers, project managers, account managers, and leadership.
Resources are created by users with the right HR security level permissions, through the Admin navigation menu. A complete resource setup covers several areas:
It's tempting to fill in the basics and move on, especially when you're onboarding a new technician in a hurry. But each of these areas affects how work gets assigned, scheduled, and reported on later, so it's worth taking the time to complete them all.
Autotask generates a permanent, unique resource ID for every resource. To protect data integrity, resources can't be deleted. All the tickets, time entries, and history tied to that person stay intact.
When someone leaves your team or no longer needs Autotask access, you deactivate the resource instead. This keeps your historical reporting accurate while removing them from active assignment.
Tip: Make deactivation part of your offboarding checklist. When a departed technician is still active, they can still appear as an option for assignments and scheduling, which leads to tickets going to someone who isn't there.
Resource configuration might look like an admin task, but it has a direct impact on day-to-day service delivery. Incomplete or outdated resource data is a quiet source of MSP help desk chaos:
Clean resource data keeps your service desk predictable, and it's essential for any kind of MSP workflow automation.
Automated dispatch is only as smart as the data behind it. To get the right ticket to the right person at the right time, an automation tool needs to know who's active, which queues they cover, and when they're available. That's exactly what your Autotask resource setup provides.
Rocketship works directly with Autotask PSA, using that foundation to automate the ticket lifecycle:
Together, accurate resources in Autotask and AI Autotask automation from Rocketship turn your service desk from reactive to predictable.
Use this checklist when onboarding a new team member, or to audit your existing resources:
Review this list at least quarterly, and any time your team structure changes.
Getting resources right in Autotask PSA keeps permissions secure, schedules accurate, and queues covered. It also sets the stage for helpdesk automation that saves your team time on every ticket.
Want to keep learning? Check out these resources:
Need help auditing your resource setup? Our Autotask Consulting team can help. Or schedule a demo to see how Rocketship automates ticket assignment, scheduling, and escalations in Autotask. You can also try Rocketship risk-free with our 30-day money-back guarantee.