Skip to main content
This guide walks you through connecting your Autotask PSA instance to MSPortal.ai. MSP staff set up the connection; company users do not administer it. You connect, check permissions, choose data and match records on the Autotask connection page. MSPortal can also import Autotask native survey results into the CSAT Dashboard, custom dashboard widgets, report blocks and CSV exports. The import is off by default, and you can keep collecting feedback through Autotask’s own surveys. See Import Autotask native CSAT for dashboards and reports.

Prerequisites

  • Admin access to Autotask, or API credentials (username and secret)
  • Admin access to MSPortal.ai with integration management permissions
  • The Ticket Settings permission in MSPortal if you will edit ticket defaults

Part 1: Configure Autotask PSA

Before connecting to MSPortal.ai, you need to create an API user and security role in Autotask. See Autotask’s API user setup and REST authentication guides for background.

Create Security Role

MSPortal signs in to Autotask as one API user. That user can do exactly what its security level allows, so start from Autotask’s API level, remove what MSPortal never uses, and keep what it does.

See the MSPortal security level (PDF)

Every section of the security level, as exported from Autotask. It grants more than MSPortal needs in a few areas, such as Inventory. Where it differs from the tables below, follow the tables.
1

Open Security Levels

  1. Sign in to Autotask as a user with HR admin rights
  2. Go to Admin > Account Settings & Users
  3. Expand Resources/Users (HR) and open Security Levels
2

Copy the API-only level

  1. Open the menu beside API User (system) (API-only) and select Copy. Autotask does not let you edit the system level itself.
  2. Rename the copy to MSPortal.
The copy starts with full access to everything, including deleting records. The next two steps trim it.
3

Remove what MSPortal never uses

MSPortal never deletes your Autotask records, so the biggest cut is Delete. Then switch off the areas it does not touch.
4

Keep what MSPortal uses

Check that the rows below are set as shown. A row marked Optional is needed only for the feature it names; the rest of the integration works without it. Where a row offers All or Mine, use All: Mine limits the API user to records assigned to it, so syncs miss records and updates to other people’s work fail.Autotask has renamed some labels between releases. Accounts may show as Organizations, and Configuration Items as Devices. Use whichever your screen shows.
Skip this section unless you sync contracts or invoices.
Skip this section unless you use Autotask projects in MSPortal. See Project management permissions for the project-specific checks.
Autotask keeps its setup lists behind these Admin areas. MSPortal reads them and changes nothing. Keep these ten and clear every other box in the section.
Resource Impersonation lets MSPortal add tickets, notes and time on behalf of a staff member, so Autotask shows that person as the author instead of the API user. Tick these boxes and leave every Delete box clear:Leave Accounts, Contact, Sales Orders, To-Dos, every Inventory row and the two time off boxes clear. Autotask also requires the security level of each staff member MSPortal acts for to allow impersonation.Contact Impersonation lets the API user add items on behalf of a client contact. Tick Add on Project Notes, Task Notes, Tickets, Ticket Notes and Attachments.When a staff member has no linked Autotask resource, MSPortal adds the note as the API user and puts their name in the note title.
Turning a feature on later? Set its rows here first, then select Re-check on the connection’s Permissions task in MSPortal.
5

Save the Role

Click Save & Close.
After you connect, the Permissions task in MSPortal checks this level from Autotask’s side: each area MSPortal reads, and whether the API user may create and update tickets. It names the setting to change for anything missing. See Permissions.

Create API User

1

Navigate to Users

  1. Go back to Account Settings & Users
  2. Select Resources/Users
  3. Click to add a new API user
2

Configure API User

Fill in the following details:The MSPortal connection form asks only for the API username and secret. It has no field for a custom tracking identifier, so set the integration vendor here. If Autotask rejects the tracking identifier, confirm the vendor association with your Autotask administrator.
3

Generate API Credentials

  1. Under Credentials, click Generate Key
  2. Click Generate Secret
  3. Important: Save the API username and secret immediately. The secret cannot be retrieved later.
Make sure to copy and save your API credentials before closing this dialog. The secret cannot be viewed again after creation.
4

Associate Lines of Business

Associate the appropriate lines of business with the API user, then click Save & Close.

Project management permissions

