No Locks, No Limits: Collaborative Editing and API v3 Are Here

Documentation is a team effort, but most authoring tools still treat writing as a solo activity. One person opens an article, everyone else waits. Meanwhile, the systems around your knowledge base keep getting more automated, and an API that can’t reach the endpoint you need becomes its own kind of bottleneck.

This release addresses both. Real-time collaborative editing comes to the Advanced WYSIWYG editor, and API v3 rebuilds the public REST API from the ground up with permission-aware authorization. Alongside them: a redesigned Publish dialog, a new labels system for internal content organization, reader-group-level control over Eddy AI features, a unified navigation menu, and offline exports that finally look like your live site.

Here’s what’s new.

Collaborative Editing: No Locks, No Queue

For most teams, the bottleneck in documentation isn’t writing. It’s waiting. An article gets locked while one person works on it, a reviewer with feedback can’t get in, and a subject matter expert with ten free minutes has to come back later.

Collaborative editing in the Advanced WYSIWYG editor removes that queue. Multiple contributors can now work on the same article simultaneously, seeing each other’s cursors and edits as they happen, adding media, and leaving comments, with every change synced live. Reviewers no longer wait their turn either, they can review and comment while others keep editing.

Publishing stops interrupting the work, too:

• Contributors are notified when an article is published
• A new draft is created automatically so editing continues uninterrupted
• Enhanced version history shows who changed what
• Versions can be compared, and earlier content restored

Permissions, workflows, and review states all still apply, so you gain the speed of everyone working at once without losing the controls that keep your documentation trustworthy.

API v3: A Rebuilt API With Permission-Aware Keys

Automation around a knowledge base tends to start small, a script to bulk-update articles, a nightly job to sync users, and then quietly becomes infrastructure. At that point, endpoint coverage and permissions matter equally.

API v3 is a ground-up rebuild of Document360‘s public REST API, built for that reality. It significantly expands what you can automate, spanning content, users and roles, reader access, drive, and analytics, with a select set of advanced endpoints available as an optional add-on.

Authorization has been rebuilt around how integrations actually work:

• Apps acting on behalf of a signed-in user authenticate via OAuth 2.0
• Integrations and scripts use scoped API keys, each with a defined portal role, content role, and content scope
• New endpoints cover article management, user management, drive management, search, and analytics

The result is an API that’s permission-aware by design: a key can only do what its role and scope allow, so a single integration never needs the run of your whole project. We recommend upgrading for the broader coverage and built-in controls, but there’s no deadline, existing v1 and v2 integrations continue to work as-is.

See how Document360 helps your team write, review, and publish together

Book a Demo

A Publish Dialog That Catches Problems Before Readers Do

Publishing used to be the moment you discovered problems: a broken link nobody noticed, a comment left unresolved, metadata never filled in. Each one meant leaving the publish flow, fixing something elsewhere, and starting over.

The redesigned Publish dialog turns that scattered process into one streamlined workspace. Article metadata, publishing options, and AI-powered suggestions now sit in a single view, so you can review, refine, validate, and publish without leaving the dialog. Suggestions that miss the mark can be regenerated in one click with Auto Fix.

Before you publish, the dialog surfaces potential issues upfront, including:

• Broken links
• Unresolved comments
• Reader acknowledgement information

Publishing options live in the same place, publish immediately or schedule for a specific date and time, as do advanced settings such as Preferences and Search visibility.

The practical effect is that the dialog has become a checkpoint rather than a button. Everything you’d want to confirm before content reaches readers is visible at the moment you’d naturally confirm it, which means far fewer surprises after an article goes live.

Labels: The Organization Layer Your Readers Never See

Tags have always been reader-facing. What they can’t do is answer the questions your own team asks: which articles still need review? what’s gone stale, what ships with v3?

Labels are new in this release, and that’s what they’re for, an internal organization layer that lives entirely in the portal and is never visible to readers. Apply a label such as needs-review, outdated, or release-v3 to an article, then filter your entire knowledge base down to that set from the All articles page. Content audits, release tracking, and bulk review all get considerably less manual.

Labels ship with their own housekeeping from day one:

