Map Connected-System Records to Scopable Clients

Mappings tell Scopable which external organization or environment belongs to each Scopable client. A correct mapping lets connected data sync into the intended client. An incorrect mapping can place provider data in the wrong client record.

Open Integrations > Mappings. The page shows Scopable clients alongside records discovered from connected systems.

Before you map records

Create the Scopable clients you need before mapping. Enrichment sources such as Liongard do not create clients for you.

Make sure the connected system has completed its initial connection or discovery step. If there are no available external records, return to the integration setup and test the connection or run its first sync.

Refresh matches

Select Refresh matches to request current external records from sources that support discovery and run Scopable's matching process.

Refreshing can produce three common states:

• Confirmed: a user has confirmed the relationship.
• Suggested: Scopable found a likely match that needs review.
• Unmatched: no active relationship exists.

Scopable only auto-links exact, unambiguous matches. Similar names alone are not enough when more than one client could match.

Review suggested matches

1. Use the search field to find a Scopable client or external organization.
2. Turn on Needs attention only to focus on unresolved rows.
3. Compare the client name with the external organization, provider identifier, and available context.
4. Confirm the suggestion only when the records represent the same client.

If you are uncertain, leave the record unmatched and verify it in the provider. An unmapped record skips sync. A wrong mapping can mix one client's data into another client's record.

Set or change a mapping

Open the source cell for the Scopable client and choose the correct external record. Confirm the selection when prompted.

An active external record can map to only one Scopable client for that source. If the record is already mapped elsewhere, resolve that relationship before assigning it again.

Some providers expose parent and child organizations. Review any conflict or child-record notice before confirming a relationship. Do not assume that a shared or similar provider name identifies the same client.

Clear an incorrect mapping

Open the mapped cell and clear the relationship. Clearing stops future sync through that mapping. It does not change the external provider or automatically delete data that was synced previously.

After correcting the mapping, run the relevant integration sync and verify the destination client.

View-only access

Users without permission to manage integration mappings can review the page but cannot confirm, change, or clear relationships. Ask an administrator or integration manager to make the change.

Troubleshooting

There are no Scopable clients to map

Create the client records first, then return to Mappings and refresh matches.

A connected source does not appear

Confirm that the integration is connected and that its discovery or initial sync completed. Some sources do not provide mapping records until a successful provider request has run.

A suggested match is wrong

Do not confirm it. Select the correct external record manually, or leave the row unmatched until you can verify the provider identity.

An external record is already mapped

Find its current Scopable client and review the relationship. Clear the incorrect mapping before assigning the record to another client.

Data still appears under the wrong client

Correct the mapping and run the relevant sync. Then review the integration's data-retention behavior. Clearing a mapping prevents future mapped sync but may not remove previously imported records automatically.