Skip to content

What your academy can do now.

Every capability we ship, in plain terms — what it lets you do, and where it lives. The fastest way to try any of these is to ask your connected Claude: it can hand you a one-click link straight into the page.

  1. Operations

    A seating chart for every room, with the children's faces on it

    See your room laid out as it really is — every seat, every child, their photo on the seat they sit in. Drag a child from the side onto a seat, drag one child onto another to swap them, and fill the empty seats in one go.

    • Big enough to actually read: the whole chart fits your screen, with each child's photo and name on their seat.
    • Three lists down the side that always add up — who has no seat yet, who is waiting for a space in the room, and who is only in today.
    • Drag to seat, drag one child onto another to swap them, click a seat twice to free it up.
    • Keep a standing plan for the room and a separate picture of today, so a one-off change never overwrites how the room normally sits.
    • Add a photo to a child on your roster once and it appears everywhere you need to recognise them — a supply teacher can tell who is who on their first morning.
    • Photos and names never leave 1EDU. The seating platform only ever knows that "somebody" is in seat B3, never who.
  2. Website

    Your school's whole website now lives here

    Not a profile page — the actual website, at your own address. Pages you choose, built from the same blocks throughout, with your enquiry and application forms coming straight to you and your search-engine settings per page.

    • Served at your own address — yourschool.1edu.app, or your own domain once it points here.
    • A menu that follows your pages: group them, order them, and leave a page out of the menu without taking it down.
    • Forms that reach you — enquiries, tour requests, applications and employment interest all arrive in 1EDU rather than an inbox nobody watches.
    • Per-page titles and descriptions for search engines and shared links, so a page you care about is not summarised by whatever Google finds first.
    • A pre-launch password holds the whole site behind one screen while you build it: real address, real content, invisible to families and to Google until you are ready.
  3. Website

    Your website is now something you can just ask for

    Your school's website is built from pages, and each page from blocks — a hero, a grid of values, a quote, a form. All of it can now be read and changed by asking your Claude, so adding a page no longer means asking us to do it.

    • Ask for what you want: "add a page for our summer programme", "put the tuition table above the FAQ", "take the staff page down until we have new photos".
    • A new page starts as a draft that only your school can see. It goes public when you say so, and you can take it down again without losing the work.
    • Your Claude can list the blocks available and exactly what each one needs, so it builds pages from the real library rather than guessing.
    • A block written in the wrong shape is refused with the reason, instead of quietly appearing as an empty band on your site.
    • Testimonials must say whether the family consented, and an unconsented quote never appears — nobody can add praise to your site that a family did not give you.
    • Building the website is its own permission: you can let the person who runs your site do exactly that, without also handing them your domain settings, tuition or staff files.
  4. Branding

    Your colours are yours to set — and there are more than two of them

    Set your academy's colours yourself on the Brand page, without asking anyone. Two colours are still all you have to give: everything else is worked out from them and checked for readability. But if your school already has a design system, the rest of the palette is now yours to say.

    • Give two colours and get a complete, legible interface — that has not changed, and is still all most schools need.
    • A school arriving with its own design system can now set the neutrals, the dark grounds and the washes as well, instead of accepting ours.
    • Every colour is checked against a readability floor before it is used, so a pale brand colour never becomes text nobody can read.
    • Set it on the Brand page, or just tell your Claude — both write the same thing.
  5. Branding

    The sign-in screen is your school's, down to the wording

    Your staff no longer sign in to a page that says 1EDU. It wears your logo and your colours, says which academy it is for, and the two lines of copy on it are yours to write.

    • Your mark and your colours, with the academy named — someone who works at two schools can tell which one they are signing in to.
    • Two lines you control: a subtitle under the academy name, and a note under the button.
    • That note answers the question families actually arrive with. By default it says plainly that parents and guardians do not need an account — because entering an address that is not a staff member returns the same neutral answer either way, and nothing ever arrives.
    • Replace it with whatever suits you: an office number, opening hours, or who to call.
  6. People

    Give a role what it needs without making someone an administrator

    A role can now carry named areas of responsibility of its own. Your IT person can rotate an API key without also holding tuition, payroll, staff files and the power to remove colleagues — which, until now, was the only way to give them that one thing.

    • Compose a role once from named responsibilities — the staff directory, credentials, the calendar, API keys, the website — and it applies to everyone in that role, including every future hire.
    • It only ever adds. Composing a role can never quietly take something away from the people already in it.
    • You can only hand out what you hold yourself, so nobody can grant themselves upward.
    • Naming your roles and deciding what they can reach are separate permissions on purpose: keeping the org chart tidy is a different job from deciding who can see the money.
  7. People

    You can now say how far a role reaches — not every job needs to see everything

    When you name a role, you can say whether it belongs to the day-to-day running of the school or whether that person just does their own work and what you hand them. Until now every role your academy named got the same reach as a lead teacher, whatever you called it.

    • Pick it when you add a role, or change it later on the "Your roles" page — or just tell your Claude "our summer youth staff should not be seeing incident reports".
    • The day-to-day reach covers the room, school materials, training, credentials and incident reports — because the person in the room is the one who writes the report.
    • The narrower reach is for seasonal help, contractors, volunteers and anyone who should not be reading about children.
    • Changing it changes it for everyone already in that role, and the page tells you who moved — you never have to go and update them one by one.
    • Anyone whose access you set individually on their own record is left exactly as they are; a change to your org chart never quietly undoes a decision you made about one person.
    • Administrator access is still given to a PERSON, deliberately and one at a time. It is not something a role can carry.
  8. People

    The person setting your academy up is no longer counted as one of your staff

    Whoever gets an academy running on 1EDU — a consultant, a founder, someone from our side — is now recorded as PROVISIONING it rather than working there. They keep the access they need to finish the job, but they hold no role on your org chart, so nothing you require of your staff is aimed at them by mistake.

    • Your roster now says "provisioning this academy" where a job title would be, instead of showing them as a head of school who does not work for you.
    • Requirement sets, trainings and clearances written for a role no longer reach them — they are not in the role.
    • Giving a provisioner an actual job is refused with a question rather than done quietly: have they finished, or are they joining you properly?
    • When the academy is ready to run itself, record the handover — ask your Claude "who is provisioning us?" and then "hand the academy over to Dana". It puts on the record who took it on and when.
    • A handover is a permanent record, not a status that can drift: who handed over, to whom, on what date, in whose words.
  9. Learning

    Your staff can finally see why they have a training, and when it is due

    The page a staff member opens at /me is now a proper list of their work: what is outstanding, what they are part-way through, what they have finished, and the certifications they hold — as a table with the things a working adult actually needs, including the reason it landed on them and the date it is due.

    • Every row says WHY: "because you work in the Infant Room", "because you are a Teacher", or the requirement set that names it. Your rooms have different requirements, and now the person standing in the room can see which of theirs applies.
    • You can put a due date on a module when you assign it — ask your Claude: "assign the safe sleep module to the Infant Room, due the 30th." Anything past its date is flagged in red, counted at the top of their page, and sorted to the front.
    • When a training is dated by two rules at once — a deadline you set and a standing requirement for their role — they see the earlier one, and the page names the rule that set it.
    • A module they cannot open yet now says what would open it, instead of just showing a padlock.
    • Each row shows what the training actually involves — how many slides, how many checkpoints, whether there is a final exam — so someone can tell a five-minute read from a proper sitting. We do not print a minute estimate, because we do not have one and a wrong one gets planned around.
    • Built for a phone: the same list reads as cards on a handset, so it works standing in a classroom.
    • Ask your Claude "what does Dana still owe?" and you get exactly what Dana sees — same rows, same reasons, same dates.
  10. Learning

    Know when someone left the exam

    For a training whose certificate gates something real, you can now ask that the assessment be taken in the training window. If a learner switches to another tab or another app while a checkpoint or the final exam is open, they get a short notice when they come back, and it is counted beside their score on your results view.

    • Off unless you ask for it, per training: right for a graded exam, noise on a reference deck. Ask your Claude — "record it if someone leaves the infant room final exam."
    • The learner is told before they answer anything, and the notice on their return is matter-of-fact — it says the assessment is meant to be taken here, not that they have done something wrong.
    • On your Learners table it reads plainly: "Left 6 times · about 4 minutes away in total", beside the score rather than folded into it.
    • It is a signal to ask about, not proof. A phone beside the laptop leaves no trace, and a learner whose browser told us nothing shows as "Not reported" — an unknown, never a clean record.
    • Optionally offer full screen when an assessment opens. It is an offer: staff can decline it, and leaving full screen is not counted against anyone.
    • Nothing about this stops a learner or changes a score. Passing, certificates and completion are exactly as they were.
  11. People

    Set up the roles your academy actually runs on

    Before you assign anyone a role, say what roles your academy has. Keep the 1EDU ones that fit, write your own for the rest — CEO, IT Tech, Education Director, Summer Youth — and give each one a description of what it is responsible for. Your chooser then shows your academy, not a generic list.

    • Your own roles sit alongside ours; you decide which of ours you actually use.
    • A role you no longer need can be retired — and if anyone still holds it, we tell you exactly who before anything changes. Nobody is ever moved for you.
    • Ask your Claude to set the whole set up in one go: "our roles are CEO, Education Director, Teacher, Assistant Teacher, IT Tech, Admin and Summer Youth."
    • Naming a role does not grant anything on its own — what a person can see and do is still set on them, deliberately.
  12. Learning

    Look back through a training — and decide whether a test is open-book

    Staff can page back through material they have already covered, and reopen a training they finished to look something up weeks later. What they cannot do is jump ahead: a module is only complete when the steps are actually done.

    • Finished a training and need to check a detail? Open it and read back through the slides — it does not affect your completion or your score.
    • Failed a checkpoint? The button that tells you to review the material now takes you to it.
    • While a checkpoint or final exam is open, the slides are closed by default — the exam is testing what someone retained.
    • If a particular training should be open-book, turn that on for that module: "let staff check the slides during the safe sleep quiz."
    • Nothing can be skipped. No setting lets a learner reach the end without doing the work in between.
  13. Learning

    Narration plays as the learner arrives on each slide

    On a narrated module the audio starts by itself and stops when they move on, so nobody has to press play on every slide of a seventy-minute course. The player is small enough to leave the slide the room it needs.

    • Turn autoplay off per module if a training is meant to be read rather than listened to.
    • A learner who prefers to read can mute for the rest of their session.
    • Some browsers refuse to start audio until someone clicks — when that happens the play button is shown clearly rather than the audio just not arriving.
  14. Academy

    Your staff training portal looks like your academy

    The logo and colours on your academy profile now carry through to the screens your staff actually see — the sign-in page, their training list, the module player and their certificate — so training reads as yours rather than as generic software.

    • Set your logo and colours once on your academy profile; every staff-facing screen follows.
    • Colours are adjusted where they need to be so text stays readable — a pale brand colour will not make a training unreadable, and we tell you when we have adjusted one.
    • No logo yet? Your academy's initials stand in, so the portal is never unbranded.
  15. Workspace

    Anything your Claude makes for you now lands in your academy

    When you ask your Claude to design, draft or diagram something, it hands the file straight to 1EDU and attaches it to what it is about — a change request, a document, a room, your academy. It stays yours, in your academy's own storage, instead of living inside one conversation.

    • Ask for a mockup of a screen you want changed and it arrives attached to your request, so our team can open the design you had in mind instead of asking you for access to it.
    • Works for anything: a draft policy, a workflow diagram, a spreadsheet export, a screenshot of something that went wrong.
    • Your files keep their original name and are never overwritten — a second version sits beside the first, not on top of it.
    • Everything handed over stays private to your academy. Nothing becomes a public web page, and nothing is published anywhere outside 1EDU.
    • Already have a file sitting on an old website or someone else's drive? Your Claude can pull it into your academy's own storage in one step.
  16. People

    Decide what every role must complete — and name your own roles

    Write down, once, what a person in a given role has to finish — trainings, documents to read, acknowledgements to sign, credentials to hold — and everyone who joins that role receives it automatically. You define the sets; the platform applies them.

    • Build a set per role: "every infant room teacher completes safe sleep, reads the handbook, and signs the acknowledgement." New hires in that role get the whole set the moment they are set up.
    • Name the roles your academy actually uses. If you have a lead teacher, a floater, or a bus driver, add them — you are no longer limited to a fixed list.
    • Preview before you commit: see exactly what a new person in a role would receive, and apply a set to the people already on your roster.
    • Ask your Claude to build one for you — "set up what every new infant room teacher has to complete" — or work through the Requirements page yourself.
  17. Operations

    Assign training by room, not just by job title

    Your rooms are now part of the platform. Set up your Infant, Toddler, Pre-School and After School rooms, put staff in the rooms they work in, and assign training to a room so only the people in it receive it.

    • Staff can belong to more than one room — a floater covers three, and gets what all three require.
    • Assign a course or a module to a room by the name you actually say: "Infant Room".
    • Add someone to a room and they pick up that room's required training automatically, without you re-running anything.
    • Rooms carry your own vocabulary — age bands like "Mixed Age 3-5" and labels like "Floater" are yours to write, not a fixed menu.
  18. People

    New staff can ask for access; you approve in one click

    Share one link with a new hire and they start their own account. The request lands in an approval queue, and approving it sets them up completely — sign-in link, onboarding, and everything their role requires.

    • No passwords, ever — approving sends them a sign-in link, the same passwordless way everyone else gets in.
    • During an onboarding week, several people can request at once and you approve them as you get to it, instead of keying in each one.
    • A role someone claims for themselves is only ever a suggestion — you decide what access they actually get.
    • Ask your Claude "who is waiting for access?" and approve from there if you would rather not open the console.
  19. Learning

    Know the moment someone finishes a training

    Training completion can now come to you instead of you going to look for it. Choose who should be told when a staff member finishes — a director, a room lead, or a specific address — and the message arrives with their name, the training, their score and the date.

    • Set it once for the whole academy, or per training when a particular course needs a particular person told.
    • Built for the moment it matters: when a training is the gate before someone takes their first solo shift, you hear about it rather than checking a dashboard.
    • Tell your Claude "email me whenever anyone finishes the infant room training" and it is configured.
    • Notifications go out as your academy, from your own sending address when you have connected one.
  20. Learning

    Fix a slide or a quiz answer yourself

    Correct a typo, reword a slide, change an answer option or adjust a passing score directly in the Learning console — no AI session needed for routine upkeep of a module you already published.

    • Reword a slide or a question and nobody mid-training is disturbed — they carry on exactly where they were.
    • Add or remove a slide and anyone who already passed that section is brought back to re-read it, so nobody misses new material.
    • Raising a passing score never un-passes anyone who already cleared the old one.
    • Building a new module is still a conversation with your Claude — this is for the small corrections that come up as your policies change.
  21. Workspace

    Read your uploaded documents in the page, and host your own logo

    Uploaded files — posters, handbooks, schedules — now open and render inside 1EDU instead of downloading, and your academy logo can be uploaded or imported rather than linked from somewhere else.

    • Click a document and read it where you are; download it when you actually want the file.
    • An uploaded file is kept exactly as you gave it to us, and comes back byte for byte.
    • Upload a PNG or SVG logo — or import the one you already have hosted elsewhere, so your academy page and your certificates stop depending on somebody else's server.
  22. Learning

    Take your own assigned training from your dashboard

    Directors and administrators are staff too, and are routinely assigned the same training as everyone else. Your assigned modules now appear on your dashboard with a button that opens them.

    • Start or continue a module straight from the overview — no separate sign-in, no hunting for a link in your inbox.
    • Hand any staff member a working link to a module they are assigned: ask your Claude to "send Dana her infant room training link" and it goes out ready to open on any device, with no login.
  23. Social

    Post to LinkedIn — from your academy, your assistant, or your Claude

    Share your academy's story on LinkedIn without leaving 1EDU. Connect your LinkedIn once (you approve it on LinkedIn's own site, in your browser), then draft posts and stage them on a pipeline board — drafts, scheduled, published. Drafts never publish anything; putting a post live is always a clear, confirmed step.

    • A pipeline board on the Social console: drag a draft to Scheduled and pick the date and time, or drag it to Published to post right now — each move asks you to confirm before anything goes public.
    • Describe the post and let the platform draft it for you, in your academy's voice — then edit before you save.
    • Your dashboard assistant drafts posts on request ("draft a LinkedIn post about our open house") — every draft waits for your approval, and nothing publishes until you stage it.
    • Fully driven by your Claude too — once your Claude is connected to your academy (Console → Connect Claude), just ask: "draft a LinkedIn post about our book fair and schedule it for Friday at 9am." It can check what's connected, draft the copy, edit wording or timing, schedule or post now, and confirm delivery.
    • Posts publish as the LinkedIn profile you connect, and scheduled posts go out automatically at their time.
  24. Web address

    Run your academy on your own web address

    Point a subdomain you own — like academy.yourschool.com — straight at your 1EDU academy, so families visit your address and see your academy, with your logo and colors. You add one DNS record; we handle the secure certificate.

    • A self-serve page shows the exact DNS record to add and checks when it's pointing to us.
    • Your academy keeps working at its 1EDU address the whole time — no risk in setting it up.
    • One button hands it back to us to finish the secure setup, usually within a business day.
  25. Publishing

    Create printed children's books — by talking to Claude

    Make print-ready picture books with your academy: add your illustrations and words, lay out the pages, and get an Amazon-KDP PDF plus a polished online reader — and a Library section on your public page that shows every book you've published. The whole thing is driven through your Claude: see all your books by category, open one, build it, and edit any page, just by asking.

    • A real picture-book reader and a print-ready KDP PDF (with a share QR and ISBN barcode) — professionally typeset, not a rough draft.
    • Every book you publish appears in a Library on your public academy page, ready to read.
    • Fully driven by your Claude: "show me my books" lists them by category, then open one, build it, or edit a single page — its words, its illustration, its layout, its order.
    • Nothing is ever lost — every image and line of text is inventoried and kept, whether or not it lands on a page.
  26. Documents

    Your academy's documents, through your Claude

    Ask your Claude what enrollment and consent documents your academy uses — enrollment agreement, media consent, field-trip permission, emergency contact, handbook acknowledgement — and it can define new document types for you on the spot. The document lifecycle runs on the platform; your academy's definitions stay yours.

    • Ask "what enrollment documents does my academy have?" and your Claude answers from your live catalog.
    • Define a new kind of document (and its section structure) just by describing it to your Claude.
    • Completed and signed copies are kept privately for your academy — never mixed with anyone else's.
  27. People

    Your student roster, in one place

    Every family and enrolled student now has a home in your console — grouped by room or grade, with guardian contacts and statuses. Add a family, enroll a student, or withdraw one right from the page; the heavier work stays a conversation with your Claude.

    • See your whole community grouped by room, with headcounts at a glance.
    • Add a family, enroll a student, or withdraw one right from the page.
    • Guardian contacts sit with each family, ready when you need them.
  28. Governance

    Publish policies and track who's read them

    Your governing documents — safeguarding, code of conduct, acceptable-use — publish here, assign to the staff who must read them, and show who has acknowledged versus who still owes. An opt-in weekly reminder nudges only the stragglers.

    • Publish a policy and assign it to everyone or a specific role.
    • Track acknowledgement — who has read it, who hasn't — at a glance.
    • Turn on a weekly reminder that nudges only the people who still owe.
  29. Settings

    Your team sees only what their role allows

    Your console is now organized into labelled sections — People, Team, Program, Operations, Money, Governance — and each teammate sees only the ones their role permits. A single Settings page gathers your team, their roles, your AI connection, and the tokens that connect Claude.

    • The console is grouped into labelled sections; each role sees only its own.
    • Manage your team, their roles, and access from one Settings page.
    • Your AI key and Connect-Claude tokens live there too — never shown after saving.
  30. Tuition

    Families can pay tuition online

    Your invoices can now carry a secure pay-online link. Connect your school's own payment account once, and every bill you send gives the family a card-payment button — the money lands in your account, and the invoice marks itself paid.

    • One-time setup: connect your school's payment account from the Payments page.
    • Each invoice you send can include a pay-now link — no more chasing checks.
    • Payments are per-school: your funds settle to your account, not ours.
  31. Leadership

    See your whole academy at a glance

    The Command Center pulls enrollment, tuition, staffing, compliance, and giving into one state-of-the-academy view — and turns that same picture into a board-ready PDF you can hand to your board or funders.

    • One dashboard across every module — no spreadsheet stitching.
    • Generate a polished board packet PDF in a click, current as of today.
    • Ask your Claude for "the state of the academy" and it reads it straight to you.
  32. Advancement

    Run your grant pipeline — and draft with AI

    Track every grant from prospect to awarded, with the reporting deadlines that come after. Your Claude can draft a full application against a live, PII-free snapshot of your academy's real numbers — so the narrative is grounded in fact, not guesswork.

    • A grant pipeline that carries its own compliance calendar once awarded.
    • AI grant-writing pulls from a factual evidence pack, never invented figures.
    • Donor campaigns and year-end giving statements live here too.
  33. Recognition

    Certificates, recognition, and success stories

    Earned certifications now print as branded, verifiable certificate PDFs with a public check page. Alongside them, you can celebrate your team's milestones and capture the academy's wins as published success stories — ready for grants, accreditation, and your public page.

    • Every earned certification can render a printable, verifiable certificate.
    • A recognition wall surfaces staff milestones and lets you give kudos by hand.
    • Success stories double as grant evidence and accreditation self-study.
  34. Operations

    Schedule rooms, and check the calendar for conflicts

    Book rooms and events on a shared academy calendar that catches double-bookings before they happen — ask for any week's agenda, or check a room and time window for a conflict, right from your Claude or the calendar page.

    • Conflict detection is automatic — a clashing booking is refused with the reason.
    • A week-at-a-glance agenda across every room.
    • Rooms are defined once and reused across bookings.
  35. Operations

    Daily attendance and adult-to-child ratios

    Take daily attendance in a couple of clicks, and check your adult-to-child ratio for right now or any moment in the day — the compliance number licensing asks for, computed from your shifts and attendance instead of a clipboard.

    • Attendance is idempotent per student per day — mark it twice, no duplicates.
    • A ratio check reads your staff shifts against present children, live.
    • Daily roll-up counts are one question away for your Claude.
  36. Team

    Staff files, clearances, and hiring

    Keep each staff member's HR file — credentials, clearances, reviews — in one place, with a radar that flags clearances before they expire. And run open roles through a hiring pipeline from applicant to hired, with a warm acknowledgment as they move.

    • Assemble a staff member's whole file in one view.
    • Expiring-clearance radar tells you what lapses next, before it does.
    • A hiring pipeline moves candidates stage by stage and reads the funnel.
  37. Curriculum

    Plan curriculum against your accreditation standards

    Build units and courses, map each to the accreditation standards it covers, and read a coverage gap report that shows exactly which standards still have no evidence behind them — the homework done before the accreditation visit, not during it.

    • Map standards onto a unit or course with your Claude in one step.
    • A coverage report names the gaps — the standards nothing yet teaches.
    • Every revision is kept, so "what did we teach that year" always has an answer.
  38. Getting started

    A public academy page and a staff handbook

    You can now publish an opt-in public page for your academy at 1edu.app/academy/your-name, drawing on your identity and published success stories. And you can compose your policies into a versioned staff handbook — a branded PDF with per-person acknowledgment tracking.

    • The public page is off until you choose to publish it — nothing is exposed by default.
    • Assemble policies into a handbook, publish it as a PDF, and track who has acknowledged it.
    • Both live on their own pages, or set them up by talking to your Claude.
  39. Certifications

    Certifications: define credentials your trainings earn

    Define a certification — its name, issuer, how long it lasts, and what it takes to earn it (complete this training, hold that credential, get an approval). When someone meets every requirement, it is awarded automatically and appears on their profile.

    • Requirements can chain: one certification can require another.
    • Certifications can gate access — require a credential before someone can start a training.
    • Just tell your Claude: "Create a certification that requires the Infant Room training."
  40. Learning

    Programs: multi-part trainings, in order

    Bundle trainings into an ordered program — staff work through the modules one by one ("Module 2 of 5"), each unlocking when the one before is complete, with overall progress at a glance.

    • Order is enforced automatically; no one skips ahead.
    • Your staff see their programs, progress, and what is next in their portal.
  41. Learning

    Scenario slides + voice narration

    Slides can now pose a scenario — a real situation with answer choices and instant feedback — so learners apply the material, not just read it. And any slide can carry spoken narration, generated from your approved script on your own OpenAI account, one module at a time.

    • Scenarios are practice, not tests — feedback on the spot, nothing graded.
    • Narration is selective: approve the script, generate the audio, preview it, then attach.
  42. Sharing

    Share with exactly the right people

    Beyond private, link-only, and public, a presentation can now be restricted: only invited email addresses get in — with a one-time code, or a personal invite link you can revoke anytime.

    • Invite specific people by email; revoke one person without touching the rest.
    • Revoked or expired access simply stops working — immediately.
  43. Learning

    Turn a slide deck into an interactive training

    Take any presentation and deliver it as a guided, step-by-step training: staff move through the slides, pass short checkpoint quizzes to advance, and finish with a final quiz — with per-person progress and scores you can review.

    • Add checkpoint quizzes after any section; a required checkpoint must be passed to continue.
    • Learners see exactly where they are ("Step 4 of 12") and pick up where they left off.
    • Assign to a person, a role, or everyone; review who completed it and how they scored.
  44. AI

    Bring your own AI keys

    Connect your own Anthropic and OpenAI accounts so the AI features run on your credentials. Your Claude does the authoring and building inside your academy.

    • Anthropic key powers the in-app AI features.
    • OpenAI key will power per-module audio narration for your trainings.
    • Keys are encrypted at rest and never shown again after you save them.
  45. Sharing

    Share a presentation with a secure link

    Publish any deck as a live web link you control — keep it private, share by link only, or make it public — with an optional expiry, and lock it down again anytime.

    • Private, link-only, or public — your choice per deck.
    • Revoke or rotate the link to instantly cut off access.
    • Locked or expired links simply stop working — nothing leaks.
  46. Team

    Roles and permissions for your team

    Provision staff with a role — administrator, leadership, staff, or contributor — and each person only sees and does what their role allows.

    • You (the owner) have full administrator access to everything.
    • Access is enforced across the console and your Claude connection.
  47. Platform

    Request features from the 1EDU team

    Need something new? Ask your Claude to file a change request. We triage it, work it, and let you know the outcome — right inside the platform.

    • Draft, refine, and submit a request in your own words.
    • You are notified when it is reviewed and resolved.
  48. Getting started

    Set up your academy — once

    Define who your academy is — name, mission, values, the basics — and everything else builds on it. Just tell your Claude "set up my academy."

    • A single, set-and-forget identity for your institution.
    • Set it by talking to your Claude, or on the Academy page.
  49. AI

    Run your academy by talking to Claude

    Connect your own Claude to your academy over a secure link. Anything the platform can do, your Claude can do — build presentations and trainings, manage your team, draft communications, and more.

    • One connection, scoped to your academy only.
    • Your Claude becomes the workbench; the console is where it all shows up.