Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connectwise Automate Feedback & Questions.

Please use this space to create a new post for issues you are having if you do not see a post already created for your issue.  We will also welcome feature functionality feedback, enhancement requests, and general questions.



This thread was automatically locked due to age.
  • Just wanted to give an update on this. I think this should be something that is added to the instructions. 

    The fix was after installing the plugin through Automate, you have to go assign the Sophos Plugin user class from within Automate. 

    There are two there. "Sophos Plugin Admin" and "Sophos Plugin User". I gave myself both, but I would think you have to have the admin one to configure the plugin.

  • Thank you very much for this William! This resolved the issue for me and got everything working. 

    Funny enough, 2 days later Sophos came back with the same suggested fix. 

  • To all whom struggled to interpret the above solution:

    You will need to go to CW Automate's User Manager, select your user, then under Permissions and User Classes, right-click and add the Sophos Plugin User and Sophos Plugin Admin entries into that list. Once added and saved, please retry the API credentials in the Sophos Central Plugin settings, and you should remain connected going forward. See the image attached for more information.

  • API Credentials will connect then immediately disconnect. 

    I've tried creating new credentials and the same thing happens. 

  • Hi Brock, 

    Please see my note just above your post. I have included a screenshot of what is needed to be added to your own user permissions to allow our plugin to function correctly, the Sophos Plugin Admin and Sophos Plugin Admin. 

    Cheers, 

    Skylar Melo

  • I tried to take my post down, because I noticed that right after I posted. Thank you though!

  • I'm assigning tenants to all our clients, but there are a fair number of mismatches between Automate and Central. For instance, a single client in Automate may have multiple locations, and each location has its own tenant in Central. I am unable to assign multiple tenants to a single client. It seems I am also unable to assign clients to tenants.

    Is there a way to assign tenants to locations in Automate, rather than clients? Any other solution that I'm not seeing? Thank you for the help.

  • Hi Eric, We explicitly disallowed the functionality to assign clients across multiple tenants as it opens up the possibility for issues to occur with miss matches of installers across tenants that are not related.  This could then cause regulatory issues with policies such as GDPR.

  • I think I should clarify on behalf of Eric: The issue is that our relationships with our customers are at the SITE level, not the over-arching COMPANY level. All of the Connectwise stack is built this way (or at least is built to have this option). If we have a customer with two sites, they have an agreement for each individual site - those sites are then given different tenants in Sophos. (This is actually more compliant with the needs of GDPR, even though that's not a concern for us.)

    Bottom line: the tenant link in Automate should be moved to the SITE, down from the COMPANY. We modified the 'old' plugin ourselves so that if an installation link existed at the site level, it overrode the one at the company level - so if it was a single site customer, we just applied the install link to the company, but for multisite companies with separate agreements per site, we specified them at the site.

    At present, we cannot link/sync our multisite customers.

  • To further clarify the above, you will need to right-click the white space under User Classes in my screenshot above and then select "Sophos Plugin User/Admin" from the list. Add both then Save, relaunch Connectwise Control Center, and you should be all good.