"No separate login" gets used loosely, and the loose version usually means SSO. That's worth separating out, because SSO solves a smaller part of the problem than people expect.
SSO removes the password, not the journey
Single sign-on is genuinely useful. Nobody has to remember another password, IT doesn't manage another credential set, and access follows the identity provider.
But look at what a learner still has to do: notice a notification, decide to act on it now, click through, land on a portal, wait for the redirect, find the assigned course, and start. SSO removes one step from that sequence. The other five remain, and they're the ones that cost completion.
The friction was never mainly the password. It was the context switch.
What "no login" means strictly
The strict version is that training is completed inside a tool the person is already authenticated in and already using — so there's no journey at all.
For most desk-based companies, that tool is Slack or Teams. A module arrives as a direct message, gets read there, the quiz is answered there, and completion is recorded. The person never navigates anywhere, because there's nowhere to navigate to.
That's the difference between reducing friction and removing it.
The IT side is underrated
The learner experience gets discussed most, but the administrative argument is often what actually decides it.
A separate LMS means accounts to provision for every new hire, permissions to configure, and deprovisioning when someone leaves. That last one matters more than it seems — orphaned accounts in a system holding training records are a real audit finding, and they accumulate quietly.
When training runs inside Slack, membership is the account. Someone joins the workspace and they're reachable; they're removed and they're not. There's no second directory to keep in step, which also means no drift between the two.
What you give up
Only people inside that workspace can be reached. This is a hard limit rather than a soft one:
- Contractors and partners who aren't in your Slack can't be trained this way.
- Customers definitely can't — you can't push into their workspace.
- Deskless staff without a chat account are unreachable.
- People who've left retain no access to their own records, which occasionally matters.
If any of those populations are in scope, you need a portal for them, and probably a conventional LMS.
The options
Poplearn delivers modules as Slack direct messages, completed in place. /courses new converts a document into modules with quizzes, /assign #support targets a person, a channel, or every new hire going forward, and /progress gives live completion by team, exportable on demand. Free under 20 seats.
Doozy also runs entirely inside Slack DMs with no separate app or login, with quizzes as interactive Slack blocks and 50+ HRIS connectors.
Haekka is Slack-first including video, focused on HIPAA, SOC 2, GDPR, and PCI compliance.
Arist goes wider, delivering through SMS, Teams, WhatsApp, Slack, and email with no app or login — useful precisely because it reaches people who have no chat account.
Everything else in the market is SSO at best, which is the weaker version.
How to check a vendor's claim
Ask for a demo of the learner's experience, not the admin's. Watch whether the person completing the training ever leaves the chat window. If a browser opens, it's SSO, not login-free — regardless of what the marketing says.
Then ask what happens when someone joins the company, and when they leave. If the answer involves provisioning an account, you still have a second system to maintain.
Add Poplearn to Slack to see the strict version — free under 20 seats, installs in about a minute.
