How do I get started with a Coassemble Sandbox?
How to request a Sandbox, what it's for, and what to prove while you're in it.
A Sandbox is a free test account for evaluating Coassemble inside your own product or platform. Request one through the form on coassemble.com and our team will set it up and send you your access link. Once you're in, the job is to take one piece of learning all the way through: built from your own content, embedded on a surface you run, delivered to a test learner, with the completion landing back in your own systems.
How do I request a Sandbox?
- Go to coassemble.com and select Request a sandbox.
- Answer a few short questions about who you're building for, your scale and your timing.
- Enter your work email address, company and job title.
- Submit the form.
Our team sets your Sandbox up and emails you a link to get in. If we need more context about your use case before provisioning, we'll reply to that same email address, so it's worth watching for it.
What you'll need: a work email address. Free email domains like Gmail, Yahoo and Hotmail aren't accepted on the form.
What is the Sandbox for?
The Sandbox exists so you can prove an integration works in your own environment, with your own content, before there's any commercial conversation. Spend your time getting one course through the full chain: created, branded, embedded, completed, and recorded in your own stack.
The Sandbox is your evaluation environment. Build is the plan that follows it when you're ready for ongoing use, and you can see what each paid plan includes at coassemble.com/pricing.
How does the Sandbox budget work?
Your Sandbox runs on a single evaluation allocation, sized to prove an integration end to end. It's a one-time budget, so once it's spent, it's spent.
Spend it on moving forward. One course taken all the way through to a captured completion is the most useful thing you can do with the budget you have. Image generation and AI narration both draw on it, so use them deliberately.
What can I do in a Sandbox?
The Sandbox gives you the same feature set as the Build plan, on an evaluation budget.
Creation: generate a course from a prompt, transform a document, or convert a PowerPoint. Generate screens, quizzes and images, refine content with AI, and add AI narration with premium voices. Connect to OneDrive or Google Drive, upload your own images and video, and organise courses into folders and collections. Course creators are unlimited, and so are courses.
Branding: themes and colours, Google Fonts, custom font upload, your logo, and a brand voice so generated content sounds like you.
Delivery: share links, email invitations, Slack, embed in any tool, and all the Course and Collection embeddables including the Player, Card, List and Builder edit mode. Recipients open courses on any device without logging in, and their progress saves. Dynamic SCORM export is available in-app.
Access and identity: anonymous sharing, email capture, Slack pre-auth, pre-determined access lists, domain locking, and API-identified access. Each learner gets a signed link tied to the identifier you already hold for that person in your own system.
Tracking: course, collection and user analytics, completion rates, sentiment, individual recipient usage, CSV export, and webhooks for course created, commenced and completed events.
What should I prove first?
Work through these in order. Each one is a rung towards a real completion landing in your own stack.
- Make an authenticated call. Find your workspace credentials and confirm a call returns your own workspace data.
- Build a course from your own material. Use a real document you'd genuinely want to train people on. Your own handbook, in whatever state it's in, is the honest test of what comes out the other side.
- Brand it. Apply your theme, fonts and logo so it looks like it belongs in your product.
- Embed it on a real surface. Your own product, an internal tool, your intranet or Slack. Somewhere you actually run.
- Deliver it to a test learner. Generate a signed link against an identifier from your own system.
- Capture the completion. Receive the completion webhook in your own stack. This step is the one most likely to need a colleague, so line that up early.
Which APIs can I use in a Sandbox?
You get the embed and player APIs, webhooks for course created, commenced and completed events, postMessage events, and API-identified access.
Generation, tracking, themes, translations and SCORM export all work in-app in the Sandbox. Programmatic access to those sits on the Scale and Partner plans.
Frequently asked questions
Does a Sandbox cost anything?
No. The Sandbox is free. Paid plans are listed at coassemble.com/pricing.
Can I use a personal email address to request one?
No. The form requires a work email address, so free email domains like Gmail, Yahoo and Hotmail won't be accepted.
Can I invite my team into the Sandbox?
Yes. Course creators are unlimited, so you can bring in whoever needs to be part of the evaluation, including the developer who'll do the integration work.
Do the people taking my course need an account?
No. Recipients open a course by link on any device without logging in, and their progress saves as they go.
Does the Sandbox budget refresh?
No. It's a single allocation for your evaluation.
What happens when I'm ready to move ahead?
Build is the plan that follows a Sandbox. Talk to our team about which plan suits your usage, or see what each one includes at coassemble.com/pricing.