Skip this section unless you create or update Autotask projects from MSPortal. Syncing projects needs only the View row under Projects in Create Security Role. These settings go on the security level of the API user whose credentials are saved in MSPortal. A technician’s own security level does not give the integration any access.
1

Grant project access

In Autotask, go to Admin > Account Settings & Users > Resources/Users (HR) > Security Levels, edit the MSPortal level and open Projects. Autotask treats project tasks separately from service tickets, so Service Desk ticket access alone is not enough.Three things to check while you are there:
  • Line of Business. Autotask can hide projects and tasks by Line of Business even with View set to All, so include every Line of Business the integration should see.
  • Time entries. The API user must be allowed to enter time for the resource the time belongs to. Enable the billing field permissions if staff set billable or non-billable time.
  • No deletes. MSPortal never deletes a project, phase or task. Keep Delete at None on the Task Notes and Charges rows.
Baseline project tasks stay read-only, and Autotask’s rules for completed tasks and submitted or posted time still apply. See Autotask’s task access rules and time entry requirements.
2

Save and re-check

Save the security level. In MSPortal, go to Settings > Integrations, open the Autotask PSA connection, select Permissions and click Re-check.
3

Test on a project

A green Projects result only confirms MSPortal can read projects. Create a test project, edit a task and log time on it to confirm write access. If applying a template partly succeeds, check the records it created before you retry. An Autotask administrator can also inspect the API user’s effective access with Autotask’s entityInformation permissions.
In MSPortal, Autotask project task notes are time entry notes. Standalone project task notes and editable checklist items are not available for Autotask, and extra Autotask permissions will not turn them on. MSPortal-only projects and templates use MSPortal permissions only.

What MSPortal writes back to Autotask projects

Autotask projects are two-way for status and dates. You do not need to repeat these changes in Autotask:
  • Project status, from the portfolio Kanban or the project’s status.
  • Task status, from the project Board or ticket details.
  • Task owner, from the Resources board or the project Board.
  • Project, phase and task dates, from Reschedule, Edit dates, Projects > Dispatch, or ticket and phase details. An Autotask phase date change needs both a start date and an end date.
MSPortal writes to Autotask first and updates its own copy only after Autotask accepts the change. If Autotask rejects it, MSPortal shows an error and keeps the old value. Some changes stay in MSPortal. Rename phases in Autotask, because MSPortal does not send phase renames. Phase descriptions and notes, milestones, and project and onboarding templates stay in MSPortal. Onboarding task status syncs with Autotask, and an onboarding task due date changed in the portal is written to the linked Autotask task. Onboarding phase dates stay in MSPortal. See What writes back to your PSA.

Part 2: Connect Autotask in MSPortal

The Autotask connection page lists its setup tasks in the Setup guide: Connect, Permissions, Choose data, Import or match companies, Import or match users, Import devices, Configure tickets, Configure opportunities and Review. Import or match users, Import devices and Configure opportunities are optional. Select a task to return to it at any time.

Open the connection

1

Navigate to Integrations

In MSPortal.ai, go to Settings > Integrations.
2

Start Setup

Find Autotask PSA and select Connect. To continue an existing setup, open the existing Autotask PSA connection instead.

Connect

1

Enter API Credentials

Fill in the following fields:
2

Test the connection

Select Test connection and resolve any reported error. A successful test does not save the connection.
If the connection fails, verify your API username and secret are correct and that the API user has the MSPortal security role assigned.
3

Save and continue

Select Save and continue to create the connection, then continue to Permissions.

Permissions

MSPortal checks what your Autotask API user is allowed to read, and whether it may create and update tickets, and shows the result for each area. The check only reads your security level; it never creates or changes anything. If the check has not run yet, select Run check.
1

Review the results

Each area of data is listed as Granted, Not permitted or Could not verify.Areas marked Required must be granted before you can continue: Companies, Contacts and staff, Tickets, and Queues and statuses. Without these the integration cannot function.Other areas cover Ticket creation and updates, Configurations, Opportunities, Product catalog, Invoices, Contracts, Projects, Time entries, Service calls, Company notes, and Satisfaction feedback. You can continue and fix them later.If Ticket creation and updates is Not permitted, the API user can read tickets but its security level has Tickets Add or Edit set to No under Service Desk. Until you change it, tickets submitted in MSPortal are emailed to your fallback inbox, and the message says the PSA was unavailable.
2

