For universities and foundations that run programs

Your speakers teach once. Every participant keeps the notes.

Scrolls for Courses turns every session of your program into study notes, a task list with deadlines and a practice list, for each person in the cohort. Nobody takes notes.

Participants pay nothing · English and Hindi · The person who records uses a Mac

1. Record58:12
Day 3 · REST APIs and authenticationThe speaker's Mac, one microphone. No bot joins.
2. Notes, written onceSample data

What it covered

  • Why APIs are stateless
  • Logging in with a JWT, and when it expires
  • 401 versus 403
Finish the REST API projectTask · Fri
Rebuild the login formPractice · Thu
3. Every participantSample data
Join codeK7QM-4TXA
Cohort Oct 2026ends 31 Oct 2027
  • A
    Asha
    4 of 4 done
  • R
    Rohan
    2 of 4 done
  • M
    Meera
    3 of 4 done
  • K
    Karan
    1 of 4 done
+ 38 more. Same notes for all, each person ticks their own.
Made for programs of every shape
  • Residential workshops
  • Coding bootcamps
  • Short courses
  • Continuing education
  • Skill development programs
  • Placement training
  • Incubator cohorts
  • Certification prep

A speaker says it once. Forty people write it down forty different ways. Scrolls writes it down once, for all of them.

1recording per session, for the whole cohort
2languages: English and Hindi, including sessions that mix the two
2yrs maxthe longest a cohort can keep access, then it ends by itself
0bots in your session and no AI training on your audio
What a participant opens

Notes that are ready before they leave the room.

Shared into the cohort when the session ends. Read-only, the same for everyone, with each person’s own ticks on top.

Study notesDay 3 · REST APIs and authentication · 58 minShared by your programSample data

What the session covered

  • How a REST API names resources and uses GET, POST, PUT and DELETE.
  • Why APIs are stateless, and how tokens carry who you are.
  • Logging in with a JWT, and what happens when it expires.

Key concepts

StatelessJWTStatus codesEndpointsRefresh tokens

Review questions

  1. Why doesn’t the server keep a session for each user?
  2. What’s the difference between a 401 and a 403?
  3. What should the app do when a token expires mid-request?
How a program runs

Five steps, from first session to last.

Get the recording app
The record of the program

What was covered, by whom, on which day.

Every session lands in one place, so the program has a record even when nobody kept one.

Who it’s for

One program pays. Everyone in it benefits.

For the institution

A whole program, documented without extra work.

Coordinators and speakers record. Scrolls does the writing, and you decide who sees what.

  • Cohorts with a start date and an end date
  • Notes for every session, on time, the same for everyone
  • Deadlines the speaker announced, written down for the whole cohort
  • PDF and Markdown export for WhatsApp, email or your LMS
  • One quote per program, so there is one invoice
Participants never pay
For participants

Pay attention in class. The notes are already coming.

Join with the code your program gives you. Nothing to buy, nothing to record.

  • Study notes, Tasks and Practice for every shared session
  • Your own ticks: ticking a Task never changes anyone else’s list
  • Ask questions and search across the whole program
  • Definitions of the session’s hard terms, written into its notes
  • If you don’t use the app, your program can send you the same notes as a PDF
Free, because your program covers it
Studying on your own? Courses are joined through an institution, with a code from your program. You can’t sign up for one by yourself. Questions? Ask us
Privacy and trust

Your institution decides what’s recorded.

Scrolls is built so that a university can say yes to it without a long meeting.

No bot joins

The speaker’s own Mac records through its microphone. Nothing enters your session or your call.

Audio stays on that Mac

The recording is a file on the recorder’s computer. We don’t keep a copy of it.

No training on your sessions

Our transcription provider is told not to train on or keep your audio. Anonymous analytics are opt-in and never include what was said.

Access has an end date

Each cohort expires on a date you choose, at most two years out. After it, participants can’t open the sessions.

The institution

Decides what is recorded, and why.

Under India’s DPDP Act that makes you the Data Fiduciary. You tell speakers and participants that sessions are recorded.

Scrolls

Processes it only to make the notes.

We act as your Data Processor, and put the terms in a short data processing agreement. Read exactly what we collect.

FAQ

Questions coordinators ask

What does it cost?

Participants pay nothing. The institution gets one quote per program, based on how many hours you record. Tell us about your program and we will send a number.

Do participants need a Mac?

The person who records does. Participants on a Mac join the cohort with the code and read, ask and tick inside the app. Everyone else gets the notes as a PDF or text file that you export and send, however you usually share things. A way to read notes in any browser is something we are looking at next.

Who can see a session?

Only the people in the cohort it was shared into, until the cohort’s end date. Sessions you don’t share stay private to whoever recorded them. Participants can read a shared session but can’t change it.

Can someone sign up for Courses on their own?

No. A course is something an institution sets up, and participants are enrolled with a code. If you are studying on your own, ask your program whether it can use Scrolls.

Does it work with online sessions?

Yes, if the recording Mac’s microphone can hear the session. Play the call through the laptop speakers, not headphones. Scrolls doesn’t capture a call’s audio directly yet, and it never joins the call.

What about weak internet at a venue?

Scrolls needs a connection to start a session and to write the transcript and notes. If the connection drops in the middle of a session, recording carries on on the Mac, and the part the transcript missed can be transcribed from the recording afterwards. If there is no connection at all, record on a phone and upload the file when you are back online. Scrolls turns an uploaded recording into the same notes and lists.

Which languages work?

English and Hindi, including sessions where speakers move between the two. Hindi is written in Devanagari. Other languages aren’t supported yet.

Are we allowed to record our own sessions?

That’s the institution’s decision and responsibility. Tell speakers and participants that sessions are recorded, for example in the program brief, and get a guest speaker’s agreement first. Recording laws differ by country and state.

Why does my Mac warn me when I open it?

Scrolls isn’t signed with an Apple developer certificate yet, so macOS stops it the first time it is opened. The Download page walks through opening it anyway, with screenshots.

How do we get a newer version?

Come back to the Download page and download the latest version. Scrolls tells you when a newer one is available and points you here. Your sessions carry over.

Run your next program with the notes already done.

Tell us about one program. We will help you set up a cohort and record the first session.