The only AD provisioning tool
built for Slate
OnboardConnect speaks Slate natively — pulling student data via Query Web Services and Source Format API. No custom development. No API credentials. No middleware.
The Integration
How Slate + OnboardConnect connect
Three steps. No Slate API credentials. No custom Slate development. Works with every Slate license.
Slate sends student data to OnboardConnect on schedule
Use Slate's built-in Scheduled Export or Query Web Services to send student data to OnboardConnect. No Slate API developer credentials or custom development required.
OnboardConnect reads the file and processes each row
Our engine polls for new files, parses each row against your provisioning rules, evaluates conditions, and determines the correct AD action — create, update, disable, move, or reset.
AD accounts are created, updated, or disabled automatically
The result executes against your Active Directory — on-premise or Azure AD — with zero manual intervention. Every action is logged, and results are written back to Slate via the Source Format API so your records stay in sync automatically.
Slate File Types
Every Slate Connection, handled
OnboardConnect maps each Slate export file to the correct AD action automatically.
| File | Trigger | AD Action |
|---|---|---|
active_students.csv | Slate enrollment confirmed | Create account (or re-enable if previously disabled) |
withdrew_students.csv | Student withdrawal recorded in Slate | Disable AD account, move to withdrawal OU |
graduated_students.csv | Commencement / graduation status in Slate | Disable active account + move to graduated OU |
password_reset.csv | IT-initiated reset request logged in Slate | Trigger password reset via configured method, log outcome |
File names shown are examples. OnboardConnect accepts any filename — you map it to the correct action in the connection configuration.
Requirements
What you need from Slate
OnboardConnect works with every Slate license. There are no custom Slate fields, no Slate API keys, and no Slate professional services engagement required.
OnboardConnect supports Query Web Services and Source Format API — working with the Slate features already available in your instance.
The short list
-
A Slate connection
Query Web Services or Source Format API — available in every Slate license tier.
-
Slate access
No Slate API developer credentials required. OnboardConnect works with standard Slate features your team already uses.
-
5 student data fields
Five fields are all that's required for basic provisioning — first name, last name, institutional ID, email, and enrollment status. Additional fields (program, campus, department) can be included to power conditional OU and group assignment rules.
Write-Back
Results flow back to Slate too
After provisioning, OnboardConnect writes results back to Slate via the Source Format API — keeping your Slate records current without any manual reconciliation.
This closes the loop: Slate owns enrollment data, OnboardConnect owns identity execution, and the two stay in sync automatically.
Results file fields
- Student institutional ID (matches Slate record)
- Provisioning action taken (created / updated / disabled / skipped)
- AD username assigned
- AD environment targeted
- Timestamp of action
- Outcome status (success / error)
- Error detail (if applicable)
Get Started
Ready to connect Slate to your AD?
We'll walk through your Slate export structure and show you how OnboardConnect maps to your exact configuration.
90-day free trial — no credit card required.