Grant anything missing

Any area that is not permitted names the security level setting to change.Update the security level assigned to your API user, then come back and click Re-check. Every setting MSPortal uses is listed under Create Security Role.
Could not verify usually means Autotask was slow or unavailable, not that a permission is missing. Click Re-check before you change the security level.
3

Continue

Optional areas that are not granted keep their syncs switched off, and their switches in Choose data stay locked until you grant the permission and re-check.
These checks test read access only. A green result does not prove that ticket creation, comments, warranty updates or other writes will succeed.
If a permission is removed later, MSPortal switches off the affected sync and notifies your integration admins rather than retrying against an entity it can no longer read.

Choose data

Choose what data to sync from Autotask and set up automatic imports. Each switch and filter saves as you change it, so wait for the saved state before you leave. Switches sit side by side in two groups, Core data (companies, users and tickets) and Extended data. Turning on a dataset reveals its settings below that group; turning it off hides them without clearing saved choices. Each switch and selector has an (i) beside its name: hover over, tap or focus it to read what the setting does. Start the initial sync when it is offered. Options in later tasks can stay incomplete while it runs.
1

Choose datasets

A switch appears locked when the permission check found that your API user cannot read that data. Grant the permission named beside it in Autotask, then select Re-check in Permissions to unlock it.
2

Configure Contact Auto-Import

If you want contacts to be automatically imported when companies are added:
  1. Turn on Contact Auto-Import to automatically create user accounts for active contacts
  2. Select a Default Role for Imported Contacts (e.g., Viewer)
  3. Optionally, under Portal roles by contact type, select Add rule to give specific Autotask contact types other portal roles. Unmapped types use the default role.
We recommend choosing a role with minimal permissions (basic ticket creation only) if you plan to import all contacts.
To create portal users from your clients’ Microsoft 365 tenants instead, use an access rule with the action Import Microsoft 365 users (branch preview). See Set access rules.
3

Deactivate contacts with Microsoft 365 (optional)

Deactivate the contact when Microsoft 365 disables the person (preview; appears once MSPortal turns it on for your MSP): with Sync Users on, this switch sits below Contact Auto-Import. When Microsoft 365 blocks a client user’s sign-in and MSPortal disables that user, MSPortal marks each of their linked, active Autotask contacts inactive, so the person can no longer open or reply to tickets by email. When Microsoft 365 enables the person again, MSPortal reactivates exactly the contacts it deactivated.
  • It applies to people Microsoft 365 disables after you turn it on. People who are already disabled are left alone.
  • A contact that was already inactive is never recorded, so MSPortal never reactivates a contact you deactivated yourself.
  • Disabling someone yourself in MSPortal, or for any reason other than Microsoft 365, never changes their Autotask contact.
  • It needs a Microsoft 365 connection. Changes are sent after each Microsoft 365 users sync, and a failed change is retried up to five times.
  • Turning it off stops new deactivations. Contacts MSPortal already deactivated are still reactivated when Microsoft 365 enables the person.
  • The Recent contact changes button below the switch opens a dialog listing each contact MSPortal changed, and why one was left alone or failed. It refreshes while open. The button needs read access to company users. The API user must be allowed to edit Autotask contacts; a refusal shows there.
4

Configure Company Auto-Import and Filters

5

Configure Ticket Sync Scope

With Enable Ticket Sync on, define which tickets to sync:
6

Choose invoice visibility

With Enable Invoice Sync on, use Hide invoice statuses to hide closed, voided or other statuses from the Invoices page. Every invoice still syncs.
7

Configure Planner Auto-Import (Optional)

With Enable Opportunity Sync on, turn on Auto-import to Planner, below the Extended data switches, to create a planner item for each new Autotask opportunity. Use Minimum opportunity value and Opportunity types to auto-import to limit which ones come through. See Importing PSA Opportunities.
Synchronizing source records, linking them to companies and importing portal records are separate steps. Automatic company and contact imports can create portal records when matching source records arrive, so review filters and auto-import settings before you turn them on. Check errors and the actual sync result before you treat an empty list as the final dataset.
Autotask Choose data with Sync Companies, Sync Users and Enable Ticket Sync in one Core data row, company filters, company and contact auto-import and ticket sync scope pickers side by side, and the Extended data switches in a three-column grid, each with an (i) beside its name.

