Configure Connection
Vector Solutions SafeSchools guide
Enable the API service, generate client credentials, and collect SafeSchools data to verify the NIM connection.
Before you beginDirect link to Before you begin
The API requires a subscription to enable API functionality. Contact the Vector Solutions team to arrange a subscription. Follow the vendor's GraphQL API setup documentation and ensure you can access the LMS Admin menu.
NIM requires Hostname, Client ID, and Client Secret.
Verify the connection with a collection
Test Connection always reports success for this connector. Collect the system to verify credentials and API access.
Add the API clientDirect link to Add the API client
- In the LMS, open Admin > Settings.
- Select Integrations, then Add Client.
- Copy the displayed Client ID and Client Secret and store them securely. These values are displayed only at this point, so copy them before closing the popup.
- Select Done to close the popup.
- Confirm the API hostname and access required for your process with Vector Solutions.
Enter the connection settingsDirect link to Enter the connection settings
- In NIM Studio, open Systems > Overview and add a Vector Solutions SafeSchools system, or select the existing system.
- Open Connection, enter the following settings, and save.
| NIM setting | Value |
|---|---|
| Hostname | The SafeSchools API host for your environment, using the format expected by the Connection screen. |
| Client ID | The ID generated when adding the API client in the LMS. |
| Client Secret | The secret displayed with that Client ID. |
Verify access by collecting dataDirect link to Verify access by collecting data
- Collect the SafeSchools system in NIM. A successful Test Connection result alone does not verify access.
- Confirm that the collection completes and inspect the people, jobs, positions, locations, and course information needed by your process.
- If collection fails, verify the API subscription, Hostname, Client ID, Client Secret, network access, and API permissions with Vector Solutions.
- Validate identity matching and field mappings. Test intended people, job, position, and location changes with safe records before enabling automation.
A successful collection verifies the selected reads. Validate write permissions separately.
Step 1 of 3