AutoTask

The Corma and Autotask integration keeps your PSA licenses and security levels in line with the technicians and staff who run your business. Its vendor describes Autotask as an AI-powered professional services automation (PSA) tool purpose-built for service providers. Autotask merged with Datto in 2017, and Kaseya completed its acquisition of Datto on June 23, 2022. Autotask bills the higher of a committed minimum or the month-end license count, so a user left active can keep costing money.

Key takeaways

• Every Autotask security level is based on one of nine license types, from Administrator to Dashboard User, and the API User license type is free.
• Since December 2025, Autotask bills the higher of the committed minimum quantity of licenses or the license count on the last day of the previous month.
• Autotask users cannot be deleted, only inactivated, and an inactive user cannot log in while their history stays available.
• Autotask requires every user to use either single sign-on or two-factor authentication, and its own SSO uses OpenID Connect.

What does Autotask need before a user is inactivated?

Autotask's checklist for departing users lists manual steps before inactivation, including reassigning scheduled LiveReports, which otherwise stop running. Autotask ships system security levels that cannot be edited or deleted, and recommends copying them into custom security levels. Configured recipients get security event emails when a user is created, activated or deactivated, or when a security level changes.

API users follow their own rules. Autotask API users are free accounts with no access to the Autotask UI, and the admin who creates one generates a 15-digit key and a 25-digit secret that is not shown again in edit mode. Every API call except getZoneInfo() needs a tracking identifier, which cannot be edited or deleted once saved. Admins can exempt API-only users from password expiration, and the Web Services API does not support SSO.

How Corma governs Autotask

• Licenses counted before month end: Autotask licenses sit in SaaS subscription management, so leavers can be inactivated before the last day of the month, when Autotask counts licenses.
• Leavers with a checklist: a leaver workflow in the IT Workflow Builder walks an admin through Autotask's steps, such as reassigning scheduled LiveReports, before inactivating the person.
• Security levels under review: users on Administrator license types and custom security levels with admin access to Resources/Users (HR) go into automated access reviews.
• API users with an owner: API users and their keys are non-human identities, so each one needs a named owner, starting with those exempt from password expiration.

Frequently asked questions

Does Autotask support SSO and SCIM?

Autotask's own SSO uses OpenID Connect, with setup guides for Auth0, Datto SSO, Microsoft Azure AD and Entra ID, and Okta, and users must exist before SSO is configured. SAML 2.0 comes through KaseyaOne, whose Automatic User Provisioning, when turned on, creates an Autotask account for anyone granted Autotask access in KaseyaOne, and extra charges may apply. Autotask documents no SCIM provisioning. Read what single sign-on covers.

How does Corma connect to Autotask?

Through the Autotask REST API where it fits, which can query and update users but not create or delete them, or through Corma's browser-based agents in Autotask's admin settings. See also how Corma covers service desk tools such as Freshservice.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want to know which Autotask licenses are still billed for people who left? Book a Corma demo.