Branch preview: MSP staff in the Demo tenant.

On a phone, Autotask Choose data stacks the Core data switches and the filter pickers in one column, each with an (i) beside its name.

Branch preview: MSP staff in the Demo tenant.


Import or match companies

Open Import or match companies. Its first view, Import, includes unlinked records with or without suggestions; use Suggested to review proposed matches.
  • Select Import beside a source company to import it on its own.
  • Select Import companies to open the selection dialog. It loads unmatched records across pages for the current search. Use Select current page or Select all pages, review the names and selected count, then confirm. Existing portal companies with the same name are matched instead of duplicated.
  • To link a company that already exists under a different name, choose it in the row, or review and accept the suggested match. Review N suggested matches opens Accept suggested matches, which lists every suggestion at 70% confidence or more with those at 90% or more already selected. Lower the Auto-select by confidence slider, as far as 70%, to select weaker suggestions too, untick any pair you want to check yourself, then select Apply N Matches.
Accepted matches, removed matches and ignores save when applied. Opening the import dialog alone saves nothing. See Import companies for selection scope and retry guidance.
Accept suggested matches dialog over the Autotask Import or match companies task, with the Auto-select by confidence slider at 90%+, two 100% matches selected, Select All and Clear All, a search field and Apply 2 Matches

Branch preview: MSP staff in the Demo tenant. Suggestions at 90% or more start selected.


Import or match users (Optional)

Import or match at least one company first. You can leave other companies for later and return to import more users.
1

Select contacts

The workspace opens on Import, which includes suggested contacts too. Use Import beside a contact, or select contacts and choose Import selected. Use the header checkbox to select the current page, click it again to select all pages matching the current filters, and click again to clear the selection. Select all with email replaces the selection with contacts that have an email address across all pages matching the current filters. Large selections run in batches.
2

Review and confirm

In the review panel, choose the intended Company role and review the ready-to-import and skipped counts. Contacts without an email address are skipped; you can add an address before confirming. Correct invalid addresses or clear them to skip those contacts, and resolve duplicate addresses.
3

Check the result

Read the result and verify the saved users. To link an existing account instead, choose that user or accept a reviewed suggestion. Importing contacts does not invite them to the portal.
Client contacts are imported here. See Import users for selection scope and retry guidance.

Import devices (Optional)

Import Autotask configuration items as devices in MSPortal. Make sure Enable configuration item sync is on in Choose data, then open Import devices to map configuration item types to MSPortal device types and select the items to import. Confirm the intended company and device type before importing, then check the result in Devices.

Configure tickets

Set up how Autotask tickets behave in MSPortal. Each change saves straight away. Wait for the saved state and resolve any reported save failure before you leave.
1

Review new ticket defaults

New ticket defaults sets the PSA values used for new tickets created in the portal. These are the same defaults as Settings > Tickets, and editing them requires the Ticket Settings permission. It includes the Requester field, which records each submitter’s name in a ticket UDF. See Requester field.
2

Choose ticket statuses

Under Ticket statuses, select the Closed statuses that mean a ticket is closed. Status choices appear once queues are chosen in Choose data; missing choices can mean the first metadata sync has not finished. To set a status after a company user replies, see Set the status after a client comment.
3

Place statuses in resolution stages

Resolution stages drive the visual indicator of ticket progress. Place each Autotask status in the stage it belongs to. A status can sit in one stage only.
4

Set Autotask ticket defaults

5

Set a reply mailbox for emailed notes (Optional)

Emailing ticket notes is off until you turn it on in Settings > Tickets > General > Email ticket notes. To let staff and company users email a ticket note on this connection, also set Reply mailbox under Emailing contacts from notes. Enter the mailbox Autotask reads incoming email from. MSPortal sends the note from your sending domain with this mailbox as the reply address and the ticket number in the subject, so a reply is added to the ticket. Without it, the Email to field is not offered on this connection’s tickets.
6

Sync actions

See Clear and Resync Integrations before you use Clear & Resync.

Set the status after a client comment

