Everyone on your team sees the same courses, blocks and scenarios. Work belongs to the team rather than the person who made it — so when someone leaves, nothing leaves with them.
Without a shared library, a team is just several people with separate accounts emailing course files to each other.
One shared library, one invoice, and a clear rule about who owns what.
Two people cannot type into the same course at the same moment. Whoever opens it holds it, and anyone else sees who is in there and can take over when they are done. Everyone can work on any course — just not the same one simultaneously.
That is a deliberate choice. A course saves as a single document, so two simultaneous editors would mean one person's work quietly overwriting the other's. A visible handover is the honest answer to that.
Worth knowing that the tools which do offer simultaneous editing have the same problem in places. Articulate's own documentation tells teams that theme and settings changes “can potentially override those of another user” and to coordinate between themselves.
Per-author pricing, compared. Figures from each vendor's own site, August 2026.
| Tool | Per author, yearly | Five authors |
|---|---|---|
| Articulate 360 Teams | $1,749 | $8,745 |
| iSpring Suite | from $770 | from $3,850 |
| Adobe Captivate | ~$480 | ~$2,400 |
| SCORMBuilder.ai | $348 | $1,740 |
Prices vary by region and change over time — check each vendor for current figures. Elucidat, Gomo and dominKnow quote on request rather than publishing a price, which usually means enterprise territory.
No. A seat on the team is all the access someone needs. You buy the seats; they accept an invitation and start working. Nobody has to sign up separately or enter a card.
Not simultaneously. Whoever opens a course holds it, and anyone else sees who is in there with the option to take over once they have finished. Everyone can work on any course in the library — just one person at a time on each. That protects against one person's save quietly overwriting another's.
They stay with the team. Courses belong to the team rather than the person who built them, so removing a seat takes away that person's access and changes nothing else. There is no transfer step and no period where the content is read-only. Anything they built on their own before joining stays theirs and stays private.
Yes. A freelancer working with three clients, or an agency running a team per client, can hold a seat on each and switch between them. Each team sees only its own library.
The team owner changes the seat count and the subscription adjusts immediately — Stripe charges the difference for the rest of the billing period. Remove a seat and it comes off at the same point. One invoice, however many authors.
Start a team, invite one colleague, and build something together this afternoon. Free for 14 days, no card required.
Start a team free →