Data Warehouse
The data warehouse is a governed, analytics-ready copy of your institution's data, built for reporting. It brings together information from across the student lifecycle — journeys, applications, programmes, subjects, and the events that move people through them — into a structured model you can query directly.
Unlike the live product views, the warehouse is optimised for analysis: it organises data into stable tables, keeps a history of changes, and lets you connect external BI tooling to build your own dashboards and reports.
What You Can Do With It
- Connect your own BI tools — point Tableau, Power BI, Looker, Metabase, or any SQL client at the warehouse and report on live data.
- Build custom reports — write SQL against a clear, documented schema instead of exporting spreadsheets.
- Track trends over time — the warehouse captures point-in-time snapshots, so you can follow how applicant and student numbers change.
- Analyse the application funnel — see how applications move from created to started to submitted.
How Access Works
Access is through managed, read-only credentials that staff create from the institution settings. Each credential is a username and password your BI tool uses to connect directly to your institution's warehouse database.
- Credentials are read-only — they can query data but never change it.
- Access is confined to a curated reporting schema (
dwh). Internal and staging data is never exposed. - Each institution can only see its own data — warehouses are isolated per institution.
- Credentials can be revoked at any time, which cuts off access immediately.
See Connecting to the Warehouse for how to create credentials and connect, and Querying the Warehouse for the tables you can query.
What's in It
The warehouse is organised around two main areas of reporting:
| Area | Describes |
|---|---|
| Journeys | How many profiles sit in each state (prospect, applicant, student, alumnus) for each class or course, captured as point-in-time snapshots |
| Applications | Application lifecycle events — when each application was created, started, submitted, or unsubmitted |
These are surrounded by descriptive tables for dates, programmes, subjects, classes, and application templates, which you join to in order to slice and filter your reports.
Note: New data is loaded into the warehouse on a regular schedule, so figures reflect the most recent load rather than the live second-by-second state of the product.