Branch preview: These Autotask reply settings and screenshots describe an unreleased update. They are not yet verified in production.
Use this setting to move an Autotask ticket to a chosen status after a company user successfully saves a public note through MSPortal. MSP staff notes, internal notes and private notes do not trigger it. You need permission to manage integrations. The Autotask API user also needs Tickets Edit on its security level. Ticket creation and updates under Permissions shows whether it has that.
1

Open Configure tickets

Go to Settings > Integrations > Autotask PSA, open the connection you want to change, and select Configure tickets in its setup guide.
2

Choose a reply status

Under Ticket statuses > Status after a client comment, select an active status from this Autotask connection. Choose None to turn the automatic status update off.
3

Choose what happens on closed tickets

Replies on closed tickets becomes available after you select a reply status.Closed-ticket handling includes statuses marked closed in Autotask, your Closed statuses, and statuses placed in the Resolved resolution stage.
4

Wait for each change to save

Each selection saves immediately. Resolve any save error before leaving, then reload to confirm the saved choices. To stop automatic status changes later, select None.
The setting applies to this integration’s tickets. Company overrides are not supported in this release. MSPortal writes only the reply status for this step; it does not write the assigned technician, queue or priority. Autotask workflows may react separately to the status change.
Autotask Ticket statuses with In Progress selected after a client comment and Keep closed or resolved selected

Branch preview in MSPortal Demo: In Progress is an example reply status; closed or resolved tickets stay closed by default.

If the note saves but the status update fails, the portal and browser extension tell the company user that the note was saved and offer Retry status update when a retry is available. Retrying changes only the status and never posts another note. See When a reply changes the ticket status.

Configure opportunities (Optional)

Set default values for opportunities created from MSPortal. These settings only apply when Enable Opportunity Sync is on in Choose data. This task also controls how synced opportunities reach the Planner. Automatic Planner imports and their filters stay in Choose data.

Review

Open Review, resolve any required incomplete tasks, then select Finish setup. Each task saves its own changes, so finishing setup does not apply a separate batch of pending company or user imports. Syncs and imports keep running in the background; check their results separately.

Managing Your Integration

After setup, open the Autotask PSA connection from Settings > Integrations:
  • Overview and Sync activity: Check connection status, sync results and errors
  • Setup guide tasks: Change saved scope, matches and settings
  • Run sync: Request a manual sync of all data, or one data type
  • More actions > Rename: Label the connection
  • More actions > Disconnect…: Remove the stored credentials, company matches and synced data after confirmation. This cannot be undone. Revoke the API user’s credentials in Autotask separately.
To replace the API credentials, open Connect, enter the new username or secret, select Test connection, then select Save changes. Leave masked values unchanged to keep them. A test alone does not save replacement credentials, so confirm the saved connection before you revoke the old credential in Autotask.

Webhook Management

MSPortal provisions the Autotask webhooks for ticket changes, so no manual webhook setup is required in Autotask. A weekly check re-creates any webhook that has gone missing. If webhooks stop working, verify that your API user’s security role still allows creating webhooks, then contact MSPortal support.

Write warranty dates back to Autotask

Warranty writeback is an optional write to Autotask. Turn it on only when you want MSPortal’s warranty dates to update Autotask configuration items.
1

Turn on Warranty writeback

Open the Autotask PSA connection, select Choose data and turn on Warranty writeback. It does not need Enable configuration item sync. Devices are matched by RMM device UID, then by serial number in the mapped company.
2

Wait for the save

The switch saves as soon as you change it. Wait for the saved state before you leave.
See Warranty writeback to Autotask for the permissions, matching rules and troubleshooting.

Import Autotask native CSAT for dashboards and reports

This imports survey results already collected by Autotask’s built-in surveys. You do not need Simplesat or a new MSPortal survey. The import is off by default.
1

Grant survey rating rights

In Autotask, open Admin > Resources/Users > Security Levels and edit the level assigned to the API user. Under Other > Surveys, enable Can view Account Survey Ratings and Contact Survey Ratings and Can view Resource Survey Ratings.
2

Re-check permissions

In MSPortal, open the Autotask PSA connection, select Permissions, click Re-check and confirm Satisfaction feedback is granted.
3

Turn on the import

Open Choose data and turn on Import satisfaction ratings. There is no rating scale to choose, because Autotask survey questions rate 1 to 5. Each completed survey’s overall rating is rounded to a whole number on that scale.
4

Start the first import

