As an MSP, managing Standard Operating Procedures (SOPs), guidelines, policies, and other critical information is essential. The daily task of storing, retrieving, and sharing numerous documents, passwords, and process maps can become cumbersome and inefficient if this information is scattered across different files and spreadsheets. This makes it difficult to locate specific items and collaborate effectively.
By integrating SuperOps.ai with an IT documentation platform like IT Glue, MSPs can centralize and streamline their knowledge management, improving organization and facilitating the sharing of both global and client-specific information.
How to configure IT glue with SuperOps
To integrate your IT Glue account with SuperOps, go Settings > Marketplace > IT Glue
You will need your IT Glue account URL and a newly created API key to integrate your IT Glue account with SuperOps.
Log into your IT Glue portal, obtain the API key,
Generating an API Key in IT Glue
Users with an Administrator role can navigate to Account > Settings.
Click on API Keys > Custom API Keys.
Enter a name for the key and click Generate API Key. You will not be able to view a key again after it has been generated.
For security, an optional Password Access setting is provided for each API key. Password values can be accessed from the Passwords API only if this setting is enabled.
To generate multiple API keys, click the plus sign icon.
Obtain the API key and enter it in SuperOps
Mapping clients from SuperOps to IT Glue
Note: Companies in IT Glue are referred to as clients in SuperOps
Client
When importing from IT Glue, you can select the organization in IT Glue by clicking on the drop-down list and mapping it against the client name in SuperOps.
Choose which SuperOps clients you would like to map to existing tenants in IT Glue using the drop-down list.
If the organization is not already available in IT Glue but exists as a client in SuperOps, you can create a new organization in IT Glue under their name from SuperOps. Just click on the "create" button next to the name.
Click the Ignore button on the right if you don’t want to map the client to IT Glue.
Note: Clients must be mapped and imported before mapping sites, requesters and platforms. Mapping clients is a mandatory action.
Mapping sites from SuperOps to IT Glue
a. Select the asset layout in IT Glue that corresponds to the site in SuperOps from the drop-down menu.
b. Select a key field. This is a mandatory step where you select a field as a unique identifier that will help us avoid duplication while syncing.
c. You can continue to map the fields in SuperOps to their counterparts in IT Glue for the selected asset layout.
d. Click on Save to start the sync at the site level and move on to requester-level field mapping. Only the mapped fields will be synced to IT Glue, and not all the fields in SuperOps.
Mapping requester from SuperOps to IT Glue
a. Select the asset layout in IT Glue that corresponds to the requester in SuperOps from the drop-down menu.
b. Select a key field. This is a mandatory step where you select a field as a unique identifier that will help us avoid duplication when importing.
c. You can continue to map the fields in SuperOps to their counterparts in IT Glue for the selected asset layout.
d. Click on Save to start the sync at the requester level and move on to asset-class level field mapping. Only the mapped fields will be synced to IT Glue, not all the fields in SuperOps.
Mapping assets classes from SuperOps to IT Glue
a. Select the asset layout in IT Glue that corresponds to the asset class in SuperOps from the drop-down menu.
b. Select a key field. This is a mandatory step where you select a field as a unique identifier that will help us avoid duplication when importing.
c. You can continue to map the fields in SuperOps to their counterparts in IT Glue for the selected asset layout.
d. Click on save to start the sync and complete your mapping process.
Note:
The "Configuration" option within the asset layout's key fields section is limited to a maximum of 13 entries.
Unlike the "Configuration" option, the "Device" option in the asset layout's key fields section allows for an unlimited number of entries.
How data syncing works
Any records, such as sites, requesters, and devices, created under a mapped client will be automatically synced to IT Glue.
If you edit an already mapped site, requester or device layout, all the information from the current layout will be moved to the newly mapped asset layout.
If you edit or change your existing field mappings, your changes will not be reflected in the existing layout. Only when a new document is created with that layout, will your changed field mappings be reflected.
You can view the last sync details on the Requester, Asset, and Site sections. If there are any synchronization failures, you can re-sync the data by clicking on the "Sync again" button as shown below.