Connect, map and verify
Open Settings > Integrations and review existing connections before adding another instance. Follow the provider’s setup workflow, verify its status, map its organizations to the intended companies and inspect synchronization/import results. A provider connection does not itself prove client visibility or enable every supported data area. Some controls save immediately; credential forms, mapping proposals and imports can have different persistence boundaries. Review the provider guide before continuing, particularly for consent, writeback, bulk operations and disconnection. Company mappings and user-role rules deserve review before automatic imports are enabled.Provider setup and compatibility
Follow the requirements in the individual guide. Providers differ in authentication, company mapping, synchronization, and supported actions. Some services connect per company or through another system, rather than through a direct integration card.Imports, synchronization, and maintenance
- Integrations FAQ
- Sync Schedules
- Import Users
- Import Companies
- Import Devices
- Clear and Resync Integrations
- Warranty Writeback to Autotask
- Warranty Writeback to IT Glue Configurations
- Warranty Writeback to Hudu and IT Glue Flexible Assets
Related setup guides
If a setup guide describes a control you cannot see, check its prerequisites and ask your MSP administrator or MSPortal support for help.FAQs
Does every provider have identical setup steps?
Does every provider have identical setup steps?
No. Authentication, company mapping, synchronization, feature availability and supported actions differ by provider.
Does a connected provider prove my clients can see the data?
Does a connected provider prove my clients can see the data?
No. Verify synchronization, mapping/import and Company role visibility separately.
Should I add another connection when an existing one has missing data?
Should I add another connection when an existing one has missing data?
Inspect the intended instance, permissions, scope and mapping first; another connection can create additional work or duplicate records.