The WithSecure™ Elements integration with Autotask PSA automatically forwards security activity from Elements into Autotask PSA as tickets. This lets MSPs manage WithSecure detections and notifications inside the same PSA tool they already use for service delivery, without manual ticket creation.
What this integration does
- Automated ticketing — WithSecure™ Elements creates tickets in Autotask PSA when there is relevant activity for a mapped customer.
- Per-customer routing — Tickets are routed to the correct Autotask PSA customer using the customer’s Autotask PSA reference ID.
- Queue selection — You choose the Autotask queue where WithSecure™ Elements tickets are created.
- Automated subscription provisioning — WithSecure™ products are synced to Autotask PSA, and subscriptions are provisioned automatically from a customer’s recurring service contract.
- Deep links back to Elements — Each ticket includes basic information about the Elements Security Center activity, along with a deep link to the full details in WithSecure.
- Native and multi-tenant — The integration is built into Elements, supports multiple customer tenants, and is configured entirely from the Elements Security Center.
Before you begin
You will need:
- An Autotask account with permissions to create API users.
- Access to the WithSecure™ Elements Security Center as a WithSecure Partner.
Step 1: Create an API user in Autotask
- Log in to the www.autotask.net management console.
- Click Admin in the navigation panel on the left-hand side.
- Under Admin categories, select Organization settings and users.
- Expand Resources/Users (HR) and click Resources/Users.
- From the New dropdown, select New API User.
- In the Add API user window:
- Fill in the mandatory general settings (names, email, etc.).
- Under Security Level, you can select API user (system) Can’t Read Costs — this is sufficient for the WithSecure™ Elements integration.
- In the Credentials section, click Generate key, then Generate secret.
- Copy the key and secret for use in the Elements Security Center.
- Under API Tracking Identifier, select the Integration vendor radio button.
- From the Integration vendor dropdown, select WithSecure.
- Click Save & Close at the top of the page.
To configure the integration you will need:
- API username/key
- API password/secret
Step 2: Configure the integration in Elements Security Center
In the WithSecure™ Elements Security Center, go to the Management > Integrations section and locate the Autotask PSA integration.
Click Configure on the Autotask component. The configuration dialog has four steps: Connection details, Data configuration, Result, and Test (optional). The configuration is saved on the Result step. Until then, go back to an earlier step with Previous or by clicking its name at the top of the dialog, and use Cancel or the X in the top-right corner to close the dialog without saving.
Connection details

- Set the API Username copied from the Autotask management console.
- Set the API Password copied from the Autotask management console.
- Click Connect to validate connectivity. When the connection succeeds, the dialog moves on to Data configuration.
When you open an integration that is already configured, the dialog shows that it is already configured and fills in the saved values. The API Password is masked; leave it as it is to keep the saved password. Click Connect to continue to the settings.
Data configuration

- Under Event types that create tickets, leave Endpoint BCD (Broad Context Detections on endpoints), Identity and Cloud BCD (Azure identity, Azure workload, and AWS workload incidents), and XM (Exposure Management Recommendations) selected, or clear a type that should not create tickets. All three are selected by default.
- Select the Queue where WithSecure™ Elements should create tickets. This is required while at least one event type is selected.
- Under BCD, set Minimum risk for tickets. It applies to both Endpoint BCD and Cloud BCD tickets. The default is High and above. Other choices are Info and above, Low and above, Medium and above, and Severe only. A threshold below Medium can create a large number of tickets. Waiting-for-customer, elevation, and risk-change updates can still create or update tickets.
- Under XM, set Minimum severity for tickets. The default is all severities (Info and above). Other choices are Warning and above and Critical only. Closed or accepted-risk recommendations never create tickets.
- Click Next.
If the queues cannot be loaded from Autotask PSA, the error is shown next to Queue. Next stays unavailable until a queue is selected or all event types are cleared.
Note: To enable automated WithSecure subscription provisioning, turn on Enable provisioning on the Data configuration step, and select the billing code where WithSecure services are sold. See Automated WithSecure subscription provisioning for how to use it.
Result
Review the settings and click Save. To change a setting first, click Previous to go back to Data configuration.
Test (optional)

