Sharing FAQ
The ways to get a course to people, whether learners need an account, and how identity affects what you can see.
There are several ways to get a course to people: a shareable link, an email invitation, Slack, embedding it in your own product, or SCORM in either direction. Which you choose depends on where your learners are and whether you need to identify them.
What are the different ways to share a course?
You can share a published course with a link, send it as an email invitation, push it to Slack, embed it inside your own product or website, or export it as a SCORM package to run in another learning system.
There's also a route in the other direction: if you have an existing SCORM package from another authoring tool, you can host it in Coassemble and share it exactly like any other course, rather than exporting anything.
A link is the quickest way to reach people. Email invitations suit a known group. Embedding keeps learning inside your own product. SCORM export delivers through an existing LMS, and SCORM hosting brings someone else's package here.
Do learners need a Coassemble account to take a course?
No. People taking a course you share don't need their own Coassemble account or login. They open the link, the email invitation, or the embedded course and start straight away.
Will I know who completed the course?
It depends how you share it. If you capture someone's identity when they start, making them an Identified Recipient, their progress and results are tracked against them. If you share a course anonymously, to Anonymous Recipients, you'll see that activity happened but it won't be tied to a named person. Choose an identified option when you need to know who did what, such as for compliance.
Can a learner pick up where they left off?
Someone identified can return and continue from where they stopped. For anonymous access, progress is kept for the same person on the same device and browser within their session, so switching device or browser means starting again.
Can I control who can access a course?
Yes. Access settings let you decide how open a shared course is, so you can keep it limited to the people you intend rather than anyone with the link. The available controls depend on your plan.
Can I stop sharing a course after I've shared it?
Yes. You can unpublish or remove access to a course so the link or invitation no longer works, which is useful when content is out of date or a programme has ended.
Can I share more than one course at once?
Yes. Grouping courses into a collection lets you share a set of related training with a single link instead of sending courses out one at a time.
Can I reuse a course that already exists?
Yes. A shareable template lets you take a course someone has made available and bring a copy into your own workspace to edit and use, rather than building it from scratch.
Can I run a Coassemble course in another LMS?
Yes. Exporting a course as a SCORM package lets you upload it to another learning management system and deliver it there, with completion and results reported back through the LMS.
Can I bring a SCORM course from somewhere else into Coassemble?
Yes, two ways. Host the package and it runs exactly as it was authored, tracked by attempt with question-level results. Or convert it into an editable Coassemble course made of blocks. Hosting is available if you deliver Coassemble inside your own product or platform, and converting is open to every workspace.
Can I put a course inside my own product or website?
Yes. Embedding serves the course inside your own product on your own domain, so learners take it without leaving your app and without being sent to a separate Coassemble portal. You can embed a whole course, or a single screen.