Built for the way universities make decisions
Permissions that carry over
Your roles apply everywhere in the model, to people and agents alike.
People approve what matters
Consequential changes route to the people authorized to make them.
Every action verified
Every write back to your systems is recorded and checked after it lands.
Every number traced
Risk scores show their reasons. Fields link to their source.
Policy checked first
Recommendations are checked against your policies before anyone sees them.
Value measured honestly
Projected and realized value, reported separately.
Lineage
Trace any number back to its source
The full lineage view is available on larger screens.
Zero trust by design
CollegeVine enforces what every person, agent, and application can see and do at the data layer, backed by an audited authorization system. Effective access comes from your own rules, resolved the same way every time.
Correct access for everyone
For team members
Access follows each person’s role, area of responsibility, and any rules specific to their position. A financial aid counselor sees their caseload. A director sees the full picture. Neither can see data outside their scope.
For agents
Every agent is bound to the person it’s working with. It can use only the data both of them are allowed to see, so an agent never sees more than its user, and a user can’t use an agent to reach past the agent’s own scope.
For applications
Applications built on CollegeVine Platform follow the same rules as people and agents. However an application is coded, it can reach only the data inside its permitted scope.
Multiparty support
One agent for all
The same agent can work with an admissions director and an applicant. What it can see and do changes with each person.
For team members
Scope comes from each person’s role, not from how a conversation is set up. There’s no setup per session.
For agents
Working with a financial aid administrator, an agent can update student records and start packaging workflows. Working with a student, the same agent can’t.
Isolation at every step
When an admin asks an agent to act on behalf of students, those conversations don’t inherit the admin’s access. Each student gets their own isolated context, bound only to their permissions. Admin data stays in admin scope.
Compliance
Ready for your security review
Our security program is audited every year and monitored continuously. We’ve been through security review at more than 200 institutions.
SOC 2 Type II
Annual audit and continuous monitoring. The report is available on request.
FERPA compliant
Student record protection is built into how access is decided.
HECVAT
Our Higher Education Community Vendor Assessment Toolkit is ready for your review.
Least privilege by default
No person or agent sees more than their role allows.
Trust and compliance documentation
Security policies, audit reports, and questionnaires are ready to share, under NDA where required.
Start with one domain, then expand on the same model
We scope the first domain with your team and agree on the outcomes to measure.
