Risely Fabric
The same person shows up in ten systems. Fabric makes them one record.
A student, a donor, a course, and a gift each live in a different system under a different ID, and the systems do not talk. Fabric reads them where they are and builds one clean record for each. Every system already in place keeps running.
SIS
CRM
LMS
Financial aid
Advancement
Career & success
The Fabric resolver
It matches every source to the same person and settles them into one clean record. Every write goes back through your SIS.
Your data platform is the foundation
Fabric reads your warehouse alongside the source systems, and writes the resolved record back, so the models and dashboards you already run get cleaner data too.
Five IDs walk in. One person walks out.
Entity resolution is the quiet hard part. Fabric matches the applicant in the CRM to the student in the SIS to the aid case to the LMS login to the billing account, so every office stops working a fragment.
Fabric matches all five to the same person.
Five IDs resolve to one person, and every office reads the same record.
What "one record" actually holds.
Fabric does not copy the source databases. The canonical record is a clean, typed shape: identity, academics, money, engagement, and the career and giving arc, each field mapped from the system that owns it.
Identity
Legal and preferred name, every source-system ID, and contact and consent, in one place.
Academics
Program and catalog year, courses, grades, credits, degree progress, and any holds.
Money
Aid package and disbursements, balance and payment plans, scholarships, and sponsors.
Engagement
Every interaction across every office, plus LMS activity, events, clubs, and appointments.
Career & giving
Outcomes and first destination, the alumni relationship, and gifts, pledges, and funds.
Courses and gifts get their own records too, each linked to every person they touch. That linking is what the Agent Graph is made of.
How a connector works: connect, map, sync.
Setup is a mapping exercise, once per source. After that, a change in the source becomes a change on the record, and every write an agent makes goes back through the system that owns the data, on a person's approval.
1 · Connect
Risely connects one source system at a time and starts read-only.
Each connector carries only the scopes its workflows need, and nothing wider.
2 · Map
Source fields map onto the canonical record, once.
The mapping happens a single time per source, with no migration.
3 · Sync
Reads flow in on the source's cadence.
When a grade posts in the SIS, the record updates, and every agent reading Maya sees the new credit load. Writes go back through the source, on approval.
Each instance stands alone.
Fabric runs single-tenant: records never pool with another institution's. Risely operates as a FERPA school official. Every read is scoped, and every write lands on the audit ledger with a name attached.
The details live on the security page
Posture, the ledger, roles, and who can see what.
Security & governanceZero records migrated
Fabric reads in place. The SIS stays the system of record, and every write goes back through it.
Connector by connector
Sources turn on one at a time, so the rollout is additive and nothing cuts over.
Least privilege
Each connector carries only the scopes its workflows need. A read scope on enrollment grants exactly that.
Fabric connects it. The Agent Graph remembers it.
Every record Fabric resolves becomes a point on the living map of the institution, and every action draws another line.