---
title: "What are Screen embeddables?"
description: "How the Screen Builder and Screen Player embeddables let you offer single-screen creation and delivery inside your own product, without embedding a whole course."
canonical_url: "https://support.coassemble.com/articles/what-are-screen-embeddables-FKiDNs18mi"
md_url: "https://support.coassemble.com/articles/what-are-screen-embeddables-FKiDNs18mi.md"
---
# What are Screen embeddables?

> How the Screen Builder and Screen Player embeddables let you offer single-screen creation and delivery inside your own product, without embedding a whole course.

Screen embeddables let you work with one screen at a time instead of a whole course: the **Screen Builder** puts Coassemble's screen editor inside your product so your customers can create a screen, and the **Screen Player** renders a single screen to a learner, signed to their identity. Together they let you drop learning creation and delivery into any surface in your product where a full course would be too much.

## When is a single screen better than a course?

A course suits a structured journey with multiple screens, sections and a finish line. A single screen suits moments where learning lives inside another workflow. For example:

- **Contextual help inside a feature.** A screen explaining one concept, rendered next to the thing it explains.
- **A knowledge check in your onboarding flow.** One question screen with scoring and feedback, without sending the user somewhere else.
- **Flashcards in a sidebar or widget.** A compact, interactive study aid that fits where a course player wouldn't.
- **Customer-created micro-content.** Your customers build one screen at a time for announcements, process explainers or quick checks, with no course structure to manage.

## What can a screen contain?

A screen is built from blocks on a flexible layout. Your customers can combine headings, paragraphs, images, media, interactive blocks such as accordions and flashcards, knowledge-check questions with scoring and feedback, and embedded content. Screens can start from a designed layout in the layout picker, or from a blank canvas.

An optional AI assistant is available inside the Screen Builder. It is off by default, and when you enable it, it is scoped to editing the screen it is on: your customers can describe what they want and the assistant writes and arranges the blocks.

## How does the Screen Builder work in my product?

You request a signed embed URL from the Coassemble API (`POST /v1/headless/embed/screen` with `action: "edit"`), identifying your user and tenant, and render it in your product. Your customer gets the full screen editor: layouts, blocks, styling and preview. Changes save as they work, with no separate publish step.

You stay in control of the surrounding experience. The builder tells your application when it is ready, when a new screen has been created (including the new screen's id, so you can store it), and when the user wants to go back, so you can route them inside your own product.

## How does the Screen Player work for learners?

You request a signed embed URL with `action: "view"` for a specific screen and learner, and render it where you want the screen to appear. Each learner's progress and answers are tied to their identity, so a returning learner picks up where they left off.

The player reports what happens to your application in real time: screen start, completion, answers and scores. Navigation at the screen's edges is handed to your application as an intent, so you decide what "next" means in your product, whether that is another screen, another page, or nothing at all.

Because the player renders the screen as it currently exists, any edit your customer makes in the builder is reflected the next time the screen loads. There is nothing to republish or redeploy.

## How do I report on screen activity?

The Tracking API returns per-learner activity for a screen, including progress, commenced and completed timestamps, and question attempts. You can filter by learner or tenant and build your own dashboards or alerts on top. Details for every endpoint are in the developer documentation at [developers.coassemble.com](https://developers.coassemble.com).

## Frequently asked questions

### Do screens created in the builder belong to a course?

No. Screens created through the Screen Builder are standalone. They exist in your workspace independently, and each one is rendered by its id. If you want structured, multi-screen journeys, courses and the course embeddables remain the right tool.

### Can I brand the experience?

Yes. Like the rest of the embedded experience, screens carry no Coassemble branding, and themes control colors and typography, so a screen looks like part of your product.

### Do learners need a Coassemble account?

No. You identify each learner when you sign the embed URL, and their activity tracks against that identity. Learners never see a Coassemble login.