February 2026 Updates: Multi-user Workflow, Improved Tables & API Improvements

February may be the shortest month of the year, but it delivered meaningful improvements where they matter most, in the everyday workflows your team relies on.

This release focuses on real friction points: coordinating multiple reviewers within a single workflow stage, navigating large tables without losing context, and maintaining clean, consistent URLs across languages and workspaces.

These aren’t flashy features. They’re operational upgrades. The kind that makes collaboration clearer, data easier to manage, and your knowledge base more reliable.

When small inefficiencies disappear, documentation flows better for everyone.

▶️ Watch the February Feature Release video to get a quick walkthrough of all the new updates.

Workflow assignments made easy to handle multiple reviewers

Earlier, a workflow state can have only one assigned reviewer. When an article enters a stage, for example, Technical Review, the author must choose a single reviewer, even if the content requires validation from multiple stakeholders. In reality, the article may need input from a backend engineer to confirm API accuracy, a UI developer to verify screenshots, and a compliance reviewer to check regulatory language. Since only one reviewer can be assigned, the author either routes the article sequentially, causing delays, or coordinates feedback manually through comments, chat messages, or external trackers. The workflow displays one name, but the responsibility is shared across several people, creating gaps in visibility and accountability.

With this update, a single workflow state can now be assigned to multiple reviewers simultaneously. Workflow statuses support auto-assignment to multiple users or groups. Configure it once in the Workflow designer, and whenever an article moves to that status, all required reviewers are automatically assigned, with no repeated manual effort.

More importantly, the review progress is visible. Clear completion indicators show who has finished and who is still reviewing, eliminating guesswork and follow-ups. Teams can confidently move the article forward once all required inputs are complete.

For organizations with multi-department reviews or layered approvals, this removes the coordination bottleneck. The workflow finally mirrors how teams actually operate instead of forcing reviews through a single checkpoint.

Tables That Work Like You’d Expect Them To

Tables work well for structured data until they grow large enough to become difficult to navigate. Scroll down, and the column headers disappear. Scroll right, and you lose the first column that identifies each row. You end up scrolling back and forth just to regain context.

With this update, you can freeze one or more rows and columns in tables. Lock the header row so it remains visible while scrolling vertically. Freeze the first column to maintain row context. Or freeze both to navigate large tables without losing orientation.

The result is familiar spreadsheet-style behavior built directly into your documentation tables. Comparison tables, pricing matrices, technical specifications, or any data-heavy layout become easier to read and manage.

URLs That Stay Clean (And SEO That Stays Healthy)

You switch your knowledge base to another language, and the URL updates. That’s expected. But when you switch back to the default language, you don’t want a leftover slug hanging around. You want the clean, canonical URL.

When that doesn’t happen consistently, problems start piling up. Shared links look different depending on who copied them. Search engines may index multiple variations of the same page. Analytics splits traffic across duplicate URLs. What should be one authoritative page starts competing with itself.

That’s not just untidy. It’s an SEO risk.

With this update, the default workspace and default language always use clean canonical URLs. No extra slugs. No identifiers. Just the base structure. When you switch to a non-default language or workspace, the appropriate slug is added automatically. Switch back to the default, and it’s removed just as cleanly.

The result is consistency. Search engines see one primary version of your content. Duplicate indexing issues are reduced. Analytics reflect true traffic instead of fragmented numbers. And every shared link leads to a predictable, standardized structure.

It’s a backend refinement most users won’t consciously notice. But over time, you’ll see the impact in cleaner analytics, stronger indexing signals, and a knowledge base that behaves the way it should.

Stop Pulling Thousands of Articles When You Only Need 50

When you’re pulling article data from a specific documentation version, the current API returns everything in one response. Hundreds or thousands of articles come back at once, regardless of how many you actually need. Your integration processes the entire dataset just to extract a small subset. Response times slow down. Memory usage spikes. And you’re left parsing through far more data than necessary.

The Project Versions Articles API now supports pagination. You can control exactly how many results you get per page and navigate directly to the page you need. Want the 50 most recent articles? Set your page size to 50 and retrieve only that. Processing articles in batches of 100? Define your batch size and iterate through results efficiently without overwhelming your system. This matters when you’re working with large documentation projects. Faster API response times, controlled data retrieval, and the ability to request precisely what you need without massive payloads. The API maintains backward compatibility; if you don’t specify pagination parameters, it returns all results just like before. But when you need control over response size, the option is there. For teams building integrations or pulling version-specific article data programmatically, this gives you the precision and performance you need as your documentation scales.

Trigger Documentation Exports Through the API

Documentation exports are critical for backups, compliance, and distribution, but they shouldn’t require manual intervention every time. Logging in, clicking buttons, waiting, and downloading create unnecessary overhead when you’re managing documentation at scale. Now you can trigger offline documentation exports directly through the API. Automate the entire process. Schedule exports to run as part of your backup systems, compliance workflows, or publishing pipelines. No manual steps. No portal access required. Generate exports at the project, workspace, language, or category level, whatever scope makes sense for your workflow. The process runs consistently in the background, following the same reliable logic as manual exports while integrating seamlessly into your existing infrastructure. For teams managing large documentation sets or embedding Document360 into DevOps automation, regulatory processes, or distribution systems, this transforms exports from a manual task into automated infrastructure.

Updates That Enhance Daily Workflows

These improvements each address specific needs and together make the experience of working in Document360 smoother:

Eddy AI now searches strikethrough content. Previously, if you had text formatted with strikethrough in your articles, Eddy couldn’t retrieve it when answering questions. Now it can. This means more complete search coverage, even for content you’ve marked with strikethrough, which can now appear in Eddy’s answers when relevant.

Writing Agent style guides expanded to 25,000 characters. That means more room for detailed brand voice documentation, tone rules, terminology standards, and edge-case guidance, allowing the AI to reflect how your team actually writes, not a simplified version.

You can also link to hidden articles. If you’re building a structured series or drafting interconnected content, you no longer need to wait until everything is published to establish relationships. Create the links while articles are still hidden. When they go live, the connections are already in place, no revisiting or patchwork updates required.

Individually, each update solves a specific workflow challenge. Together, they strengthen search completeness, content structuring, and writing consistency, making the day-to-day experience in Document360 more seamless and predictable.

February Refined the Details

This month was about refinement. Workflows that reflect real team structures. Tables that behave like proper data tools. URLs that stay clean and SEO-ready. APIs that support automation at scale. And a series of smaller improvements that remove friction from everyday work. Major features attract attention. But precision is what makes a platform reliable. February was about precision. And that’s what elevates good software into something teams depend on.