Curate
What source material can my users bring into Coassemble?
Every route content can take into a course, from cloud storage and SCORM to stock media and embeds, and which routes are on by default in your integration.
Your users can pull content in from cloud storage, upload their own files, bring existing SCORM packages in either editable or as-authored form, use built-in stock media, record their screen, and embed external pages and video. Which of these they see depends on the options you enable in your integration.
Import from cloud storage
Your users can connect their existing cloud storage accounts and pull content directly into Coassemble, without downloading files first.
- Google Drive: connect a Google account and browse Drive files from within the course editor. Documents and presentations can be selected and turned into courses in one step.
- OneDrive: connect a Microsoft account and pull Word documents or other files from OneDrive directly into the creation flow.
Both are enabled by default in the builder and can be turned off in your integration.
Bring in existing SCORM content
Existing training built in another authoring tool doesn't have to be left behind. There are two routes, and they suit different situations.
Convert a SCORM package into an editable course. Upload a package when creating a course with the AI agent and it becomes a fully editable Coassemble course made of blocks. Text, images, galleries, flashcards, process steps, accordions and knowledge checks carry across, and anything that couldn't be converted is listed for review rather than quietly dropped. Articulate Rise, Articulate Storyline, Adobe Captivate and iSpring are recognised specifically, as are Coassemble's own SCORM exports. Packages from other tools still convert, but they're read without knowledge of how that tool structures its content, so less of the original structure survives.
Because conversion runs through the agent, the author also chooses a source-fidelity level for the package, the same three levels that apply to any source material:
| Mode | What it does | When to use it |
|---|---|---|
| Verbatim | Keeps the wording exactly as authored | Policies, compliance content, anything already approved |
| Structured | Keeps the content but reorganises it into a clearer learning flow | Material that's accurate but poorly sequenced |
| Adaptive | Rewrites and expands the material into a fuller course | Rough or thin source content |
This is the answer to "we don't want AI rewriting our approved content". Verbatim doesn't.
Host a SCORM package as it is. Upload it through New course, then Upload SCORM package, and it runs exactly as it was authored, with the original design and interactions intact. A hosted package isn't editable, which is the point when the original design has to survive a sign-off. What your users get around it:
- It appears in the library as a course card with a SCORM label, with an editable cover image, so it looks consistent rather than standing out as an import.
- An explicit processing state shows while the package extracts, so an upload never looks like it has silently failed.
- Reporting is by attempt: attempts, time spent, success and score, and multiple attempts by one learner shown side by side.
- Question-level results download as a CSV, one row per question result, for finding the questions a whole cohort is getting wrong.
- An extra attempt can be granted to a learner who was genuinely blocked, without resetting their record.
SCORM 1.2 and SCORM 2004 (3rd and 4th Edition) are supported, single-SCO or simple multi-SCO, up to 200 MB per package by default. Packages using SCORM 2004 sequencing rules (activity trees, rollup rules, global objectives) are rejected at upload with the reason given, rather than played incorrectly. The original file is untouched either way, so the copy running in the customer's current system keeps working.
Hosting and converting are both open to every workspace.
Upload your own content
Users can upload files from their own device to use as source material or embed directly in course screens.
- Upload documents: Word docs, PowerPoint files and PDFs from a local machine. These can be fed into the AI creation flow to generate a course, or embedded as a document block within a course.
- Upload images: add images to an asset library that's available across every course in the account, so a brand asset or diagram uploaded once can be used anywhere.
- Upload videos: video files can be uploaded to the same asset library or embedded directly into course screens, for walkthroughs, product demos, or any recorded content that belongs inside a course rather than linked externally. Video can be set to landscape or portrait, so footage shot on a phone sits in a vertical frame rather than being letterboxed. Captions can be added by choosing the caption language and uploading an SRT or WebVTT file. Captions aren't generated automatically for uploaded video, so the caption file comes from the user.
- Upload audio: add an audio file to a screen as an inline player.
Access stock media
Built-in integrations with third-party media libraries mean users don't need to source imagery outside of Coassemble.
- Stock photography from Pexels: the built-in stock library is Pexels, searchable from inside the image picker, with images licensed for use in courses and inserted directly into screens. Pexels replaced Unsplash as the built-in library, so if a customer's older material references Unsplash, that's why they're seeing a different library.
- GIPHY: search and add animated GIFs from the GIPHY library to bring energy or humour to screen content. Useful for onboarding courses, culture content, and anything where tone matters.
Record your screen
- Screen recording: record a screen capture directly within Coassemble to create software walkthroughs, process demonstrations, or any instructional content that's easier to show than describe. Recordings are embedded into course screens as video content.
- Loom: Loom recording is offered in the Add video dialog, so a user can record straight into a video block. It can be enabled in your integration and is off by default.
Embed external content
Course screens can embed content from outside Coassemble, keeping learners in one place while drawing on external resources.
- YouTube and Vimeo: paste a video URL into the Paste URL tab of the Add video dialog and the video plays inline within the course without opening a new tab. Captions set on those platforms carry through.
- PDF embed: embed a PDF document into a screen so learners can read or reference it without leaving the course.
- Web embed: embed any web page or external tool into a course screen using an iframe embed block.
A note for partners
Which sources your users can reach depends on the options you enable. Google Drive and OneDrive import are on by default, and Loom recording is off by default. Check your configuration before promising a source to a customer.