How the Academy works

The Rival Academy is the learning layer that sits on top of these docs. Where the documentation is a reference — organized by topic, read on demand — the Academy is a journey: sequenced training that takes a person from new to capable, tuned to who they are and how far along they are.

Reference vs. Academy

The two are deliberately different shapes of the same knowledge. A reference page answers “how does X work?” when you go looking. An Academy path answers “what should I learn next?” and walks you through it in order. The Academy is built from the reference — every lesson draws on the topic pages, so there’s one source of truth and no contradictions between what you learn and what you look up.

Two dimensions: role and maturity

Academy learning is organized along two axes:

Role — Executive, Admin, and End User each get a path tuned to what they need. An exec needs the value and the guardrails; an admin needs setup and control; an end user needs to get productive fast.
Maturity — paths meet people at their level and grow with them, from first steps to advanced deployment. (Rival’s public learning experience does this by asking a couple of quick questions and assembling a path to match — the same idea applied to your enterprise team.)

How it’s structured

The Academy content is grouped into four tracks, from getting started to advanced, and into role-based paths built from those tracks. See Tracks and Learning paths.

A quick example

A new admin doesn’t read the docs front to back. They start the Admin path: what Rival is, then user management, permissions, connectors, governance — each lesson pointing back to the reference page for when they need the detail later. Structured to learn, organized to look up.