Your members sign in and find the lessons in order, the resources beside them, and their own progress marked. A training hub behind a login turns a folder of PDFs and a shared drive into something people actually finish.
The Onboarding Guide Portal is a live Taskade Genesis app embedded on this page and the closest starting point for a training hub. Move through its guided sequence, then choose "Use this app" to clone it in about ten seconds, gate it behind sign-in, and replace the steps with your own curriculum.
The build gives you a course structure with real membership behind it. Modules hold lessons, lessons hold the video, the written material, and the exercise. Each signed-in member has their own progress record, so returning to the hub picks up where they left off. Cohort tags let you release module three on the date the cohort reaches it rather than dumping everything on day one. An embedded agent answers questions from your own course material, which is the difference between a member getting unstuck at 10pm and a member quietly dropping out.
Completion is the metric that matters, and structure drives it more than content quality does. Members finish courses where the next lesson is obvious, progress is visible, and something arrives on a schedule. A hub that shows twelve modules at once, with no marker of where you stopped, produces the folder-of-PDFs outcome regardless of how good the material is. Progress tracking per member, a clear next lesson, and a nudge when someone stalls are three small features that change the finishing rate substantially.
Workspace DNA runs the hub. Memory holds the curriculum, the resources, and each member's progress. Intelligence, powered by 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, drafts lesson summaries, generates practice questions, and answers member questions from your content. Execution releases modules on schedule, sends the nudge to members who have stalled, and issues completion notices.
The hub renders in every layout you need:
- List view for the member-facing lesson sequence in order
- Board view for tracking members through not started, in progress, and complete
- Table view for your internal register of members, cohorts, and progress
- Calendar view for the release schedule and live session dates
- Plus Mind Map, Gantt, and Org Chart across the 7 project views
Automations run the cohort. Connect Taskade automations so enrolment invites the member and tags their cohort, a release date opens the next module, and a member with no activity for ten days gets an encouraging nudge. With 100+ bidirectional integrations, your payment and form tools pull enrolments in, while email and Slack push releases and reminders out.
Release in a rhythm your members can keep. Weekly suits most working adults, and a cohort that starts together finishes at a higher rate than one where everyone begins whenever they bought. The release schedule is a design decision, not an afterthought.
The AI agents in the app carry 34 built-in tools including web search, file analysis, persistent memory, and custom slash commands. A study agent grounded in your lessons answers member questions and cites the lesson it drew from, so nobody is guessing whether the answer is on-curriculum.
The hub is also where your material stops being a one-time delivery and starts compounding. Each cohort produces questions, and each question is either a gap in a lesson or a candidate for the resource list. Feeding those back in means the third cohort gets a noticeably better course than the first, without rewriting anything from scratch. Because the content, the questions, and the progress records all live in the same workspace, that improvement loop takes an hour between cohorts rather than a project.
Clone the app, invite your members, and the course is yours. Members sign in as App Users, counted separately from workspace seats, so a large cohort does not multiply your team billing. Client sign-in is available on Business plans and up, $25/mo billed annually, and App Users is in beta.
Read Education for teaching builds, Knowledge kit for grounding the agent, or browse learning builds in the Community Gallery. Start at Taskade Genesis. Pair this with Add a Client-Facing Knowledge Base to Your Portal and Set Up App User Invites and Access Tags.
Frequently Asked Questions
Can I drip-release content?
Yes. Set a release date or a cohort offset per module and the hub opens each one on schedule rather than showing everything at once.
Does each member see their own progress?
Yes. Progress is tracked per signed-in member, so returning to the hub resumes where they stopped and your register shows who is where.
Can I run several cohorts at once?
Yes. Tag members by cohort and release modules per tag, so a January group and a March group move independently through the same curriculum.
Do members need a Taskade account?
No. They sign in to your published app with their email as app users. They never see a workspace or a Taskade login.
Can the agent answer questions about the lessons?
Yes, grounded in your own material and citing the lesson it used. When a question falls outside the curriculum, it says so rather than inventing an answer.
How do I handle payment for access?
Take payment where you already do and let the confirmation trigger the enrolment invite through Taskade automations. The hub handles access, not billing.
Can I issue completion certificates?
Yes. When a member completes the final module, an automation can generate and email the completion notice and mark the record.
How do I keep members coming back?
A predictable release rhythm, visible progress, and a place to ask questions. The nudge to a stalled member matters too, because most people who drop out do so quietly at the point where they got stuck.
