Sync your ConnectWise PSA contacts and update license & user based billing
ConnectActive helps keep your contacts up to date for easier billing & security
ConnectActive syncs your ConnectWise PSA contacts and updates license & user based billing
Discover the power of the Nilear Operations Suite (NilearOS), a comprehensive suite of nine products seamlessly integrated with ConnectWise PSA. Nilear is your essential third-party integration tool, with over 15 years of expertise to elevate your CW experience.
Try My User List to allow your customers to access their ConnectActive reports.
About ConnectActive
Sync Sources:
Azure AD Users, Groups & Licenses
Office 365 Users, Groups & Licenses
Active Directory Users, Groups & OUs
Google Workspaces
Populates ConnectWise PSA with:
Contact Name, Email & Phone Numbers
Contact Creation & Deactivation
Site Mapping
Custom Field Checkboxes
Agreement Addition Count
*Also includes the list of people covered on each invoice
*Prorating Options Available
About ConnectActive
Sync Sources:
- Azure AD Users, Groups & Licenses
- Office 365 Users, Groups & Licenses
- Active Directory Users, Groups & OUs
Google Workspaces
Populates ConnectWise PSA with:
- Contact Name, Email & Phone Numbers
- Contact Creation & Deactivation
- Site Mapping
- Custom Field Checkboxes
- Agreement Addition Count
*Also includes the list of people covered on each invoice
*Prorating Options Available
When to Apply ConnectActive
1.
When ConnectWise PSA’s Email Connector generates a new ticket, the MSP needs the Email Connector to resolve the incoming email address to an existing Contact successfully.
2.
When the Help Desk receives an incoming call, the MSP staff should be able to create a ticket based on the caller and their existing Contact information in ConnectWise PSA.
3.
When an MSP client has a user removed from the Active Directory, Azure AD, and/or Office 365, the Contact’s Portal Access and PSA Contact should be deactivated to maintain customer security.
4.
MSPs working with a third-party NOC, security subscription or other integrated service should have all their Contacts up to date to ensure seamless integration.
5.
When sending an employee on an on-site, the Contact associated with the ticket should have the correct Site information assigned.
6.
User-based Agreement Additions should include the actual list of users included under the Agreement Additions.
7.
Office 365 license counts should be updated in real-time, reliably, and without human intervention.
8.
User-based Agreement Additions should be prorated for additions to protect the MSP’s own costs and refunded for removals to protect their clients’ costs.
When to Apply ConnectActive
1.
When ConnectWise PSA’s Email Connector generates a new ticket, the MSP needs the Email Connector to resolve the incoming email address to an existing Contact successfully.
2.
When the Help Desk receives an incoming call, the MSP staff should be able to create a ticket based on the caller and their existing Contact information in ConnectWise PSA.
3.
When an MSP client has a user removed from the Active Directory, Azure AD, and/or Office 365, the Contact’s Portal Access and PSA Contact should be deactivated to maintain customer security.
4.
MSPs working with a third-party NOC, security subscription or other integrated service should have all their Contacts up to date to ensure seamless integration.
5.
When sending an employee on an on-site, the Contact associated with the ticket should have the correct Site information assigned.
6.
User-based Agreement Additions should include the actual list of users included under the Agreement Additions.
7.
Office 365 license counts should be updated in real-time, reliably, and without human intervention.
8.
User-based Agreement Additions should be prorated for additions to protect the MSP’s own costs and refunded for removals to protect their clients’ costs.
More Information
User Based Agreement Additions
Map the active users of a company to the User-based Agreement Addition in ConnectWise Manage.
License Mapped Additions
Map an Office 365 License to an Agreement Addition and include the list of users licensed.
Tiered Pricing
Use Tiered Pricing on Agreement Additions for different rates based on user count.
Agreement Addition Prorating
Learn how ConnectActive manages Prorating for your customer’s invoices.
Group Mapped Additions
Need to map different Groups in AD or Azure AD to different ConnectWise Manage Agreement Additions?
Group Filtering
Use Group Filtering to limit which Users are sync’d with ConnectWise Manage.
Single Tenant / Multiple Companies
Have a single Azure AD / 365 Tenant containing multiple companies?
Licenses w/ OU Filter
Map an Office 365 License to an Agreement Addition and filter the list of users licensed based on selected OUs.
Troubleshooting Powershell
Troubleshooting steps for issues encountered when scheduling the PowerShell Script for ConnectActive
ConnectActive Security
For ConnectActive sync purposes, ConnectActive does not store company names, contact names, contact email addresses, domain names or any other sensitive customer data in its database. Instead, ConnectActive stores only ConnectWise PSA’s primary keys for your companies and contacts and uses one-way hashes for usernames and email addresses in order to maintain a sync.
The actual list of companies and contacts are rendered in memory or via webpage when performing a sync by querying the customer’s ConnectWise PSA API and Active Directory/Office 365 environment.
Access to the customer’s Office 365 / Azure AD is granted by an Administrative delegate and can be removed using the tenant’s Office 365 / Azure AD portal. Active Directory integration can be terminated by removing the Scheduled Task for the Powershell Script.
Any MSP information stored by Nilear is protected and available for the MSP’s usage only. Any MSP information can be permanently removed after account termination upon request.
ConnectActive/Nilear requires MFA for website access and the physical servers are housed at a third-party facility with ISO 27001, SOC 1 Type II & SOC 2 Type II, HIPAA/HITECH, GLBA, PCI DSS v3.2.1, NIST SP 800-53, SOC 2 + HITRUST, ITAR, and Privacy Shield compliance.
ConnectActive Security
For ConnectActive sync purposes, ConnectActive does not store company names, contact names, contact email addresses, domain names or any other sensitive customer data in its database. Instead, ConnectActive stores only ConnectWise PSA’s primary keys for your companies and contacts and uses one-way hashes for usernames and email addresses in order to maintain a sync.
The actual list of companies and contacts are rendered in memory or via webpage when performing a sync by querying the customer’s ConnectWise PSA API and Active Directory/Office 365 environment.
Access to the customer’s Office 365 / Azure AD is granted by an Administrative delegate and can be removed using the tenant’s Office 365 / Azure AD portal. Active Directory integration can be terminated by removing the Scheduled Task for the Powershell Script.
Any MSP information stored by Nilear is protected and available for the MSP’s usage only. Any MSP information can be permanently removed after account termination upon request.
ConnectActive/Nilear requires MFA for website access and the physical servers are housed at a third-party facility with ISO 27001, SOC 1 Type II & SOC 2 Type II, HIPAA/HITECH, GLBA, PCI DSS v3.2.1, NIST SP 800-53, SOC 2 + HITRUST, ITAR, and Privacy Shield compliance.