Connect once. Every system resolves into one record.
The SIS, CRM, LMS, and warehouse each hold a shard of every student. Risely's agents read them in place, resolve the shards into one record, and write finished work back through the same doors.
reads enrollment
reading ▸
reads outreach
scoped
reads coursework
scoped
reads risk score
scoped
Identity fragments
Draft, waiting on a person
advising note + a seat hold on a late-start course that returns her to 12 credits before the aid census
▸Read enrollment from Banner · within scope
The systems a campus runs, worked in place.
One scoped connector per system. Nothing migrates and nothing cuts over.
Student information systems
reads · writes back
reads enrollments, holds, catalog · writes advising notes, flags, equivalencies
CRM
reads · writes back
reads applications, outreach · writes activities, status
LMS
reads only
reads submissions, logins, grades in progress
Canvas
Blackboard
Aid & student accounts
reads only
Data warehouse
reads only
reads named views only · models stay the institution's
Advancement
reads · writes back
reads gifts, contacts · writes contact reports
Career & engagement
reads only
System names describe read and write coverage. No partnership or endorsement is implied, and all marks belong to their respective owners. Additional systems connect through the same scoped-connector pattern.
One scope file your CIO can read, end to end.
A CIO grants a connector the way a registrar grants a role: named scopes, and a deny-by-default floor under all of it.
- Reads are bounded to the named tables and fields
- Writes wait for a named person's approval
- Every call lands on a ledger the team can export
The raw data stays the institution's to take.
You own it, and you can export all of it in open formats.
Every record, transcript, interaction, and outcome Risely's agents read or write is the institution's Customer Data. Export runs on the institution's schedule, including in full at termination. Leaving with everything brought in is a contractual right.
The resolved layer is licensed for the term.
The resolved knowledge graph, the schema mappings, and the models Risely builds across connected systems are licensed to the institution for the full term. This layer is why connect-once takes weeks instead of quarters.
What changes, and how it runs.
The record comes together where the data lives
The SIS stays the system of record. Staff keep the screens they know.
Finished work lands back in existing systems
Writes travel through the same doors, each one on a person's approval.
Turn on one connector at a time
Start read-only. Add writes when the CIO signs the scope.
The technical read
Connects read-only to the SIS, CRM, and LMS to start
A person approves every write to a system of record
Every call lands on an append-only, exportable ledger
Runs alongside existing systems. Nothing rips out.