For registrars and student records teams
Your office runs the record. Here is what changes.
Whether your title is Registrar, Academic Registry or Student Records, the work is the same: the authoritative record, the calendar, the policies, and the reporting your institution is judged by. On Salesforce as the SIS, all of it runs natively — and changes at the speed you decide, not the speed of a vendor release.
The office, function by function
Nothing about the record is someone else’s module.
In our deployments every records function runs natively — one platform, one student record, no reconciliation between systems that each believe they are right.
- Registration
- Prerequisites enforced at enrollment, section capacity, waitlists, and registration windows you configure.
- Grading
- Grade entry, grade rolls, grade changes with the audit trail your office requires.
- GPA and academic standing
- Computed in the platform from the policies you set — not imported.
- Official transcripts
- Produced natively, delivered through the National Student Clearinghouse, Parchment and My eQuals networks.
- Course catalog and scheduling
- Terms of any shape — or no terms at all — sessions, rooms, times.
- Degree audit
- Progress and what-if analysis against requirements you maintain yourself.
- Transfer credit
- Articulation rules that evaluate, not spreadsheets that remember.
- Holds and blocks
- Any hold type you need, enforced wherever it should bite.
Policy, at your speed
A policy change is a configuration change.
A new hold type, a calendar exception, a revised progression rule, a new program structure — made in days, by configuration. Not a development project, not a vendor ticket, not the next release cycle. The academic policy your institution debates in committee does not then wait a year to exist in the system.
Reporting
The returns your office answers for.
IPEDS, National Student Clearinghouse enrollment reporting and degree verification, state authorization — or HESA, Graduate Outcomes and the Student Loans Company; or the Land statistical office under the Hochschulstatistikgesetz. A statutory return is configuration, so your regime runs natively, and changes when the statute does.
The record is yours. The system should act like it.
Registrars at Westmont, Unity, San Francisco Bay University and Palmer run their records on Salesforce today — with real students registering in real terms.
Insights & events
Written for the records office.
Explainer · Dec 2, 2024
What in the Education Cloud: DocGen
Why we do not recommend Salesforce Document Generation in Education Cloud, and why third-party tools cost far less to own.
Case study · Sep 25, 2025
How SFBU Meets its Mission Through Adoption of Salesforce as an SIS
How San Francisco Bay University moved from paper-based silos to Salesforce as a full SIS, cutting manual work by 80% and growing domestic enrollment.
Article · Feb 23, 2026
Is Your Institution One Resignation Away from a Crisis? The Hidden Risk Inside CAMS SIS
When CAMS know-how lives in one staff member's head, the registrar's office is one resignation from crisis. What that risk looks like and how to reduce it.
Start here
Bring your hardest policy.
The progression rule nobody could configure, the calendar exception your current system cannot hold, the transfer articulation that lives in a spreadsheet. A demo is more useful when it is about your record, not ours.