Centralized Asset Management & Collaboration

The End of 'V2_Final_Final'

Breaking Free from Local Files

In Articulate 360, projects are often trapped in local files (.story or .rise). This leads to version control nightmares and manual asset replacement. Claro operates as a cloud-native LCMS, meaning your content lives in a central environment accessible to your whole team.

Welcome. For years, Articulate users have managed projects through a fragmented, file-based workflow, juggling versions like 'V2_Final_Final'. In this lesson, we'll explore how Claro moves your entire production into a cloud-native LCMS, providing a single source of truth for your team.

The Single Source of Truth

The Centralized Media Library

Unlike desktop tools where assets are embedded into specific projects, Claro uses a Centralized Media Library. An asset exists as a standalone object linked to your pages.

In the Claro ecosystem, media isn't buried inside a project file. It lives in a Centralized Media Library. Think of it as a hub: one image can be linked to dozens of different courses. Because assets include metadata and tags, your team can search for existing media instead of re-uploading duplicates.

Simulation: The Branding Crisis

Global Update Challenge

Your organization has just updated its logo. Instead of opening every project file, use the Global Update feature to swap the asset once and push it everywhere.

Imagine your company undergoes a sudden rebrand. Usually, you'd have to open every single Storyline project and swap the logo manually. Click the library to upload the new logo and see what happens. Watch closely! By replacing the file in the library, every project using that logo is updated instantly. You've just saved hours of tedious manual labor.

Real-Time Collaboration

Multi-Author Power

In Claro, multiple authors can work in the same project at the same time. To prevent conflicts, the system uses page-level locking.

Collaboration in Articulate is often 'one person at a time.' In Claro, your whole team can dive in simultaneously. While you build an interaction on Page 1, a colleague can write content on Page 5. The system automatically locks the page you're editing and allows for real-time Page Notes to keep communication in-context.

Strategy Session: Optimizing Workflow

Transitioning Your Team

Talk to your lead developer about how to set up your new cloud-native environment. Consider permissions, tagging, and asset audits.

You're meeting with Sarah, your lead developer, to plan the migration. She wants to know how you'll keep the new library organized and how you'll handle team access. Discuss your strategy with her.

Avoiding Common Pitfalls

Smooth Sailing

Even with a powerful LCMS, teams can run into Ghost Locking or Asset Duplication. Establishing a team protocol is key.

To keep your environment efficient, watch out for two main pitfalls. First, 'Ghost Locking'—if an author leaves without committing, a page stays locked. Second, 'Asset Duplication'—where users upload the same image twice. The solution? Establish a check-in protocol and encourage your team to: Search first, upload second.