Summary
The ClayHR connector links ClayHR as an HRIS source so that Integrations can provision and keep users in sync inside KnowledgeCity. It is configured per account from the account's Integration Settings, where ClayHR appears as one of the supported HR/HCM integrations. Once connected, employee records flow from ClayHR into KnowledgeCity without manual data entry.
Introduction
Integrations connects KnowledgeCity to many external systems so that users, courses, and reporting flow automatically between platforms. The ClayHR connector is the HRIS integration that links a ClayHR source to a KnowledgeCity account, so employee records maintained in ClayHR drive the creation and upkeep of KnowledgeCity users.
This connector is set up by administrators who manage an account's integrations. It solves the problem of maintaining user lists by hand: new hires, role changes, and departures recorded in ClayHR can be reflected in KnowledgeCity through scheduled synchronization, keeping training records accurate and current.
Key Concepts
- ClayHR connector: an HRIS integration that connects ClayHR as a source of user data for a KnowledgeCity account. It is listed among the account's HR/HCM integrations alongside systems such as ADP, BambooHR, and UKG.
- Integration Settings: the account-level hub where every third-party integration is listed, configured, and shown with a configured or Not Configured status. ClayHR is configured here alongside other HR/HCM systems.
- Provisioning: creating KnowledgeCity user records from the ClayHR source so that employees exist in the platform without being added manually.
- Synchronization: the ongoing process that keeps KnowledgeCity users aligned with ClayHR, applying changes such as additions, updates, reactivations, and deactivations.
- Sync actions: the individual behaviors you enable to determine what a sync does (for example, adding new users, updating existing users, reactivating, or deactivating) based on each employee's state in ClayHR.
- Sync scheduler: the schedule that controls how often synchronization runs and when it begins, so provisioning stays current automatically.
- Audit Log: the record of integration configuration changes for the account, used to confirm what changed and to troubleshoot unexpected sync behavior.
Steps to Follow
Opening Integration Settings
You configure the ClayHR connector from the account's Integration Settings. Open it from Accounts Manager by choosing Integration Settings from the account's Actions (⋮) menu. This opens the account's edit page on the Integration Settings tab. The Settings view lists every available integration for the account.
Locating the ClayHR integration
In the list of integrations, find the ClayHR entry among the HR/HCM systems. Each integration is an expandable panel with a status badge showing whether it is already configured or Not Configured. Expand the ClayHR panel to begin configuration.
Entering the ClayHR connection settings
Enter the connection settings that identify and authenticate against your ClayHR source. Providing valid connection details is what establishes the link between KnowledgeCity and ClayHR so that user data can be read. Confirm these credentials with the customer before saving, since they control access to real user data.
Configuring provisioning and sync behavior
Set how KnowledgeCity users should be provisioned and kept in sync from ClayHR. As with the other HRIS connectors in Integrations, you enable user import and choose the sync actions that fit the account, for example creating new users that exist in ClayHR but not yet in KnowledgeCity, updating existing users, reactivating users, or deactivating employees who are no longer active in ClayHR. Enable only the actions the customer wants so that a sync makes exactly the changes intended.
Setting the synchronization schedule
Configure the schedule so synchronization runs automatically and provisioning stays current. You set how often the sync runs and when it starts, so ClayHR changes are picked up on a regular cadence rather than only on demand.
Saving and confirming the integration
Save the ClayHR settings within the panel. After saving, the integration's status reflects that it is configured. You can return to the panel later to adjust settings, temporarily disable, or re-enable the connector as needed.
Reviewing the Audit Log
Switch from Settings to the Audit Log view to see the history of integration changes for the account. Use it to confirm who changed the ClayHR configuration and when, and to investigate if a sync behaves unexpectedly.
Conclusion
The ClayHR connector brings ClayHR into KnowledgeCity as a governed HRIS source: you configure it once per account in Integration Settings, enable the provisioning and sync behavior the customer needs, set a schedule, and rely on the Audit Log to keep every change traceable. With it in place, KnowledgeCity user records stay aligned with ClayHR automatically.