• Manage labels lets Owners and Admins create, rename, group, and delete labels and label groups, move or delete in bulk, and see a label’s usage count before removing it
• Full portal search surfaces any label alongside its dependency count in articles and page categories
• The Label references panel lists every article and page category using a label, with its contributor and last-updated date, and removes stale references in one pass

Eddy AI Access, Now Per Reader Group

One knowledge base often serves several very different audiences. Internal teams, partners, trial users, and enterprise customers may all read the same site, but they don’t all need, or all warrant, the same AI capabilities.

You can now control which reader groups can use specific Eddy AI features on your knowledge base site. The new Restrict access option lets you exclude selected groups from individual features rather than switching AI on or off wholesale.

Features you can restrict per reader group:

• AI assistive search (Ask Eddy)
• AI article summarizer
• Dynamic related article recommendation
• MCP server
• Listen (text to voice)

Restricted features are hidden for those readers across the site, while every other group keeps full access by default, so nothing changes for your existing audiences unless you choose to restrict them.

That granularity matters most where AI access is a commercial or compliance question rather than a technical one. For teams currently maintaining separate sites purely to differentiate AI access, one workspace can now serve all of them.

One Dropdown for Projects, Workspaces, and Languages

As projects multiply, so does the clicking. Moving from one project’s workspace to a different language in another project meant working through separate menus to get there.

The redesigned top and left navigation bars replace that with a single unified dropdown. Projects appear at the top, with their workspaces and available languages organized in an expandable hierarchy, so your full structure is visible at a glance instead of discovered one menu at a time.

What the redesign changes:

• Projects, workspaces, and languages all switch from one dropdown in the top navigation
• Manage projects and Manage Workspace & language are reachable directly from that same dropdown
• The left navigation bar expands to show item names when you need context, and collapses when you’d rather have the space

It’s a smaller change than collaborative editing, but one you’ll touch dozens of times a day, and the compound effect of not hunting through menus is easy to underestimate until it’s gone.

Offline Exports That Look Like Your Knowledge Base

Exported documentation often travels furthest, into air-gapped environments, onboarding packets, and offline reading, and it should still feel like your knowledge base rather than a stack of loose files.

Offline and Web Help exports now match your live site far more closely, closing several gaps in exported content and improving both readability and usability. Navigation travels with the export as well: articles include the table of contents, breadcrumbs, and previous/next links, so readers can move through your documentation instead of getting stranded.

Formatting and structure hold up much better:

• H1 and H2 headings render at distinct sizes, preserving hierarchy
• Markdown articles in right-to-left (RTL) languages keep the correct text direction and layout
• Snippet-embedded images retain their original display size, and glossary definitions and links are preserved
• Exports use the same font family as your live knowledge base
• Code blocks include a copy button that works without an internet connection

Together these turn an export from an approximation of your documentation into something much closer to the real thing.

Other Improvements

This release also includes a broad set of smaller enhancements across the portal and knowledge base site:

• Redesigned status icons. Article and page category status indicators have been redesigned for clarity. When a published article has an active draft, the icon itself now reflects that state with a dual-tone design, replacing the yellow dot shown alongside the title.
• Smart bar redesign. The Smart bar experience adds a live preview, an improved creation panel, a language selection dropdown, bulk actions, and a duplicate option.
• Ticket deflector is now Get help. The page has been renamed on the knowledge base site, with the new name reflected in the page URL and breadcrumb navigation. Existing bookmarks and links continue to work automatically.
• Dark theme for offline documentation. Offline documentation now supports dark theme for more comfortable reading.
• Step-by-step guides for AI agents and LLMs. Step-by-step guides are now structured for AI agents and LLMs to read and understand.
• None option for AI chatbot sources. The Content access configuration dropdown now includes a None option, so knowledge base content is no longer mandatory and a chatbot can draw solely on other configured sources.
• Widget configuration reorganized. The Widget configuration page regroups fields and tabs for a clearer layout.
• UI refinements. The Article settings, Localization variables, My profile, and Change Password pages all have an improved UI for easier navigation.
• Platform improvements. Minor security updates, bug fixes, and performance improvements across the Knowledge base portal and Knowledge base site.