Spotlight on RubyLaw: Content Locking

RubyLaw provides law firms, and specifically digital content managers, with a single source of truth—a place where the definitive record for content lives. 

As firms expand, the teams managing their marketing and business development content tend to grow, too. They might operate from distributed locations, work in different time zones, or speak dissimilar languages. Concomitantly, the types and volumes of content increase, demanding a more sophisticated software solution to ensure that everyone is ‘singing from the same hymn sheet’—even if they’re singing in differing tongues.

One such requirement is the ability to ‘lock content’, a key, value-add feature in RubyLaw 21, which reduces the potential for conflict. Intra-team collisions, or conflicts, may occur when multiple RubyLaw users find themselves attempting to update the same piece of content simultaneously. This could happen when team members are co-authoring an alert, a news item, a blog post, a lawyer’s bio, a matter—or any content managed within RubyLaw.

RubyLaw’s Content Locking function enables editors to quickly see which content is currently being edited by another user. In the event that a RubyLaw user attempts to modify a piece of content currently being edited, that person will see a visual warning and be prevented from overwriting another editor’s work. The integrity of that content is thereby preserved, and the source of truth for the firm’s marketing and business development content remains intact.