After you save, you can create a test ticket to check that Autotask PSA accepts tickets from Elements with these settings. A test ticket shows problems such as a queue that cannot be used, a mandatory field that Elements does not fill in, or missing API permissions, before the first real ticket fails.
- Select the Company for the test ticket. The list shows the companies in your Autotask PSA; no company mapping is needed yet.
- Click Create test ticket.
- Check the result:
- Test ticket created shows a link to the ticket in Autotask PSA. This is a real ticket, so you can close or delete it in Autotask PSA.
- Test ticket could not be created shows the error message from Autotask PSA. Click Edit settings to go back to Data configuration, change the settings, click Next and Save again, and create a new test ticket.
- Click Close. Creating a test ticket is optional; the configuration is already saved.
Step 3: Enable ticketing for a customer
Map your Autotask PSA companies to the corresponding WithSecure™ Elements companies. Ticket creation starts automatically for each mapped company.
- In the company mapping view, match each Autotask PSA company to its WithSecure™ Elements company.
- Click Save Mappings.

Monitor tickets
Monitor the tickets you configured the integration to create in Autotask PSA. Each ticket contains basic information about the Elements Security Center activity and a deep link to the full details in WithSecure.
Automated WithSecure subscription provisioning
When Provisioning is enabled in the integration configuration, the integration provisions WithSecure™ subscriptions for your customers directly from recurring service contracts in Autotask PSA. You no longer need to create subscriptions manually in the WithSecure partner portal.
How it works
Once Provisioning is enabled in the integration configuration, the integration automatically syncs the available WithSecure™ products to the Autotask PSA tenant of the partner. These products become available in Autotask PSA so you can add them to a customer’s recurring service contract. When a recurring service contract that includes a WithSecure™ product is enabled for a customer, the integration provisions the corresponding subscription for that customer automatically.
Note: If the customer’s organization does not yet exist under your partner account in WithSecure, the integration creates it automatically as part of provisioning.
Prerequisites: required organization details
Before a subscription can be provisioned automatically, the organization in Autotask PSA must meet the following requirements:
- The organization must have Address, City, Zip Code, and Country defined.
- The organization must have at least one contact.
To add a contact, open the organization details and click Contacts from the navigation on the left-hand side, then add a new contact. The contact must have at least First Name, Last Name, and Email Address defined. This is the billing contact for the organization, and its details are sent to WithSecure as the account’s contact information.
Provision a subscription with a recurring service contract
To provision a WithSecure™ subscription for a customer, add a recurring service contract in Autotask PSA:
Open the organization’s details and click Edit.
Click the three-dot menu to find Contracts, and click it.
Click New, then select Recurring Service Contract.
Note: The organization must be of type Customer for it to be possible to add contracts to it.

- Set the Contract Name as you prefer. Set the Start Date to today or to a later date, and set the End date as you prefer.
- Click Next.

- Fill in the revenue and billing information fields as preferred.
- Click Next.
- Click Add Services/Bundles, find one or more WithSecure™ products, and select the products you want to provision for this customer.

- Click OK.

Set the Units for each WithSecure™ service. This works the same way as the quantity on a Halo PSA recurring invoice: the units determine the maximum number of seats available for the WithSecure™ subscription, so make sure they match the number of seats the customer needs. You can change this later from the contract if needed.
Note: You can set the Unit Price to whatever you want. This is the price the MSP bills their customer and has no effect on the WithSecure™ subscription itself.
Click Next.

- Fill in the exclusion contract fields as preferred.
- Click Next.

- Fill in the notification fields as preferred.
- Click Finish, then click Close.
If the organization’s billing contact details are correctly set, Elements will automatically provision the new organization/subscription within 15 minutes. To change the number of seats later, update the units on the recurring service contract.
Tip: To provision the subscription immediately instead of waiting, go to Management > Integrations in the Elements Security Center, open the active Autotask PSA integration, and click Sync sites.
Troubleshooting
If tickets are not created as expected, open the integration with Configure, click Connect, Next, and Save, and create a test ticket on the Test (optional) step. It shows the error message from Autotask PSA directly.
You can also review the integration logs in the Elements Security Center:
- Go to the Management > Integrations section.
- Open the active Autotask PSA integration.
- Select Logs to review recent integration activity and error details.
If a subscription is not provisioned after enabling a recurring service contract, review the integration logs to check for any missing organization details required for provisioning. After completing the missing details for the organization in Autotask PSA, you can manually trigger provisioning by going to Management > Integrations in the Elements Security Center, opening the active Autotask PSA integration, and clicking Sync sites. Then, review the integration logs again—please note that processing may take up to 1 minute.
Availability
This integration is available to WithSecure Partners in the Elements Security Center. It is not available for free trials or company-managed subscriptions. To access dedicated partner features, contact WithSecure.