LearningFlow LearningFlow vs Notion
Notion builds better databases than we do. The difference is what sits around the data: which app may read which columns, and what happens to a base when the person who built it leaves.
Data · Sources last read 13 September 2026
Choose Notion if
Choose Notion when the thing you are building is a record the whole organisation reads, and the AI is a help rather than the point.
- A staff handbook, the induction checklist and the term planner in one place, linked and searchable.
- A course catalogue with relations and rollups, maintained by a coordinator who does not write code.
- Committee minutes that AI can search alongside the trackers those minutes refer to.
Choose LearningFlow if
Choose LearningFlow when software you publish has to read the data, and access has to be taken back one app at a time.
- A consent base where the sign-up app reads and inserts rows, and the office app reads two columns and cannot delete.
- One base read by a staff screen, a webhook and a nightly job, each revocable on its own.
- Students working against that data with their own accounts, not guest invitations to a page.
Where the two are built differently.
The account holds the work.
Someone has to ask her to hand it over, or it goes with her.
The work was made on a personal login, so recovering it is a favour rather than a setting. Schools discover this in August, when the person who built the scheme of work no longer answers email.
The organisation holds the work.
Ms Okafor's key is revoked. The work has not moved.
People hold keys, not possessions. Removing someone removes their key. Whoever teaches 6C next September opens the same library and the same base, on their first morning, without asking anyone for a copy.
What each one does.
Written from each product's own documentation. Where something is true only on a higher tier, the row says so.
| Notion | LearningFlow | |
|---|---|---|
| Database depth | Relations, rollups, dependencies, subtasks, several views of one table and charts, all built without code. | Bases are shared spreadsheet-style databases that published apps read through a contract. |
| Documents and wikis | Pages and blocks hold policies, meeting notes and project trackers that link to each other. | There is no page editor or wiki. Work lives in flows, apps, bases and videos. |
| How access is scoped | Full access, Can edit, Can comment or Can view, given to a person or group on a page or teamspace. | Each app gets seven independent permissions scoped to named tables, named columns and a row filter. |
| Taking access back | Sharing is withdrawn per page or teamspace, from a person or a group. | Any one app is suspended or revoked without touching the others sharing the base. |
| Learner accounts | Members are billed per seat and guests cannot create pages outside what they are invited to, with no roster or submission. | Students are a first-class user type with their own accounts, join codes and assignments. |
| A feature for one group | Switches such as disable export and disable publishing sites and forms apply to the whole workspace. | Seven capabilities switch per member, including base, solution-designer and work-with-ai. |
| What the AI costs | Plus is $10 and Business $20 per member a month billed annually, the Notion Agent starts at Business, and credits are $10 per 1,000 on top. | Credits, not seats, and no subscription is required to run anything. |
| Reading it from your own software | A public REST API covers pages, databases, blocks, users and comments, with a bearer token and an MCP server. | Every flow has an address: POST /task/:taskId with an x-api-key, with optional SSE streaming. |
What comes with it here.
Several apps, one base
One solution can hold a staff screen, a webhook and a scheduler over the same base, each with its own contract.
Credentials the app never holds
A published app calls Gmail, Resend, WhatsApp, Firecrawl, document parse and web search with the keys injected server-side.
Separate wallets
Personal, organisation and enterprise credit wallets are separate, so a teacher's free monthly grant never funds the school's work.
xAPI into your own LRS
Statements go to a self-hosted SQL LRS, or you point the organisation at the LRS it already runs.
Where Notion is the better choice
If the problem is institutional knowledge rather than teaching output, buy Notion. A registrar who wants the admissions policy, the committee minutes and the course tracker linked and searchable will get there faster in Notion, and the database engine underneath is deeper than ours. Relations, rollups, dependencies and four views of the same table are built by staff who write no code, and we have none of that. A Notion page is also a nicer place to write than anything we ship.
The whole stack against Notion.
The table above compares the two at the job they share. This one runs every capability past both, because what a school is choosing between is usually a tool that does one job and a workspace that does many. Hover any mark to see what it means, and a partial one to see exactly what is limited.
| LearningFlow | Notion | |
|---|---|---|
| Ask and read | ||
| Chat with AI | ||
| Research the web and write it up | ||
| Read text off an image or a scan | ||
| Agent browses the live web | ||
| Make | ||
| PowerPoint deck | ||
| Spreadsheet with working formulas | ||
| Word document | ||
| Image generation | ||
| Video generation | ||
| Narrated whiteboard video, corrected scene by scene | ||
| Voice-over | ||
| Song generation | ||
| Interactive web page | ||
| Edit what it made, online | ||
| Slide and design templates | ||
| Presenter on camera, from a photo you supply | ||
| Teach | ||
| Ready-made teacher tools | ||
| Build your own tool, no code | ||
| Lesson that branches on the answer | ||
| Hears them read aloud, checks pronunciation | ||
| Assign to a class with a join code | ||
| Assignments and submissions | ||
| Student accounts | ||
| LTI link from your LMS | ||
| Learning records to your own LRS | ||
| SCORM 1.2 package out | ||
| Build | ||
| Working app | ||
| Full working platform templates | ||
| Several apps over one database, rights each | ||
| App sends email or WhatsApp | ||
| App runs on a schedule | ||
| App accepts webhooks | ||
| Generate real-time apps | ||
| Generate AI-driven apps | ||
| Shared database | ||
| Revoke one app's access, not the others | ||
| Run | ||
| Run any tool from your own software | ||
| Choose the AI model, on every plan | ||
| Switch a feature off per group | ||
| Organisation keeps the work when staff leave | ||
| We do not do this | ||
| Transcribe a video or audio file | ||
| Custom domain for a published app | ||
Before they decide.
We already keep everything in Notion. Do we have to move it?
No. Keep the handbook, the minutes and the trackers in Notion, and put the data that software has to read in a base. Notion has a REST API with a bearer token, and every LearningFlow flow answers at POST /task/:taskId with an x-api-key. A script you own can call both, so the two need not become one system. Most teams draw the line where a published app or a student touches the data.
What will Notion actually cost us per teacher?
Budget Business at $20 per member a month billed annually, because Free and Plus give only a limited trial of Notion AI, and the Notion Agent, AI Meeting Notes and image generation start at Business. Premium models and Custom Agents then run on credits, a Business and Enterprise add-on sold at $10 per 1,000. Note also that a free workspace with more than one member is capped at 1,000 blocks for the life of the workspace. The cap is long-standing, and deleting blocks does not free the count.
Can our students have accounts on the data?
In Notion they would be members, billed per seat, or guests, who cannot create pages outside what they are invited to and cannot join a teamspace or group. There is no class roster, assignment or submission, because teaching delivery sits outside what Notion is built for. In LearningFlow students are their own user type, with join codes and assignments.
A trainer builds a base and leaves in July. What happens?
In Notion, anything in a shared teamspace stays in the workspace. Private pages are the risk, and the recovery tooling is Enterprise-only: admin content search finds pages including private ones and changes their permissions, and an Enterprise workspace owner can take ownership of a teamspace. In LearningFlow the organisation id is stamped when the base is created and never moves, so removing the member deletes the membership row, not the base.
Can an admin give one department the base builder and not another?
Notion's documentation describes no way to do this. Content access is granular, per person or group on a page or teamspace, but feature switches such as disable export and disable publishing sites and forms are workspace-wide. In LearningFlow the seven capabilities switch per member, and a role grants the permission key before the member opts in.
Where this came from. Read on 13 September 2026. Notion changes its product and its prices without telling us, so check anything that decides a purchase.
- Notion pricing: plans, per-member prices and credit pricing ↗
- Notion help: Notion Agent, model choice, credits and downloadable files ↗
- Notion help: Workspace settings and the scope of admin toggles ↗
- Notion help: Admin content search, Enterprise only ↗
- Notion help: Add members, admins, guests and groups ↗
Try it on your own work.
Teachers get credits every month, free. No card, no seat count.