Installation is the standard Slack app authorisation flow, and it's genuinely quick. The more useful part of this page is what to do in the ten minutes afterwards.
Installing
Start from the Poplearn site and choose to add it to Slack. Slack shows you the permissions the app is requesting, you pick the workspace, and you approve.
Whether you need an admin depends on your workspace settings. Many workspaces let any member install apps; others require admin approval for anything new. If yours restricts installation, the request goes to a workspace admin and you'll need them to approve it before continuing.
If you're evaluating for a company that restricts app installation, it's worth starting that approval early — it's usually the longest part of the process by a wide margin.
What permissions are for
The app needs to do a few things, and the permission requests map onto them:
- Send direct messages, because that's how modules are delivered.
- Respond to slash commands, for
/courses new,/assign, and/progress. - Read channel membership, so assigning to a channel targets the right people and stays correct as the team changes.
- Receive interactions, so quiz answers clicked inside a message reach the app.
Slack shows you the exact scopes at the point of installation. If your security team wants to review them, that screen is the authoritative list.
No accounts to provision
This is the part that surprises people coming from a conventional LMS.
There is no user provisioning step. Slack workspace membership is the account — someone joins the workspace and they're reachable; they leave and they aren't.
That removes the deprovisioning problem too, which matters more than it sounds. Orphaned accounts in a system holding training records are a genuine audit finding, and they accumulate silently in standalone platforms.
The first ten minutes
Installation on its own doesn't tell you anything. This does:
Convert something real. Run /courses new with an actual document you already have — the onboarding handbook, a policy, an SOP. Not a test document; the point is seeing how it handles your material.
Read the generated modules. Check the split landed sensibly, that each module makes sense on its own, and that the questions test a decision rather than the wording of a sentence. Reorder if the source wasn't in teaching order.
Assign it to one channel. Pick a real team rather than a test channel, so you see how delivery actually lands.
Check /progress a day later. That tells you more about whether this fits than any feature list.
What to check before rolling out wider
Once one course has run:
- Did completion actually improve compared to however you were delivering before? That's the claim the whole tool rests on.
- Did the channel membership match who needed the training? Channels sometimes include observers who don't.
- Is the export what compliance needs — per-person, timestamped, in a form someone outside your tools would accept?
Cost
The free plan covers teams under 20 seats, with Slack-based course authoring and unlimited courses and assignments. No card, no time limit.
Paid plans add web-based course authoring, web-based user management, and in-app rewards and a leaderboard, with annual billing priced lower than monthly.
Add Poplearn to Slack to start — about a minute to install, and a document you already have is all you need.