Wait for the switch to save, then start the sync when it is offered. Later imports run hourly. A saved setting does not mean every response has arrived.
5

Check company links

Make sure the surveyed companies are linked to portal companies and their tickets have synced. A result whose company is not linked will not appear in company-scoped CSAT results until a later sync can resolve it. Technician attribution uses the assigned resource on the synced ticket.
6

Grant read access

Give intended readers Surveys > Read > CSAT in their role. Building dashboards and reports also needs the matching permissions.
Only completed surveys are imported. Surveys that were sent but not answered, and surveys completed without answering any rated question, are not counted. Autotask does not provide free-text survey answers to integrations, so imported responses carry ratings only.

Present the imported results

These CSAT views can include other connected feedback sources alongside Autotask. Check the company selection, dates and survey filter before you read a total as Autotask-only.

If Autotask CSAT is missing

Connecting Autotask does not turn on the import by itself. Check that Import satisfaction ratings is saved, Satisfaction feedback is granted, the companies are linked, the tickets have synced and the reader has the CSAT permission. If the Import satisfaction ratings switch does not appear at all, contact MSPortal support.

Additional Configuration

After completing setup, you may want to configure additional settings:

Configure Ticket Settings

Navigate to Settings > Tickets to:
  1. Set the Delivery Method to PSA
  2. Ensure Autotask is selected as your PSA provider
  3. Configure ticket categories and map them to Autotask ticket types
  4. Set Ticket Defaults for tickets created from compliance tasks or automation
Ticket defaults are also used as the starting point for new ticket templates, making template creation faster.

Configure Display Groups

Display groups control which ticket fields users can see based on their role.
  1. Navigate to Settings > Tickets
  2. Scroll to Display Groups and click Create Group
  3. Configure:
    • Name for the display group
    • Select Autotask as the PSA provider
    • Assign roles that should use this display group
    • Select which fields are visible
Only grant access to information users need for their role. Follow the principle of least privilege.

Configure Allowed Statuses

Set which ticket statuses users can select when updating tickets:
  1. Navigate to Settings > Tickets
  2. Configure status permissions for each display group
We recommend preventing users from closing tickets directly. Instead, use a “Ready for Review” status to ensure tickets are reviewed before closure.

Devices from Autotask configuration items

MSPortal treats an RMM, MDM or network tool as the source of truth for a device. When an RMM is connected, a Autotask configuration item keeps or creates a device only when its type has Auto-import on and is not ignored in Import Devices. Configuration items of other types add their details to devices your RMM reports.
  • Configuration items removed in Autotask. Once a day MSPortal checks the full list of active configuration items in Autotask. A configuration item that is deleted or made inactive is removed from staging three days after Autotask stops listing it, and stays if it comes back in the meantime.
  • What happens to the device. When the configuration item leaves staging, its device moves to another integration that still reports it, such as your RMM. A device nothing else reports is removed. In a tenant with an RMM, an IT Glue or other PSA record keeps the device only when its type has Auto-import on.
Only companies still mapped to this connection are affected. Unmapping a company or excluding a type stops syncing those records and keeps their devices. Archived devices are never removed.

Troubleshooting

Frequently asked questions

Yes. Select Save and continue after a successful test to create a connection, or Save changes to save replacement credentials on an existing connection.
Yes, for tickets. Ticket creation and updates reads whether the API user may add and edit tickets, without creating one. Other writes, such as projects, time entries and warranty dates, are not checked: confirm those with a real action.
It writes back. Project status, task status, task owners, and project, phase and task dates you change in MSPortal are written to Autotask, so you do not update them again there. Phase renames, milestones and onboarding portal dates stay in MSPortal. See What MSPortal writes back to Autotask projects.
No. Check the background sync result and verify company, user and device imports separately.
Discovery and import are separate. Review user matches, company links and the permissions assigned to portal users; invitation is a separate workflow.
Yes. Turn on Import satisfaction ratings in the Autotask connection’s Choose data task and grant the API user’s security level the survey rating rights. Completed survey results are available in the CSAT Dashboard, custom dashboard CSAT widgets, report blocks and CSV exports, subject to company mapping and role access. You can keep using Autotask’s own surveys; Simplesat is not required.
A retest only verifies access. Select Save changes after testing the replacement credentials, then confirm the saved connection before revoking the old credential.