DEV Community: NocoBase

How to Build a Production-Ready IT Operations System with AI and NocoBase

NocoBase — Tue, 18 Aug 2026 07:50:34 +0000

Originally published at https://www.nocobase.com/en/blog/build-it-operations-system-with-ai-nocobase

Introduction

A recent post in Reddit's r/sysadmin described how one user built an ITSM system with AI over a weekend, covering both ticketing and asset management. In actual use, they found it more convenient than many products they had used before.

The comments also raised a different view: AI can quickly generate a Help Desk that looks mature, but that does not mean it already has the data structure, permissions, security, and extensibility required for production use.

In our previous article, Enterprise IT Asset Management System Guide: From Requirements to Implementation, we introduced a way to design an IT asset management system: let AI understand and break down business requirements, let NocoBase provide the data, permissions, and automation capabilities, and then have people review and adjust the system against real business rules. This combines AI's efficiency in understanding requirements and generating systems with the data, permissions, security, workflows, and other foundations that enterprise applications actually need.

💬 Hey, you're reading the NocoBase blog. NocoBase is the most extensible AI-powered no-code/low-code development platform for building enterprise applications, internal tools, and all kinds of systems. It’s fully self-hosted, plugin-based, and developer-friendly. → Explore NocoBase on GitHub

This time, we will take that approach further and focus more on efficiency. In about two hours, we will use AI and NocoBase to build a more complete IT operations system from scratch. It will cover IT asset inventory, device assignment and return, service catalog and service requests, device approval and delivery, maintenance management, software license management, an AI IT assistant, an operations knowledge base, and dashboards. We will also improve permissions, workflows, and data synchronization so the system can be used in production and continue evolving with business needs.

🚀 Try applications built with NocoBase + AI online and see what AI-assisted application building looks like in practice: https://demo.nocobase.com/new

All screenshots in this article come from the NocoBase online Demo. The entire system, from design to implementation, was completed by an AI Coding Agent.

1. Start by Designing Around the Core Business Process

You are the IT administrator at a mid-sized company. The company has both office-based and remote employees and needs to manage laptops, monitors, phones, printers, servers, network devices, and other office peripherals.

Employees regularly request new laptops, monitors, software licenses, VPN or remote-access permissions, and they also report password, MFA, device, and other IT issues. These requirements can eventually involve asset management, service requests, approvals, maintenance, software licenses, a knowledge base, permissions, and dashboards.

But there is no need to put every scenario into the first version. We will start with one of the most common workflows:

Employee requests a laptop → Manager approves → IT selects a device and completes delivery

Let AI Understand the Requirements First

Once the business scenario and first-stage scope are clear, give the requirements to AI so it can understand the company's IT work and design the first version around laptop requests and delivery.

You can use the following prompt:

Please help me build an internal IT operations system in NocoBase.

The company has both office-based and remote employees and needs to manage laptops,
monitors, phones, printers, servers, network equipment, and other office peripherals.

Common IT requests include new laptop requests, monitor or peripheral requests,
software license requests, VPN / remote access, password or MFA issues,
and meeting-room equipment support.

Devices may go through registration, inventory, available for assignment, assigned to an employee,
in use, under maintenance, returned, reassigned, or retired. Employee requests may require
manager approval before IT completes delivery.

For the first stage, only build:
- Employees;
- Asset inventory;
- Device assignment and return records;
- Service catalog;
- Service requests;
- Laptop request and delivery workflow.

Maintenance, software licenses, operations manuals, reminders, and operational reporting
will be added later. Keep room for them, but do not create them yet.

Regular employees can submit and view their own requests; managers handle requests
that require approval; IT administrators maintain assets and complete device delivery.

Please return first:
1. The core data needed in the first stage;
2. How the data should be related;
3. How a laptop request should move through delivery;
4. Which pages and workflows you plan to create;
5. Which business rules still need confirmation.

Do not create anything yet. Wait for my confirmation before building.

Check AI's Understanding of the Business Rules

Before AI starts creating the system, confirm that it has correctly understood these five key rules:

One employee can be associated with multiple devices;
One device has a clear current user;
The asset's current status and historical assignment records are stored separately;
After a service request is approved, the actual device still needs to be delivered;
When the device is delivered, the asset information and assignment record are updated together.

The rule most likely to be missed is:

An approved service request does not mean the device has already been delivered.

For a new laptop request, approval only means the request has been accepted. IT still needs to select an actual device, assign it, update the asset status, and save the assignment record.

If AI treats “request approved” as the end of the workflow, ask it to add the IT processing and device delivery steps before creating the system.

For guidance on collaborating more effectively with an AI Agent, see: https://docs.nocobase.com/ai-builder/ai-portal/agent-workflow

2. Build and Check the Core Workflow

After confirming the business rules above, let AI create the first-stage system based on the agreed design. Once it is generated, start from the laptop request workflow and verify step by step that assets, assignment records, service requests, and device delivery work together correctly.

Check the Asset Inventory

When an employee is preparing to request a laptop, IT first needs to know what devices exist and which ones are currently available. Start by checking the asset inventory.

The asset inventory should at minimum record asset ID, serial number, device category, device name, model, location, current user, warranty expiration date, and current status.

You can verify asset status against the following flow:

In inventory → Available → Assigned → In use → Under maintenance / Retired

Here, “Assigned” means IT has selected and allocated the device, but the employee has not formally started using it yet. After delivery is completed, the status changes to “In use.”

The asset inventory mainly answers three questions: what is this device, who is using it and where, and can it still be assigned?

Check the following points carefully:

Asset IDs must be unique to prevent duplicate registration;
Devices under maintenance or retired must not appear in the available-device list;
Assigned or in-use devices must have a clear current user so the same device is not assigned twice.

Also verify the employee-device relationship. One employee may use multiple devices at the same time, such as a laptop, monitor, and phone, while one device should have only one current user at a given time. The employee detail page should directly show all devices assigned to that employee.

After the first-stage system is generated, enter three test devices: one “Available,” one “In use,” and one “Under maintenance.” Then filter for “Available” devices. Only the first device should appear, confirming that the status and filtering rules work.

Record Every Device Assignment and Return

The asset inventory records who currently uses a device, but past assignments and returns need to be stored separately. Therefore, the system also needs a dedicated device assignment and return record linked to both the device and the employee.

Each record should at minimum include the device, assigned employee, assignment time, return time, return condition, operator, and notes.

These two data types serve different purposes: the asset inventory stores the current state of the device, while assignment and return records preserve the history of each device movement.

Next, simulate a complete device lifecycle:

Assign to Employee A → Employee A returns it → Reassign to Employee B

Afterward, check that:

The current user on the asset detail page is Employee B;
Employee A's original assignment and return history is still preserved;
The device no longer appears in Employee A's current-device list, but does appear in Employee B's list.

3. Extend IT Operations Capabilities on Top of the Core Workflow

Once the laptop request and delivery workflow works end to end, the system already has the basic data for assets, service requests, approvals, and device movement. Next, give the follow-up requirements—device maintenance, software licenses, AI assistance, and operations manuals—to AI and let it extend the existing system. Afterward, test each new capability against a real business scenario.

NocoBase AI Builder lets AI design, build, and continue adjusting enterprise applications from natural-language requirements: https://docs.nocobase.com/ai-builder

A Device Breaks — Add Maintenance Management

Devices can fail after delivery. Once maintenance management is added, IT can create a maintenance record for the original device and save the problem description, date sent for repair, service provider, repair cost, maintenance status, and result.

When a device enters maintenance, the asset status must change as well:

In use → Under maintenance → In use / Available / Retired

If the repaired device goes back to the same employee, restore its status to “In use.” If it returns to inventory, set it to “Available.” If it can no longer be used, set it to “Retired.”

After creating a test maintenance record, first verify that the linked asset automatically changes to “Under maintenance” and disappears from the available-device list so it cannot be assigned again while being repaired.

When maintenance is complete, separately test the three outcomes—“return to original employee,” “return to inventory,” and “retire device”—and confirm that the asset status matches the maintenance result.

More Software Requests — Manage Software Licenses

As the number and variety of software products grow, IT needs to know how many seats have been purchased, how many are already in use, when each license renews, and the annual cost. The system therefore also needs software license management.

Each software record should store the vendor, total seats, used seats, renewal date, annual cost, and current status. When handling a software request, first check whether seats remain available, then update the used-seat count after activation is completed.

These rules can also be handed to AI and automated through NocoBase Workflow. For example, notify the owner and create a renewal task when a license is about to expire; if used seats exceed total seats, trigger an overage alert and let AI assist in deciding whether to expand capacity or reclaim accounts.

Employees Cannot Explain the Problem Clearly — Let AI Structure the Request

Employees do not always know which service to choose, and they may not describe an issue in the format IT prefers. For example:

After resetting my password, I cannot connect to VPN and need access before today's customer call.

Employees can describe the issue in natural language and let AI turn it into a request title, service type, priority, and problem description. The employee can review or edit the result before formally submitting the request.

Use the example above as a test and confirm that the service type, priority, and description produced by AI can still be edited and submitted normally. This way, employees can describe issues in their own words while IT still receives a structured request that can be categorized and processed.

Repeated Problems — Build an Operations Knowledge Base

Issues involving VPN, MFA, new-laptop setup, and printer failures occur repeatedly. Verified solutions can be organized into operations manuals that record purpose, prerequisites, procedures, validation steps, and exception handling.

As the knowledge base grows, AI can also help IT find the relevant procedure based on the content of a request.

4. Validate the System with a Complete Workflow

Check Whether Everything Stays in Sync

By this point, the system contains asset, service request, assignment, maintenance, and software-license data. The operations dashboard can summarize available devices, devices in use, pending requests, devices under maintenance, license utilization, licenses approaching renewal, and software costs.

The dashboard data comes directly from the asset, service request, maintenance, and license records built earlier.

Change a device status, complete a service request, or add a maintenance record, then confirm that the related dashboard metrics update accordingly. Clicking a metric should also allow users to view the matching details.

Validate the Full Process from Request to Return

Finally, return to the employee used in the earlier tests and run through the whole process again:

Request laptop → AI-assisted form filling → Manager approval → IT selects device → Create assignment record → Employee starts using device → Maintenance / Return → Asset status updates → Operations dashboard updates

After completing the process, verify these points:

Are the current user and asset status accurate?
Are assignment, return, and maintenance histories fully preserved?
Can the service request be traced back to the actual delivered device?
Do employee, manager, and IT viewing and operation permissions match the design?
Do status updates, reminders, and other automations execute correctly?
Can AI-structured requests be edited and submitted normally?
Do the related dashboard metrics update with business-state changes?

Once these data and workflow behaviors match the business rules defined earlier, the system can first be released to a small group of users and then adjusted based on real feedback.

Conclusion

If you already have a clear business scenario, start with the workflow your team knows best. Describe the real requirements, team roles, and handling process directly to AI, then let NocoBase provide the data, permissions, and other enterprise application foundations. Build, check, and adjust as you go. Get the core business process working first, then expand the system gradually based on actual use.

If this article was useful, feel free to share it with others who are exploring how to use AI to build internal enterprise systems.

Related reading:

Weekly Updates: Added Default Space Settings with Automatic User Assignment

NocoBase — Mon, 17 Aug 2026 09:27:16 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.1.41

Release date: 2026-08-16

🚀 Improvements

[lock-manager] Added renewable local lock leases and ensured try-acquired locks are released safely across reuse and errors (#10368) by jiannx
[Redis lock adapter] Added renewable Redis lock leases and made reusable lock handles release safely during contention and errors by jiannx

🐛 Bug Fixes

[File manager] Fix the extra submit step when selecting an existing file in a single-value field (#10372) by zhangzhonghe
[Collection field: Markdown(Vditor)] Fix Markdown HTML previews in v2 details blocks under dark themes. (#10370) by katherinehhh
[Collection field: Encryption] Fixed bulk import failing with model.changed is not a function when the collection contains an encryption field by cgyrock
[Workflow: Webhook] Fixed a 400 error when manually executing a webhook workflow without request headers by mytharcher

v2.1.40

Release date: 2026-08-14

🚀 Improvements

[Block: Tree] Tree filter blocks now support configurable default sorting. (#10339) by jiannx

🐛 Bug Fixes

[client-v2]
- Fix filter forms refreshing automatically in UI edit mode (#10356) by zhangzhonghe
- Use Cascader by default for tree-structured relation fields in v2 filter forms (#10357) by zhangzhonghe
- Fix mobile single-select relation fields not clearing when the selected record is tapped again (#10346) by zhangzhonghe
- Fix the issue where China region fields cannot be added directly to filter forms (#10333) by zhangzhonghe
- Fix JS items incorrectly appearing in form field linkage rule actions (#10363) by gchust
[Workflow: JSON calculation] Fixed JSON Query jobs losing structured parser errors and displaying [object Object] (#10344) by mytharcher
[Action: Export records]
- Fixed a page crash when sorting an edited relation field in Export V2. (#10335) by katherinehhh
- Fix table export errors after filtering by multiple relation fields (#10342) by zhangzhonghe
[Block: Kanban] Fixed configured content disappearing after reopening a kanban card's detail drawer (#10334) by jiannx
[File manager] Fixed video previews not updating when switching between files (#10345) by mytharcher
[Action: Import records Pro]
- Fixed asynchronously imported records not being associated with the current space by jiannx
- Clarified import results by showing the number of newly created records separately from updated records by mytharcher
[Workflow: Approval]
- Fix inconsistent subtable column widths in approval details by zhangzhonghe
- Add data scope filtering to Client V2 related approval blocks by zhangzhonghe

v2.1.39

Release date: 2026-08-11

🐛 Bug Fixes

[client-v2] Fixed an issue where ctx.form.submit could not correctly submit form data. (#10063) by gchust
[database] Fixed prefix indexes on camel-case fields when underscored database naming is enabled (#10329) by 2013xile
[Action: Duplicate record] Improve direct duplication failure feedback in v2 without duplicate API error messages. (#10327) by katherinehhh
[Record history] Improved record history write performance for collections with large snapshot tables by 2013xile
[Workflow: Approval] Fix the issue where removed one-to-many relation records cannot be selected again in approval forms by zhangzhonghe

v2.1.38

Release date: 2026-08-10

🚀 Improvements

[undefined] Clarified the default JavaScript Worker concurrency behavior and when to configure a concurrency limit (#10317) by mytharcher Reference: JavaScript node
[Workflow: JavaScript] JavaScript workflow nodes now queue asynchronous Worker execution and limit per-process Worker concurrency to reduce resource spikes. (#10280) by mytharcher

🐛 Bug Fixes

[Flow engine]
- Fixed popup record variables and association blocks for custom non-Sequelize data sources (#10272) by gchust
- Fixed incorrect variable resolution for form field values (#10319) by gchust
[File manager] Fixed file downloads failing after previewing cross-origin images when browser cache entries lack CORS response headers (#10313) by mytharcher
Reference: File Preview / Aliyun OSS

v2.2.0-beta.17

Release date: 2026-08-10

🎉 New Features

[client-v2] Add Date variables and optional formatted output to V2 field-value editors. (#10289) by katherinehhh
[AI employees]
- AI employees can now be assigned skills from the employee settings page. Skills are built from plugins. (#10237) by cgyrock
- Added UI navigation for supported LLM service CLI commands, including provider preselection when creating a service. (#10210) by cgyrock
[Multi-space] Added default-space configuration so newly created users automatically join the selected default space. by jiannx
[AI: Knowledge base] Added UI navigation for creating and editing vector databases from CLI commands, with provider preselection for new databases. by cgyrock

🚀 Improvements

[undefined] Clarified the default JavaScript Worker concurrency behavior and when to configure a concurrency limit (#10317) by mytharcher Reference: JavaScript node
[Workflow: JavaScript] JavaScript workflow nodes now queue asynchronous Worker execution and limit per-process Worker concurrency to reduce resource spikes. (#10280) by mytharcher
[Action: Export records] Add field search to v2 import and export action settings. (#10261) by katherinehhh
[Action: Batch update] Support configurable after-success behavior for v2 Update record and Bulk update actions. (#10278) by katherinehhh
[Workflow: HTTP request node] Fix unstable test cases (#10246) by mytharcher
[Workflow] Workflow create and update nodes now support combining text with variables when assigning string and text fields (#10238) by mytharcher
[Action: Export records Pro] Add field search to v2 Import Pro and Export Pro action settings. by katherinehhh
[AI: Knowledge base] Aligned the vector database list styling with other settings tables by cgyrock

🐛 Bug Fixes

[client-v2]
- Fixed Kanban column quick create records not inheriting the selected group value (#10321) by jiannx
- Fix missing and incorrectly resolved Current popup parent record variables in v2 popup-subtable add-new and edit dialogs. (#10292) by katherinehhh
- Fixed parent item variables resolving to the wrong level when assigning association field values in sub-tables. (#10249) by gchust
- Fix the cancel button language in mobile selection lists (#10297) by zhangzhonghe
- Fix missing Current record variables in v2 JS column event-flow conditions. (#10279) by katherinehhh
[database]
- Fixed migration packages omitting many-to-many through-table data after an application restart (#10306) by cgyrock
- Fixed MSSQL queries failing when filtering to-many relations with pagination and sorting by a root collection field (#10224) by cgyrock
[data-source-manager]
- Fixed formula fields being converted to number fields after synchronizing fields from the database (#10303) by 2013xile
- Fixed external data source table synchronization leaving removed collections registered in the database manager (#10209) by cgyrock
[auth] Fixed occasional Invalid CSRF token errors on API requests in cross-origin deployments (#10245) by mytharcher
[Block: Tree] Fixed Tree block searches showing placeholder nodes when no business-field records matched (#10323) by jiannx
[Block: Gantt] Fixed custom record colors not being applied to short Gantt task bars (#10322) by jiannx
[Flow engine]
- Fixed incorrect variable resolution for form field values (#10319) by gchust
- Fixed popup record variables and association blocks for custom non-Sequelize data sources (#10272) by gchust
[Backup manager]
- Prevent repeated V2 backup restore submissions while a restore request is in progress. (#10262) by katherinehhh
- Fix duplicate backups from async exports (#10300) by gchust
[Data source manager] Prevented clearing a field interface directly from the Configure fields table. (#10288) by hongboji
[File manager]
- Fixed file downloads failing after previewing cross-origin images when browser cache entries lack CORS response headers (#10313) by mytharcher Reference: File Preview / Aliyun OSS
- Fixed shared attachments such as the system logo not loading for authenticated member users (#10268) by mytharcher
[Collection field: Sequence] Fixed duplicate automatic sequence values after migration when multiple records share the latest creation time (#10239) by mytharcher
[AI employees]
- Fixed the untranslated Settings tab in the AI plugin's client-v2 settings pages (#10234) by cgyrock
- AI employee actions now support linkage rules for conditional visibility in v2 forms. (#10298) by jiannx
[UI templates] Fix the issue where table blocks load data after returning to a page with empty filters (#9890) by zhangzhonghe
[Localization] Fixed a crash when opening Localization settings with the Lina AI assistant entry. (#10293) by cgyrock
[Workflow] Fixed an issue where manually executing a workflow with autoRevision=0 could still create a new revision. (#10243) by mytharcher
[Workflow: JavaScript] Fixed JavaScript workflow Workers not exiting after scripts returned or asynchronous workflows timed out (#10241) by mytharcher
[Data source: External NocoBase] Fixed external NocoBase files and attachment fields failing to load in AI workflows by 2013xile
[Data source: External SQL Server] N/A — regression test coverage only by cgyrock
[Data source: External MySQL] Fixed previously selected external database tables disappearing after adding new tables. by cgyrock
[AI: Knowledge base] Fixed PGVector knowledge base searches consuming unused PostgreSQL pool connections and creating duplicate pools for different vector tables. by cgyrock
[Migration manager] Fixed many-to-many through-table migration data after application restarts and classified migration rules as system data by cgyrock
[Template print]
- Fixed unwanted spacing between Latin and East Asian text in PDF files generated from DOCX templates. by jiannx
[Workflow: Approval]
- Fix missing external data source fields in approval views by zhangzhonghe
- Fix missing field values in approval sub-tables by zhangzhonghe
- Fix approval comment default values when using RunJS by zhangzhonghe
- Fix the issue where removed one-to-many relation records cannot be selected again in approval forms by zhangzhonghe
- Allow approval comments to use configurable default values by zhangzhonghe
[App supervisor] Prevented app creation with database identifiers that do not start with an English letter or contain unsupported characters. by hongboji
[DingTalk] Fixed DingTalk notification channels losing the selected authenticator when saved from the v2 channel form by jiannx
[Auth: LDAP] Fixed LDAP login when a user DN mixes UTF-8 escapes with escaped syntax characters such as commas. by hongboji

develop

v3.0.0-alpha.9

Release date: 2026-08-11

🚀 Improvements

[cli] nb api resource create now accepts a JSON array for --values to create multiple records in a single request. (#10325) by Molunerfinn Reference: nb api resource create

🐛 Bug Fixes

[client-v2]
- Fix incorrect editing and display of large decimal values in V2 fields. (#10330) by katherinehhh
- Fixed an issue where ctx.form.submit could not correctly submit form data. (#10063) by gchust
- Automatically redirect to an accessible Settings tab when the current tab is unavailable (#10332) by zhangzhonghe
- Fixed Kanban column quick create records not inheriting the selected group value (#10321) by jiannx
- Redirect users without Settings access to the first available page (#10331) by zhangzhonghe
[database] Fixed prefix indexes on camel-case fields when underscored database naming is enabled (#10329) by 2013xile
[Block: Gantt] Fixed custom record colors not being applied to short Gantt task bars (#10322) by jiannx
[Block: Tree] Fixed Tree block searches showing placeholder nodes when no business-field records matched (#10323) by jiannx
[Action: Duplicate record] Improve direct duplication failure feedback in v2 without duplicate API error messages. (#10327) by katherinehhh
[Record history] Improved record history write performance for collections with large snapshot tables by 2013xile
[Workflow: Approval]
- Fix missing return scope options in Client V2 approval forms by zhangzhonghe
- Fix the issue where removed one-to-many relation records cannot be selected again in approval forms by zhangzhonghe
[DingTalk] Fixed DingTalk notification channels losing the selected authenticator when saved from the v2 channel form by jiannx

v3.0.0-alpha.8

Release date: 2026-08-10

🎉 New Features

[client-v2] Add Date variables and optional formatted output to V2 field-value editors. (#10289) by katherinehhh
[Portal manager] Show an access denied message when users do not have permission to access a Portal (#10275) by zhangzhonghe
[Connect coding agent] Copy a ready-to-paste prompt from an AI Portal card to connect a coding agent to the instance by Albert-mah

🚀 Improvements

[undefined]
- Clarified the default JavaScript Worker concurrency behavior and when to configure a concurrency limit (#10317) by mytharcher Reference: JavaScript node
- Add a model selection guide with evaluation dimensions and a color-coded model comparison table. (#10295) by Charls-Wu
[cli] fix: incorrect author identity in nb portal push commits (#10315) by gchust
[Portal manager]
- Improve Portal access check efficiency (#10302) by zhangzhonghe
- Show a concise placeholder when Portal access cannot be configured directly (#10301) by zhangzhonghe
[Workflow: JavaScript] JavaScript workflow nodes now queue asynchronous Worker execution and limit per-process Worker concurrency to reduce resource spikes. (#10280) by mytharcher
[Verification] Add a refresh button to the Verification settings list (#10299) by zhangzhonghe

🐛 Bug Fixes

[client-v2]
- Show loading feedback when enabling or disabling plugins (#10310) by zhangzhonghe
- Hide the retry button while the app is running a command (#10290) by zhangzhonghe
- Fix the cancel button language in mobile selection lists (#10297) by zhangzhonghe
- Fixed parent item variables resolving to the wrong level when assigning association field values in sub-tables. (#10249) by gchust
- Fix missing and incorrectly resolved Current popup parent record variables in v2 popup-subtable add-new and edit dialogs. (#10292) by katherinehhh
[database] Fixed migration packages omitting many-to-many through-table data after an application restart (#10306) by cgyrock
[data-source-manager] Fixed formula fields being converted to number fields after synchronizing fields from the database (#10303) by 2013xile
[undefined] fix the issue unable to create portal from local (#10304) by gchust
[Flow engine]
- Fixed incorrect variable resolution for form field values (#10319) by gchust
- Fixed popup record variables and association blocks for custom non-Sequelize data sources (#10272) by gchust
[AI employees]
- Fixed the AI employee chat entry briefly appearing while a page is loading or redirecting. (#10309) by cgyrock
- AI employee actions now support linkage rules for conditional visibility in v2 forms. (#10298) by jiannx
[File manager] Fixed file downloads failing after previewing cross-origin images when browser cache entries lack CORS response headers (#10313) by mytharcher
Reference: File Preview / Aliyun OSS
[Action: Batch edit] Corrected built-in plugin documentation to show that these plugins are enabled by default (#10314) by hongboji
[Portal manager]
- Fix compatibility issues when older AI Portals check access permissions (#10307) by zhangzhonghe
- Fix incorrect Portal URLs when the name is x or v (#10305) by zhangzhonghe
- Keep Portal titles unchanged in role permissions (#10291) by zhangzhonghe
[Backup manager] Fix duplicate backups from async exports (#10300) by gchust
[Workflow] Disable workflow execution mode selection until a trigger type is selected. (#10296) by Molunerfinn
[Data source: External NocoBase] Fixed external NocoBase files and attachment fields failing to load in AI workflows by 2013xile
[Migration manager] Fixed many-to-many through-table migration data after application restarts and classified migration rules as system data by cgyrock
[Workflow: Approval]
- Fix approval application cards not showing submitted content immediately by zhangzhonghe
- Align the V2 approval message template page with the V1 layout and actions by zhangzhonghe

NocoBase vs Baserow: Flexible Databases vs Enterprise Systems

NocoBase — Wed, 12 Aug 2026 11:47:35 +0000

Originally published at https://www.nocobase.com/en/blog/nocobase-vs-baserow

Introduction

If you are looking for an open-source, self-hosted platform to manage data, build internal applications, or automate business processes, NocoBase and Baserow are likely to appear on the same shortlist.

Both products provide visual data management and application-building capabilities, and both let teams extend the platform around their own needs. But judging only by these shared labels can make them look more similar than they really are.

In practice, Baserow and NocoBase represent two different product directions.

Baserow represents the spreadsheet-style no-code approach. Its first priority is helping teams organize, manage, and collaborate on structured data in a more flexible and intuitive way.

NocoBase starts from business-system development. It combines data models, pages, role-based permissions, workflows, and automation to help teams build enterprise applications that can run for the long term and continue evolving.

As AI Agents move into real business scenarios, these capabilities are also becoming infrastructure for AI to access enterprise data, invoke business processes, and perform tasks within defined permission boundaries.

This article therefore looks at the products from the perspective of actual usage and answers a practical question: when is a spreadsheet-style no-code platform such as Baserow the better fit, and when should you choose NocoBase instead?

Baserow: A Spreadsheet-Style No-Code Platform

Baserow was started by Bram Wiepjes as a personal project in 2019. Its first version was released in 2020, when the team also began to take shape. Today, its GitHub repository has around 5.3k Stars.

Baserow first gained attention as an open-source Airtable alternative. Its most recognizable experience still starts from a familiar model: create and manage structured data as easily as working in a spreadsheet.

Products in this category are often described as multidimensional spreadsheets, online databases, or spreadsheet-database tools. Besides Baserow, Airtable, NocoDB, Grist, SeaTable, and Feishu Bitable follow a similar approach.

NocoBase: Business-System Infrastructure for the AI Era

The NocoBase GitHub repository has now surpassed 23k Stars. NocoBase is an open-source AI + no-code platform for rapidly building business systems, but its role goes beyond visual application building. It provides infrastructure for people and AI Agents to build, run, and continuously extend business systems together.

In NocoBase, the data model is the foundation, but the final product is not simply a set of tables for users to maintain directly. It is a complete business system that can include:

Business pages designed for different roles
Data scopes and actions available to different users
Forms, detail pages, and business operations
Approvals, state transitions, and automated workflows
Operation records and audit logs
AI Employees that participate in business processing inside the system
APIs, MCP, CLI, and Skills for external AI Agents
Plugins and integrations that continue to grow with enterprise requirements

These capabilities support not only traditional business applications but also the context and execution boundaries AI needs in enterprise environments. AI Coding Agents can participate in data modeling, page configuration, permission setup, workflow orchestration, and plugin development. AI Employees inside the system and external Agents can query data, trigger workflows, and execute tasks within predefined permissions, while their operations remain subject to access control and auditing.

Ordinary users typically work through configured pages, forms, and actions instead of interacting directly with underlying tables. System builders can continue changing data models, pages, permissions, and workflows, while AI Agents can participate in building and iteration on top of the same architecture.

Core Difference 1: Creating a Database or Building a Business System

Both Baserow and NocoBase are based on data models, and both let users visually create fields, relationships, and application pages.

But they start from different places in actual use.

Baserow: start by creating a database and manage data collaboratively in a more flexible way.
NocoBase: start by identifying business objects, roles, and processes, then combine them into a complete business system.

Both products can create tables, relationships, and application pages, but their most natural end results are different.

With Baserow, a team will typically end up with a table-centered collaborative workspace:

Clear data structures
Direct editing
Flexible views
Easy bulk maintenance
Fast adaptation to changing needs

With NocoBase, a team will more naturally end up with an application system centered on business roles and processes:

Users work through dedicated business pages
Different roles have different permissions
Data changes are governed by operation rules
State changes can trigger approvals and workflows
New modules can be added as the business grows

In Baserow, the database itself is often the team's primary workspace.

In NocoBase, the database is more often the underlying foundation of a business system, while ordinary users interact with data through pages, forms, buttons, and workflows.

Core Difference 2: Editing Data or Completing Business Operations

Baserow and NocoBase both support tables, forms, and application pages, but ordinary users interact with data differently.

Baserow: users typically enter a table view to view, filter, and bulk-edit records. Grid View remains its most representative data-management interface.
NocoBase: users typically complete work through business pages, forms, and action buttons. Buttons can also trigger workflows that control subsequent data processing and business steps.

For example, consider updating a customer record.

In Baserow, users can click a cell and change the value directly. This is efficient for quick maintenance and bulk editing.

In NocoBase, once the data model is defined, the frontend can be organized much more freely. Teams can build pages around different roles and business scenarios, and AI can also help configure those pages.

For the same customer-status change, a team could use an action button on the customer detail page, or organize customers in a Kanban board and move cards between statuses. Each record can still open into a detail page for full information and editing.

This means the same underlying data and business rules can be presented through different pages and interactions depending on how the work is actually performed.

The two approaches fit different situations:

Spreadsheet-style tools emphasize directness, speed, and flexibility.
Business systems emphasize explicit operation entry points, validation, and process control.

When users are changing a content plan or a task note, direct editing is often more efficient.

But when they are changing an order amount, inventory quantity, contract status, or approval result, enterprises often need users to complete an explicit business operation rather than directly change underlying data.

For collaborative data tools, saving one click can improve efficiency. For formal business systems, adding one confirmation step may reduce the cost of mistakes.

Core Difference 3: Small-Team Collaboration or Enterprise Multi-Role Use

Baserow and NocoBase both support multi-user collaboration and permission management, but their typical collaboration models differ.

Baserow: better suited to teams collaborating around the same set of data through different views, filters, and record editing.

NocoBase: better suited to multiple departments and roles working in the same system, with different pages, data scopes, and operation permissions for each type of user.

For example, in a sales-management application:

Sales representatives can only view and edit customers assigned to them.
Sales managers can view the entire team's data and approve discounts.
Finance users can only access contracts, invoicing, and payment information.
Management can view aggregated data without directly editing business records.

In NocoBase, data permissions can also be controlled down to the row level for finer-grained access management.

Building the Same Business Scenario with Baserow and NocoBase

Consider the same CRM scenario in both products.

Assume the system needs to manage customers, contacts, sales opportunities, and follow-up records while supporting sales-stage management, owner assignment, and sales reporting.

Both products can build this CRM, but the resulting usage model will differ.

Baserow more naturally starts from data tables and views, then gradually adds application pages, automation, and permissions.

NocoBase starts from the data model, then builds pages, permissions, workflows, and AI capabilities around the same underlying data, eventually forming a business system designed for different roles.

AI makes the comparison even more interesting. Baserow has already integrated AI deeply into database and application building. Its AI assistant Kuma can create and modify databases, formulas, views, and application pages through natural language.

NocoBase also supports AI-assisted system building, but AI reaches further across the complete business-system structure. AI Agents can participate in data modeling, page building, permission configuration, workflow orchestration, plugin management, and system deployment. After the system is built, AI Employees can work directly inside CRM pages using current customer data, sales opportunities, and user permissions.

Both products can therefore use AI to build applications and process data. The clearer difference is that NocoBase can directly connect Coding Agents and treat AI as a participant in the business system: AI not only helps users build the CRM, but can continue participating in daily business execution after the CRM is in use.

Enterprise Capability Comparison

As applications spread across more teams, factors beyond data management and page building—permissions, security, deployment, and long-term operations—also become part of the selection process.

Baserow has expanded from an open-source database product into application building, automation, and AI, while adding increasingly complete enterprise capabilities.

NocoBase's enterprise capabilities are organized around complete business systems. Data models, pages, workflows, permissions, security, multi-environment management, cluster deployment, and AI Agents all operate within the same system architecture.

Conclusion: How to Choose Between Baserow and NocoBase

Baserow and NocoBase are both open-source and self-hostable, and both now offer application building, automation, and AI capabilities. But the problems they are best suited to solve are still different.

If your core requirement is to organize data quickly, replace spreadsheets, and let a team collaborate around that data, Baserow is simpler. It keeps a spreadsheet-like experience while allowing you to add views, applications, automation, and AI.

If your requirements already involve multiple business objects, different roles, complex permissions, approvals, and workflows—or if you want AI Agents to operate inside an enterprise system under established permissions and business rules—NocoBase is better suited to building that kind of long-running business system.

In simple terms:

Baserow is a good fit when you want to start from straightforward data management and collaboration.
NocoBase is a better fit when you want to start from a business system and provide AI Agents with an executable enterprise environment.

We are also seeing more users who originally chose spreadsheets or multidimensional-table products for business management move to NocoBase as their needs grow. As business complexity increases, table-centered management often begins to run into limitations around role permissions, workflows, data relationships, and system extensibility. At that point, the requirement starts shifting from “a better spreadsheet” to a real business system.

Related reading:

How to Build a Production-Ready CRM with AI and NocoBase

NocoBase — Tue, 11 Aug 2026 12:29:28 +0000

Originally published at https://www.nocobase.com/en/blog/build-production-ready-crm-with-ai-and-nocobase

TL;DR

AI can build a CRM that is genuinely ready for production. With NocoBase providing the enterprise application foundations—data models, role-based permissions, security auditing, workflows, and more—AI can build a CRM from business requirements and then continue adding automation and AI Employees so the team can use it reliably in real operations over the long term.

Background

A recent Reddit discussion raised an interesting question: now that AI development tools are so capable, do teams still need to buy Salesforce or HubSpot, or can they simply Vibe Code an internal CRM?

One user who had actually built a CRM this way noted that AI can quickly create basic features such as customer management and dashboards. But once the system needs to support a real team over time, issues such as permissions, data isolation, security, and ongoing maintenance still have to be solved.

He made the point that you can absolutely Vibe Code a CRM, but you cannot simply Vibe Code an enterprise CRM that remains reliable once it is exposed to real users, real data, and real business processes. Coding is the easy part; everything behind it is harder.

AI can build the basic framework of a CRM very quickly, but there is still a gap between that and a system that is truly ready for enterprise use.

Today, however, there is another approach. Instead of asking AI to recreate enterprise application fundamentals from scratch—permissions, security, auditing, data models, and so on—we can give it an application foundation that already provides those capabilities, then let AI focus on building and iterating the actual business system.

In this guide, we will show how to combine AI with NocoBase's enterprise application capabilities to build a production-ready CRM from natural-language requirements in about an hour.

🚀 You can also try applications built with NocoBase + AI online and see what AI-assisted application building looks like in practice: https://demo.nocobase.com/new

All screenshots in this article come from the NocoBase online demo. The entire system, from design to implementation, was completed by an AI Coding Agent.

1. Start with Real Business Requirements

This article uses a small B2B office furniture company as the example.

The company mainly supplies office furniture and commercial-space solutions to businesses, design firms, architecture studios, hotels, coworking spaces, and educational institutions. A small sales team handles customer acquisition, project follow-up, quotations, and deal closing.

A typical project might begin when a design firm requests an office renovation. A salesperson needs to create the company account and contacts, open an opportunity, continuously record meetings and email communication, select products such as conference tables, office chairs, workstations, and acoustic partitions based on the project requirements, generate a quotation, and then move the deal through several rounds of communication and negotiation until it closes.

The main sales process is:

Lead → Company account → Opportunity → Quotation → Ongoing follow-up → Closed deal

For this sales team, the CRM needs to manage company accounts and contacts, leads, opportunities, products and quotations, communication records, and follow-up tasks in one place. It should also support sales dashboards, team permissions, business automation, and AI-assisted work.

Describe the Business in Natural Language

Describe the company's business, customer types, team roles, and sales process directly to AI. The key is to explain what the company sells, which customers it serves, how salespeople develop accounts and move projects forward, how a project progresses from initial contact to closing, and what data and daily work the CRM needs to manage. You can also include team roles, sales rules that should run automatically, and the work you want AI Employees to handle so AI first understands the team and business the CRM is supposed to support.

NocoBase can connect to different large language models for application building, including GPT, Opus, Qwen, and DeepSeek. Different models may vary in how they understand requirements, how quickly they generate results, and how the final application is presented, so you can choose based on actual results and your own preferences.

Which model should you choose? NocoBase model comparison: https://docs.nocobase.com/ai-builder/ai-portal/model-selection/

You can give the business requirements to AI like this:

I run a small B2B office furniture company. We mainly provide office furniture and commercial-space solutions to businesses, design firms, architecture studios, hotels, and coworking spaces.

Please use NocoBase to help me build a CRM that manages the full sales process from lead to closed deal, including company accounts and contacts, opportunities, products and quotations, customer communications, follow-up activities, and sales dashboards.

Our opportunities usually move through these stages:
Initial contact → Quotation → Business negotiation → Closed deal.

The team includes sales representatives, sales managers, and read-only users. We will also need corresponding data permissions, post-deal automation, reminders for opportunities that have not been followed up for a long time, and AI Employees that can organize customer emails and meeting notes.

First, summarize the CRM's main modules, data relationships, sales process, and user roles based on these requirements. After I confirm the design, begin building it in NocoBase.

Permissions, automation, and AI Employees do not all need to be configured in one pass. First confirm that AI correctly understands the core business objects—accounts, contacts, opportunities, products, and quotations—then continue improving the existing CRM.

Confirm AI's Understanding of the Business

Before building, ask AI to produce a concise CRM structure based on the requirements. Confirm that it includes accounts and contacts, leads, opportunities, products and quotations, communications and follow-ups, sales dashboards, user roles, and business rules.

Also verify that the main data relationships and sales stages are correct. For example, one company account can have multiple contacts, opportunities, and communication records, while each quotation should be linked to the customer, the opportunity, and the specific products being quoted.

Use the following sales stages consistently:

Initial contact → Quotation → Business negotiation → Closed deal

Once AI clearly understands the business, let it start building the CRM from this design.

2. Let AI Build the CRM, Then Check the Core Business Logic

After the CRM is generated, first verify the basic business relationships instead of immediately adding permissions, automation, or more pages. Focus on whether accounts, contacts, opportunities, products, quotations, and communication records are correctly connected and whether the full process matches how sales actually works.

Check Accounts and Contacts

Each company account should centrally connect company information, contacts, account owner, related opportunities, communication records, and follow-up items.

When a salesperson opens an account detail page, they should be able to immediately see who the contacts are, which projects are currently active, what the latest communication was, and what needs to happen next.

Also check that one customer can be linked to multiple contacts, opportunities, and communication records instead of having this information generated as unrelated standalone pages.

Check Opportunity Progression

All active projects should be managed through opportunities and progress through these stages:

Initial contact → Quotation → Business negotiation → Closed deal

Each opportunity should record the associated customer, opportunity owner, expected value, expected close date, and current stage, and users should be able to view and update opportunities from a pipeline board.

Check Products and Quotations

The product catalog should centrally maintain product code, product name, category, sales price, and availability status.

A quotation should be linked to the company account, the specific opportunity, quoted products, quotation amount, validity period, and current status, so salespeople can open quotations from an opportunity and also view related quotations from the customer detail page.

If the relationships between customers, opportunities, products, and quotations do not match the real business, describe the specific issue directly to AI and have it adjust the existing CRM. Once the core business is correct, continue adding the capabilities needed for team use.

For guidance on collaborating more effectively with an AI Agent during application building, see: https://docs.nocobase.com/ai-builder/ai-portal/agent-workflow

3. Turn the Basic CRM into a System the Team Can Actually Use

Once the core workflows around customers, opportunities, and quotations work correctly, continue giving AI the team's roles and sales rules. AI can then add permissions and automation to the existing CRM so it supports collaboration and daily operations.

Configure Permissions Around Team Responsibilities

First tell AI which roles exist and what each role is allowed to view and do:

Sales representatives can only view and manage the customers, opportunities, and follow-up items assigned to them; sales managers can view the entire team's data, reassign owners, and review sales progress; read-only users can view relevant information but cannot create, edit, or delete business data.

AI can create these roles directly in the existing CRM and configure data scopes and operation permissions. After configuration, enter the system as each role and confirm that the visible data and available actions match the actual division of responsibilities. If the permission scope is inaccurate, tell AI which role, data, or operation needs adjustment, or modify the permissions directly in the interface.

Turn Repetitive Sales Rules into Workflows

Repeated business actions in the sales process can also be expressed as clear trigger conditions and expected outcomes, then handed to AI to configure as automation in the existing CRM.

For example, when an opportunity reaches the Closed stage, the system can automatically update the customer status, create follow-up tasks, and assign them to the appropriate owner. If an opportunity has no new communication record for seven consecutive days, the system can automatically remind the salesperson to follow up.

After the rules are configured, test real scenarios by changing opportunity stages or simulating a long period without follow-up. Confirm that the automation triggers as expected and correctly updates data, creates tasks, or sends reminders.

Configure AI Employees for Sales Work

You can also configure AI Employees for sales scenarios and let them participate directly in everyday work.

For example, after a customer meeting, a salesperson can give the meeting notes or customer email to an AI Employee. The AI Employee can organize the communication, extract key points and next actions, generate a customer activity record, and provide follow-up suggestions.

The same approach can be used to organize customer background information, summarize historical communications, and prepare follow-up content, allowing AI Employees to continuously take over repetitive information-processing work.

Keep Adjusting the CRM Based on Real Use

Once the CRM is in actual use, a sales manager may want the dashboard to add current pipeline value, expected near-term closing value, closed revenue, customers requiring follow-up, and sales target completion.

Sales representatives may also want the opportunity board to add customer filters, owner filters, expected close dates, and more complete opportunity information so they can quickly identify the projects that need attention first.

Continue giving this feedback to AI so it can adjust page layouts, information density, status presentation, card content, key data placement, and the overall visual style. All changes can be made directly on the existing CRM without rebuilding the system.

NocoBase AI Builder lets AI design, build, and continue adjusting enterprise applications from natural-language requirements: https://docs.nocobase.com/ai-builder

4. Run Through a Complete Real Sales Process

Once the system is basically complete, run through the full process in the same order a salesperson would use it:

Create company account → Add contact → Create opportunity → Move opportunity through stages → Record customer meeting → Create follow-up task → Select products and generate quotation → Enter business negotiation → Close opportunity → Automatically run post-deal workflows → Update sales dashboard

Check four areas throughout the process:

Is the business data connected correctly? Are customers, contacts, opportunities, quotations, communication records, and follow-up tasks linked correctly?

Are team permissions correct? Do sales representatives, sales managers, and read-only users see the right data and have the right actions?

Does automation run correctly? Do closed opportunities, long periods without follow-up, and other configured scenarios trigger correctly and update data or create tasks as expected?

Are AI Employees genuinely useful? Can meeting notes and customer emails be organized correctly, and can key information, next actions, and follow-up suggestions become part of the real sales workflow?

After completing this end-to-end sales process, you can confirm that the CRM is capable of supporting a small B2B sales team across customer management, opportunity progression, product quotations, ongoing follow-up, team collaboration, and daily sales operations.

Conclusion

Vibe Coding has significantly lowered the barrier to taking an application from zero to one. A new division of responsibilities is emerging between AI and enterprise application platforms: AI understands the business, generates the application, and keeps iterating as requirements change; enterprise application platforms such as NocoBase provide the data management, permissions, workflows, auditing, and other foundations required for a system to run reliably over the long term.

If you already have a clear business requirement, start by describing it. Tell AI about your business, team, and processes, then combine it with NocoBase to build the CRM you actually need step by step. Going from requirements to a usable business system may now be simpler than you expect.

Ready to get started? Build your enterprise AI CRM with AI + NocoBase.

Related reading:

Weekly Updates: Assign Plugin Skills to AI Employees

NocoBase — Mon, 10 Aug 2026 07:22:18 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.1.37

Release date: 2026-08-08

🎉 New Features

[client-v2] Add Date variables and optional formatted output to V2 field-value editors. (#10289) by @katherinehhh

🐛 Bug Fixes

[client-v2]
- Fix missing and incorrectly resolved Current popup parent record variables in v2 popup-subtable add-new and edit dialogs. (#10292) by @katherinehhh
- Fixed parent item variables resolving to the wrong level when assigning association field values in sub-tables. (#10249) by @gchust
- Fix the cancel button language in mobile selection lists (#10297) by @zhangzhonghe
[data-source-manager] Fixed formula fields being converted to number fields after synchronizing fields from the database (#10303) by @2013xile
[database] Fixed migration packages omitting many-to-many through-table data after an application restart (#10306) by @cgyrock
[Backup manager] Fix duplicate backups from async exports (#10300) by @gchust
[AI employees] AI employee actions now support linkage rules for conditional visibility in v2 forms. (#10298) by @jiannx
[Data source: External NocoBase] Fixed external NocoBase files and attachment fields failing to load in AI workflows by @2013xile
[Migration manager] Fixed many-to-many through-table migration data after application restarts and classified migration rules as system data by @cgyrock
[Workflow: Approval] Fix approval comment default values when using RunJS by @zhangzhonghe
[App supervisor] Prevented app creation with database identifiers that do not start with an English letter or contain unsupported characters. by @hongboji

v2.1.36

Release date: 2026-08-05

🐛 Bug Fixes

[Data source manager] Prevented clearing a field interface directly from the Configure fields table. (#10288) by @hongboji
[Auth: LDAP] Fixed LDAP login when a user DN mixes UTF-8 escapes with escaped syntax characters such as commas. by @hongboji

v2.1.35

Release date: 2026-08-05

🚀 Improvements

[Workflow: HTTP request node] Fix unstable test cases (#10246) by @mytharcher
[Action: Batch update] Support configurable after-success behavior for v2 Update record and Bulk update actions. (#10278) by @katherinehhh
[Action: Export records] Add field search to v2 import and export action settings. (#10261) by @katherinehhh
[Action: Export records Pro] Add field search to v2 Import Pro and Export Pro action settings. by @katherinehhh

🐛 Bug Fixes

[client-v2] Fix missing Current record variables in v2 JS column event-flow conditions. (#10279) by @katherinehhh
[database] Fixed MSSQL queries failing when filtering to-many relations with pagination and sorting by a root collection field (#10224) by @cgyrock
[data-source-manager] Fixed external data source table synchronization leaving removed collections registered in the database manager (#10209) by @cgyrock
[Workflow: JavaScript] Fixed JavaScript workflow Workers not exiting after scripts returned or asynchronous workflows timed out (#10241) by @mytharcher
[Collection field: Sequence] Fixed duplicate automatic sequence values after migration when multiple records share the latest creation time (#10239) by @mytharcher
[Data source: External SQL Server] N/A — regression test coverage only by @cgyrock
[AI: Knowledge base] Fixed PGVector knowledge base searches consuming unused PostgreSQL pool connections and creating duplicate pools for different vector tables. by @cgyrock
[Data source: External MySQL] Fixed previously selected external database tables disappearing after adding new tables. by @cgyrock
[Workflow: Approval]
- Fix missing field values in approval sub-tables by @zhangzhonghe
- Allow approval comments to use configurable default values by @zhangzhonghe

develop

v3.0.0-alpha.7

Release date: 2026-08-06

🎉 New Features

[client-v2] Support using the standalone Settings application as the default app entry. (#10267) by @katherinehhh
[AI employees]
- AI employees can now be assigned skills from the employee settings page. Skills are built from plugins. (#10237) by @cgyrock
- Added Portal-scoped AI conversations and unread counts. (#10266) by @cgyrock
[Portal manager] Updated init defaults so non-latest installs use the modern client entry and seed the default AI, admin, and mobile portals; the CLI can now save and update the client entry mode. (#10281) by @chenos

🚀 Improvements

[Action: Batch update] Support configurable after-success behavior for v2 Update record and Bulk update actions. (#10278) by @katherinehhh
[Action: Export records] Add field search to v2 import and export action settings. (#10261) by @katherinehhh
[Action: Export records Pro] Add field search to v2 Import Pro and Export Pro action settings. by @katherinehhh

🐛 Bug Fixes

[client-v2]
- Fix missing spacing in workflow approval configuration dialogs (#10276) by @zhangzhonghe
- Fix missing Current record variables in v2 JS column event-flow conditions. (#10279) by @katherinehhh
- Hide the maintenance dialog and retry button while the application is upgrading (#10250) by @zhangzhonghe
- Prevent long table content from widening columns and wrap it automatically (#10259) by @zhangzhonghe
[database] Fixed MSSQL queries failing when filtering to-many relations with pagination and sorting by a root collection field (#10224) by @cgyrock
[data-source-manager] Fixed external data source table synchronization leaving removed collections registered in the database manager (#10209) by @cgyrock
[Localization] Fixed a crash when opening Localization settings with the Lina AI assistant entry. (#10293) by @cgyrock
[Data source manager] Prevented clearing a field interface directly from the Configure fields table. (#10288) by @hongboji
[Backup manager] Prevent repeated V2 backup restore submissions while a restore request is in progress. (#10262) by @katherinehhh
[File manager] Fixed shared attachments such as the system logo not loading for authenticated member users (#10268) by @mytharcher
[AI employees] Fixed the AI employee entry not appearing in non-default portals. (#10260) by @cgyrock
[Data source: External MySQL] Fixed previously selected external database tables disappearing after adding new tables. by @cgyrock
[AI: Knowledge base] Fixed PGVector knowledge base searches consuming unused PostgreSQL pool connections and creating duplicate pools for different vector tables. by @cgyrock
[Data source: External SQL Server] N/A — regression test coverage only by @cgyrock
[Workflow: Approval]
- Fix missing field values in approval sub-tables by @zhangzhonghe
- Fix approval comment default values when using RunJS by @zhangzhonghe
- Allow approval comments to use configurable default values by @zhangzhonghe
[App supervisor] Prevented app creation with database identifiers that do not start with an English letter or contain unsupported characters. by @hongboji
[Auth: LDAP] Fixed LDAP login when a user DN mixes UTF-8 escapes with escaped syntax characters such as commas. by @hongboji

v3.0.0-alpha.6

Release date: 2026-08-03

🚀 Improvements

[Workflow: HTTP request node] Fix unstable test cases (#10246) by @mytharcher

🐛 Bug Fixes

[auth] Fixed occasional Invalid CSRF token errors on API requests in cross-origin deployments (#10245) by @mytharcher
[Portal manager] Fix device icon and long title display on Portal cards (#10248) by @zhangzhonghe
[Collection field: Sequence] Fixed duplicate automatic sequence values after migration when multiple records share the latest creation time (#10239) by @mytharcher
[Workflow: JavaScript] Fixed JavaScript workflow Workers not exiting after scripts returned or asynchronous workflows timed out (#10241) by @mytharcher

How to Design an IT Asset Management System: Data Model, Lifecycle, and Workflows

NocoBase — Wed, 05 Aug 2026 15:49:17 +0000

Originally published at https://www.nocobase.com/en/blog/enterprise-it-asset-management-system-guide

Introduction

Recently, Sarvam AI Product Manager Neha Kalani shared the experience of a startup where her sister works. In March, the team used vibe coding to build an internal project management system similar to Jira. The person responsible for development was a QA lead, yet the first version not only fit the team’s working habits better but also appeared to offer more features than the SaaS tool they had used before.

By July, however, the team had abandoned the in-house system and migrated back to Linear because maintaining the internal tool was taking up too much time and energy.

As vibe coding and AI coding agents become more widely used, building a business system is getting easier. But as that system becomes more deeply embedded in day-to-day operations, the cost of modifying and maintaining it can continue to rise.

Is there a way to combine the flexibility of vibe coding with the stability of a mature business system?

Using an IT asset management system as an example, this guide explains how to start from real requirements, define the data model, asset lifecycle, and core workflows, and then use AI to build a business system that balances customization flexibility with operational stability and can continue evolving after launch.

1. Define the Scope of the IT Asset Management System from Real Scenarios

To make the following data model, asset lifecycle, and workflow design more concrete, this article uses a technology company with around 300 employees as an example.

The company operates across multiple office locations and also has some remote employees. Its IT team needs to manage computers, monitors, mobile phones, peripherals, and network equipment centrally, but the relevant information is currently scattered across Excel files, shared spreadsheets, and employee chat messages.

Daily asset management mainly involves the following scenarios:

Find and assign available equipment when a new employee joins;
Verify and recover assets assigned to an employee when they leave;
Transfer equipment between employees, departments, or office locations;
Record the repair process and outcome when a device fails;
Check a device’s current location, user, status, and warranty period;
Trace previous assignment, return, transfer, and repair records.

These scenarios can be further organized into three core capabilities that the system needs to cover:

If procurement and cost management need to be included later, the system can be extended with suppliers, purchase contracts, repair costs, asset depreciation, and budgets. If the scope expands to software assets, it can also include software licenses, account assignments, and authorization periods.

2. Design the Core Structure of the IT Asset Management System

Once the business scope is clear, the next step is to determine which data the system should store, how different data objects should relate to one another, and how asset statuses and business processes should be designed. AI can assist with this stage as well. Based on the business scenarios above, it can identify the main data objects, break down their relationships, and draft the asset statuses and business processes before business users confirm and adjust them according to actual policies.

Using the employee equipment management scenario in this article, let’s look at how the core structure of an IT asset management system can be designed.

1. Build a Data Structure Centered on the Asset Register

A basic employee equipment management system mainly contains three types of data:

The asset register is the core of the entire system. Each record represents a specific asset that can be managed independently. Asset IDs and serial numbers should have uniqueness rules to prevent the same device from being entered more than once.

Information that needs to be reused by multiple assets and maintained centrally—such as asset categories, device models, employees, departments, and office locations—can be stored in separate collections and linked to the asset register. When the data volume is small and management requirements are simple, information such as brand, model, and supplier can first be stored directly as asset fields and restructured later if necessary.

The main relationships in the system are centered on individual assets and include several common one-to-many relationships. One asset category or device model can correspond to many assets, one employee can hold several assets, and one asset can be linked to multiple assignment, return, transfer, and repair records. Reference data such as employees, departments, and office locations can be reused through association fields. Suppliers can be associated with repair records when needed, reducing duplicate data entry and making later queries and reporting easier.

The asset register stores the device’s current user, department, office location, status, procurement information, and warranty information. Business records preserve previous assignments, returns, transfers, and repairs. Every business operation should create the corresponding history record while updating the asset register so that current information remains consistent with historical changes.

2. Define Asset Statuses and Transition Rules

The asset register needs a “current status” field to indicate whether a device is available and which management stage it is currently in. The full process from registration and use to final retirement can be represented by the current status together with historical business records.

When defining status rules, registration, assignment, return, repair, and retirement scenarios can also be given to AI first. It can draft possible statuses, transition paths, and the data that needs to be updated together.

A basic system can start with four asset statuses:

Status changes are triggered by specific business actions:

Asset registration completed → Available

Available
  └─ Assign → In use

In use
  ├─ Returned and passes inspection → Available
  ├─ Sent for repair or fault found after return → Under repair
  └─ Confirmed no longer usable → Retired

Under repair
  ├─ Repair completed → Available
  └─ Cannot be repaired → Retired

“Available,” “In use,” “Under repair,” and “Retired” are asset statuses. “Assign,” “Return,” “Transfer,” “Send for repair,” and “Complete repair” are business actions. A business action may change the asset status, or it may only change the current user, department, or office location.

For example, after a device is returned, the system needs to determine the next status based on the inspection result. A working device returns to Available, a faulty device moves to Under repair, and a device that can no longer be used moves to Retired. Business actions and status changes therefore do not have a fixed one-to-one relationship.

For scenarios that require inspection, approval, or waiting, intermediate statuses such as Reserved, Pending inspection, Pending transfer, and Pending disposal can also be added. A separate status is only necessary when the asset genuinely needs to remain in that stage for a period of time.

3. Configure High-Frequency Business Actions as Workflows

The current information in the asset register, the business records, and the status transition rules have now been defined. A workflow combines these rules into a complete operation so that administrators do not have to update asset status, current user, office location, and history records separately.

Whether the operation is an assignment, return, or repair, a complete business action usually includes the following steps:

Validate current data and permissions → Update the asset register → Create the corresponding business record → Send notifications or trigger follow-up actions

Common workflows can be designed in the following way:

Whether transfers need a separate workflow depends on how frequently they occur. If the company needs a clear record of which employee, department, or location an asset moved from and to, a separate transfer record is recommended. If office locations are only changed occasionally, the location can also be updated as part of another operation while preserving the change history.

Workflows need to keep related data synchronized. For an asset assignment, the operation should only be considered complete when the current user, asset status, and assignment record have all been updated successfully. If any step fails, the system should roll back the change to avoid inconsistent data.

For a device repair, the workflow updates the asset status to Under repair and creates a repair record for tracking the repair supplier, repair type, processing status, cost, and completion time. Once the repair is complete, the asset is returned to Available or moved to Retired based on the outcome.

4. Summarize Asset Statuses with a Management Dashboard

As asset register and business record data accumulate, the team can use a management dashboard to understand the overall asset situation and quickly identify devices that require attention.

Dashboard data can be aggregated directly from the asset register and different types of business records. For example, total asset counts and status distribution come from the asset register, repair trends come from repair records, and assets approaching the end of their warranty can be filtered by warranty date.

Asset status, category distribution, and trends are suitable for charts. Items that need follow-up are better shown as detailed lists, such as assets with warranties about to expire, assets under repair, assets past their expected return date, assets left unassigned for a long time, or devices with frequent repairs.

3. Build the System with an AI Agent and NocoBase

The data model, asset statuses and transition rules, business workflows, and management dashboard have now been designed. Next, an AI agent can connect to NocoBase and turn these designs into collections, associations, pages, business actions, and workflows.

1. Define the Roles of the AI Agent, NocoBase, and Business Users

Each of the three plays a different role during system implementation.

Business users explain the actual requirements and confirm asset statuses, operation conditions, role permissions, and exception-handling rules. For example, whether returned devices require inspection, which assets department managers can view, and whether devices under repair can be reassigned all depend on company policies.

The AI agent turns these business rules into executable system configurations. After connecting to NocoBase, it can create collections and associations, build list, form, and detail pages, configure workflows and permissions, and continue adjusting existing structures as requirements change. NocoBase officially provides a CLI and Skills, allowing AI agents such as Claude Code, Codex, Cursor, and OpenCode to participate in data modeling, page building, workflow orchestration, and permission configuration.

💡 How do you connect an AI agent to NocoBase? Read the official guide: https://docs.nocobase.com/ai-builder

NocoBase supports the system’s long-term operation. As an open-source AI no-code platform, it provides data models, pages, roles and data-scope permissions, workflows, scheduled tasks, and operation audits, together with self-hosting and plugin extensibility. The AI agent can call these existing capabilities directly instead of rebuilding accounts, permissions, page frameworks, and workflow execution mechanisms for every new system.

This approach increases implementation speed while preserving room for later maintenance and adjustment. After launch, administrators can still inspect and modify fields, pages, permissions, and workflows through the visual interface, reducing dependence on generated code and one-time AI output.

2. Let the AI Agent Complete the Initial Build in Stages

An asset management system contains multiple collections and business processes. Trying to configure everything in one step makes it easy to miss important details. It is better to ask the AI agent to produce the design first, confirm the data structure and status rules, and then create pages, workflows, permissions, and the management dashboard in stages.

You can proceed in the following order: define the data model, asset statuses, transition conditions, and workflows, and then let the AI agent execute each stage separately.

Confirm the data model
→ Create basic pages
→ Configure business actions
→ Add roles and permissions
→ Build the management dashboard and reminders
→ Test the complete business process
→ Import production data

The previous sections have already defined the data to manage, the relationships between data, asset statuses, and high-frequency business actions. Next, adjust the following prompt according to the company’s actual situation, add the confirmed fields, statuses, and processes, and then give it to an AI agent that is already connected to NocoBase.

Please design and build an IT asset management system in NocoBase.
It will mainly be used to manage computers, monitors, mobile phones,
peripherals, and network equipment.

First, read the collections, pages, workflows, and permission configurations
in the current application.
If identical or similar content already exists, prioritize reusing or adjusting it
to avoid duplicate creation or overwriting existing configurations.

Follow the confirmed business design below strictly.
For any rules that are still unclear, ask questions first and do not fill in the gaps yourself.

1. Data structure

The system needs to contain three types of data:

1. Reference data

- Asset categories
- Device models
- Employees
- Departments
- Office locations
- Suppliers (optional)

Based on whether the information needs to be reused and maintained centrally,
determine which items should be stored in separate collections
and which can be stored directly as asset fields. Explain the reasons.

2. Asset register

Each asset needs to store:

- Asset name
- Asset ID
- Serial number
- Asset category
- Brand and model
- Current status
- Current user
- Current department
- Current office location
- Device condition
- Purchase date
- Warranty date

Set uniqueness rules for the asset ID and serial number.

3. Business records

The system needs to store:

- Asset assignment records
- Asset return records
- Asset repair records

Based on the actual frequency of asset transfers,
determine whether a separate transfer record is needed.

If transfers are infrequent, changes to the user, department, or office location
can be included in existing business records. Explain the specific approach.

The data relationships need to support the following:

- One asset category or device model can correspond to multiple assets;
- One employee can hold multiple assets;
- One asset can be linked to multiple business records;
- Suppliers can be linked to asset sources or repair records when needed.

2. Asset statuses and transition rules

The basic statuses are:

- Available
- In use
- Under repair
- Retired

The following statuses are optional:

- Reserved
- Pending inspection
- Pending transfer
- Pending disposal

Explain the meaning, entry conditions, exit conditions,
and permitted business actions for each status.

Status transitions must follow these basic rules:

- An asset becomes Available after registration is completed;
- An Available asset becomes In use after assignment is completed;
- An In-use asset returns to Available after it is returned and passes inspection;
- An asset moves to Under repair when it is sent for repair or a fault is found during inspection;
- An asset returns to Available after repair is completed;
- An asset moves to Retired when it can no longer be used or repaired.

3. Business actions

The system needs to support:

- Assign device
- Return device
- Send device for repair
- Complete repair
- Retire device
- Optional asset transfer

Each business action needs to:

- Validate the asset’s current status and operation permissions;
- Update the current information in the asset register;
- Create the corresponding business record;
- Send notifications or trigger follow-up processing when needed.

Ensure that the asset register update and business record creation
are completed within the same operation.

If an exception occurs during execution,
roll back the changes to avoid inconsistencies between current information and history records.

4. Pages and management dashboard

Design the following pages:

- Asset management overview
- Asset list
- Asset detail page
- Create and edit asset forms
- Employee-held assets page
- Assignment records page
- Return records page
- Repair records page
- Optional transfer records page

The management dashboard needs to show:

- Total assets and status distribution
- Category and brand distribution
- Assets currently under repair
- Assets with warranties about to expire
- Number and cost of repairs
- Assets held by employees or departments

If a metric does not have the required fields,
first explain which fields need to be added. Do not generate an empty metric directly.

If device warranty periods need to be tracked,
configure a scheduled task to check warranty dates
and show assets with warranties about to expire on the management dashboard.

5. Roles and permissions

Design permissions for the following roles:

- IT administrator
- Regular employee
- Department manager
- System administrator

For each role, explain:

- Which pages they can access;
- Which data they can view;
- Which actions they can perform;
- Which fields they can modify.

Regular employees can only view assets assigned to themselves;
Department managers can only view data within their departments;
IT administrators are responsible for asset assignment, return, repair, and retirement;
System administrators manage the data structure, pages, workflows, and permissions.

6. Execution method

Execute the work in stages.

In the first stage, only output the following design and do not create any configuration:

- Collections and fields;
- Associations between collections;
- Asset statuses and transition rules;
- Page structure;
- Business workflows;
- Roles and permissions;
- Questions that still require confirmation from business users.

After I confirm the design, complete the following in order:

1. Create collections, fields, and associations;
2. Create basic pages;
3. Configure business actions and workflows;
4. Configure roles and data permissions;
5. Create the management dashboard and warranty reminders.

After each stage, explain:

- What has been completed;
- Which configurations were created or modified;
- Which items need to be checked;
- Which business rules remain undecided.

Wait for confirmation before moving to the next stage.

After the AI agent completes the configuration, use a small amount of test data to verify the complete business process.

For example, after a device is assigned, check whether the current user, department, office location, asset status, and assignment record are updated together. After a device is returned or a repair is completed, check whether the asset enters the correct status according to the transition rules defined earlier. Import production data only after confirming that the relationships, workflows, and permissions match actual requirements.

3. Connect Existing Data and Complete Pre-Launch Checks

Before connecting production data, standardize field names, associations, and status values according to the defined reference data, asset register, and business records, and remove duplicate or invalid data. After a small data set has been verified, import or connect the complete asset data.

If existing asset information is stored in Excel or shared spreadsheets, standardize the fields and formats before importing it in batches. If the data is already stored in an enterprise database or another business system, connect it through NocoBase data sources or APIs to reduce duplicate entry.

Permissions also need to be configured according to actual responsibilities. Define which pages each role can access, which actions they can perform, and which data they can view or modify. NocoBase can also apply field-level permissions. For example, regular employees can only view the assets assigned to them, department managers can view assets within their department, and IT administrators handle assignments, returns, repairs, and retirement. Critical fields such as asset status and current user can be restricted so that only designated roles can view or modify them.

4. Integrate AI into Daily Asset Management

After the system goes live, AI can continue to participate in daily asset management.

AI agents are mainly used to adjust fields, pages, and workflows. AI employees work with structured data in NocoBase and, within the authorized scope, handle data entry, queries, summaries, and report generation. Operations that modify official records—such as asset assignment, status changes, device retirement, and responsibility confirmation—should still be executed through system permissions and workflows.

Automatically Extract Asset Information

After receiving purchase lists, invoices, asset tag photos, or device handover notes, IT administrators can ask an AI employee to identify the device type, brand and model, asset ID, serial number, purchase date, and warranty period, and automatically fill the results into the asset form.

Critical fields such as asset IDs, serial numbers, and warranty dates should still be confirmed by an administrator and checked against uniqueness rules for duplicates or recognition errors.

Query Assets and Generate Reports

Within the authorized data scope, an AI employee can read the asset register and business records to find idle equipment, assets with warranties about to expire, repair frequency, assets held by departments, and repair costs. It can also summarize asset changes over a period and generate a monthly asset activity report.

Get Started Faster

If the number of device types is small and the permission and approval processes are simple, you do not need to design every structure from scratch. Start by defining the asset scope, fields, statuses, business actions, and role permissions, and let an AI agent connected to NocoBase generate the initial version. You can also use the NocoBase lightweight IT asset management solution as a starting point and adjust its fields, statuses, and permissions.

As the number of assets and management requirements grow, gradually add support for multiple office locations, more complex permissions, complete historical tracking, procurement, and cost management.

Conclusion

When building ITAM, ITSM, and other enterprise business systems that need to operate over the long term, we still recommend choosing a platform such as NocoBase that combines a stable business foundation with AI capabilities. It provides reliable data models, permissions, and workflows, while AI agents accelerate system implementation and AI employees participate in ongoing operations. This makes it possible to move beyond a quick prototype and build a system that can operate in real business environments, remain maintainable over time, and expand as management requirements evolve.

If you found this article useful, share it with others who are also interested in AI and enterprise system development.

Related reading:

Weekly Updates: Added Frontend AI Tools for JavaScript Blocks

NocoBase — Mon, 03 Aug 2026 16:17:58 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.1.34

Release date: 2026-08-02

🐛 Bug Fixes

[Workflow] Fixed an issue where manually executing a workflow with autoRevision=0 could still create a new revision. (#10243) by mytharcher
[UI templates] Fix the issue where table blocks load data after returning to a page with empty filters (#9890) by zhangzhonghe
[Template print] Fixed unwanted spacing between Latin and East Asian text in PDF files generated from DOCX templates. by jiannx
[Workflow: Approval] Fix missing external data source fields in approval views by zhangzhonghe

v2.1.33

Release date: 2026-07-31

🐛 Bug Fixes

[client-v2] Fix JSON field save validation errors after reloading v2 forms. (#10206) by katherinehhh
[Backup manager] Validate the maximum backup retention count and display save errors. (#10189) by katherinehhh
[AI employees] AI employee chat now validates attachment count and combined size before upload (#10195) by cgyrock
[Workflow] Fixed workflow executions becoming blocked while saving a large number of jobs in one database operation (#10204) by mytharcher

v2.1.32

Release date: 2026-07-29

🚀 Improvements

[Documentation] Improved documentation site search by grouping results by documentation section and displaying section headings and paths. More relevant pages are now ranked higher, while plugin metadata pages are placed last. (#10185) by Molunerfinn

🐛 Bug Fixes

[client-v2] Fixed table action buttons remaining disabled after their linkage rules were disabled or removed. (#10186) by hongboji
[Data source manager] Added support for searching relation target collections and target keys in the v2 Data Source Manager. (#10194) by katherinehhh
[Variables and secrets] Fixed missing error feedback when submitting a duplicate variable name on the v2 Variables and Secrets settings page. (#10181) by katherinehhh
[Workflow] Fixed the workflow canvas version dropdown not displaying versions beyond the first 20. (#10190) by mytharcher
[Version control] Fixed version control shortcuts becoming inactive after opening the settings page, and improved shortcut preview, saving, resetting, and state restoration after leaving the page. by cgyrock

v2.1.31

Release date: 2026-07-27

🚀 Improvements

[Workflow] Improved workflow pending task handling by persisting start, resume, and rerun tasks in the event queue. (#9846) by mytharcher

🐛 Bug Fixes

[ai] Improved document loading reliability with clearer password-protected PDF errors and timeout handling. (#10172) by cgyrock
[flow-engine] Fix v2 table quick edit visibility for record-scoped and field-scoped update permissions. (#10182) by katherinehhh
[AI employees]
- Fixed the Operator variable selector in AI employee workflow nodes so nested variables can be expanded, and removed the Null option from the required field. (#10167) by cgyrock
- Fixed AI employee shortcuts losing block context when starting a new conversation from an existing conversation (#10169) by cgyrock
- Fixed AI form context not using customized form item labels (#10168) by cgyrock
[AI: Knowledge base] Improved AI knowledge-base document processing with clearer PDF errors, upload size validation, timeout protection, and correct segment-list pagination. by cgyrock
[Workflow: Approval] Fix missing field templates in approval configuration when UI Editor is off by zhangzhonghe

v2.2.0-beta.16

Release date: 2026-07-31

🎉 New Features

[AI employees]
- Added an embeddable AI chat box block that supports scoped conversations, AI employee tasks, and shared chat runtime behavior. (#10125) by cgyrock
- Added frontend AI tools for JS blocks (#10121) by 2013xile
[WEB client] Reduced application language responses to requested resource namespaces (#10175) by 2013xile
[Workflow: Approval]
- Added usage instructions and card-style workflow selection to the approval initiation list in client v2 by mytharcher
- Added usage instructions and card-style workflow selection to the approval initiation list by mytharcher

🚀 Improvements

[undefined] Improved documentation site search: results are now grouped by section with visible headings and paths, more relevant pages rank first, and plugin metadata pages are sorted last. (#10185) by Molunerfinn
[client-v2]
- Improved v2 QR code and barcode scan recognition, camera lifecycle safety, and responsive preview behavior. (#10145) by katherinehhh
- Added Myanmar (my-MM) to the languages selectable in System Settings. (#10131) by hongboji
[client] Added Myanmar (my-MM) to the legacy System Settings language selector. (#10153) by hongboji
[AI employees]
- Simplified AI knowledge base vector configuration (#10178) by cgyrock
- Improved AI employee reliability across validation, data permissions, record context, attachments, workflow tasks, conversation recovery, and coding editor lifecycle handling. (#10162) by cgyrock
- Fixed AI employee model settings persistence, disabled employee conversation creation, and mobile chatbox layout behavior. (#10120) by cgyrock
[Workflow]
- Workflow tasks can now be filtered and navigated by workflow, with per-workflow pending counts (#10173) by mytharcher
- Improved workflow pending task handling by persisting start, resume, and rerun tasks in the event queue. (#9846) by mytharcher
- Improved workflow pending task handling by persisting start, resume, and rerun tasks in the event queue. (#9846) by mytharcher
[File manager] Added independent storage settings for returning original file URLs and allowing public access to file URLs (#10160) by mytharcher
[AI: Knowledge base] Vector database and embedding settings can now be configured directly for each AI knowledge base by cgyrock
[Workflow: Subflow] Change pending queue strategy based on workflow engine refactored by mytharcher
[File storage: S3(Pro)] Added independent S3 Pro settings for original URLs, public file URL access, and unsigned URLs by mytharcher
[Workflow: Approval]
- Approval application and todo tasks can now be filtered by workflow with per-workflow pending counts by mytharcher
- Improved the approval timeline with clearer status badges, timing details, user avatars, responsive layout, and connected submission rounds by mytharcher
- Added usage instructions and card-style workflow selection to the approval initiation list by mytharcher
- Approval notification channels can now be searched remotely by title by mytharcher

🐛 Bug Fixes

[client-v2]
- Fix JSON field save validation errors after reloading v2 forms. (#10206) by katherinehhh
- Fixed table action buttons remaining disabled after their linkage rule is disabled or removed. (#10186) by hongboji
- Improve error messages for unsupported and missing pages in the /v/ branch (#10159) by zhangzhonghe
- Fix RunJS values not taking effect in client v2 date range limits. (#10157) by katherinehhh
- Fix record picker lists not refreshing after creating a record in client v2. (#10142) by katherinehhh
- Fix inconsistent route state after renaming a newly enabled page tab (#10117) by zhangzhonghe
- Fixed required association values being cleared after selection in popup sub-table forms with parent-item data scopes. (#10146) by katherinehhh
- Fix mobile menus hidden incorrectly by device type rules (#10123) by zhangzhonghe
- Fixed full and specified height settings not working for JS Blocks displayed with a card (#10126) by gchust
- Fix v2 table action titles being reverted after linkage refresh. (#10140) by katherinehhh
- Fix the issue where date filter defaults become a single date (#9854) by zhangzhonghe
- Reset unwanted border and shadow styles on Markdown h2 headings. (#10107) by katherinehhh
- Fix an error that could prevent approval pages from loading (#10116) by zhangzhonghe
[flow-engine]
- Fix v2 table quick edit visibility for record-scoped and field-scoped update permissions. (#10182) by katherinehhh
- Fix v2 block configuration dropdowns closing when clicking their active trigger. (#10143) by katherinehhh
- Fixed untranslated default text in secondary confirmation settings when using Simplified Chinese (#10149) by mytharcher
- Fixed an issue where the Add Block menu could unexpectedly disappear while searching. (#10097) by gchust
- Fix mobile popups exceeding the screen and hiding the close button (#10118) by zhangzhonghe
[ai] Improved document loading reliability with clearer password-protected PDF errors and timeout handling. (#10172) by cgyrock
[utils] Ensured server-side outbound request redirects also comply with SERVER_REQUEST_WHITELIST (#10109) by mytharcher
Reference: Environment variables
[database] Fixed an SQL injection risk when reading database view metadata (#10115) by 2013xile
[resourcer] Fixed pre-action workflows not triggering when used together with before-save approval workflows. (#10119) by mytharcher
[server] Prevented uploaded XML and other active content files from executing scripts in the application origin (#10104) by mytharcher
[UI layout] Fix desktop pages using mobile styles on narrow screens (#10229) by zhangzhonghe
[Workflow]
- Fixed workflow executions becoming blocked while saving a large number of jobs in one database operation (#10204) by mytharcher
- Fixed workflow canvas version dropdown not showing versions beyond the first 20. (#10190) by mytharcher
- Improved regression coverage for permanent file URLs, attachment thumbnails, preview downloads, and local storage security headers (#10148) by mytharcher
[Backup manager]
- Validate the maximum backup retention count and display save errors. (#10189) by katherinehhh
- Improved the stability and accuracy of backup plugin frontend tests. (#10184) by cgyrock
- Fix missing visible error notifications when Backup Manager restore requests fail in the v2 client. (#10158) by katherinehhh
[AI employees]
- AI employee chat now validates attachment count and combined size before upload (#10195) by cgyrock
- Fixed the Operator variable selector in AI employee workflow nodes so nested variables can be expanded, and removed the Null option from the required field. (#10167) by cgyrock
- Fixed AI employee shortcuts losing block context when starting a new conversation from an existing conversation (#10169) by cgyrock
- Fixed AI form context not using customized form item labels (#10168) by cgyrock
- Prevented Nathan from reporting malformed or unchanged code patches as successfully applied (#10174) by 2013xile
- Fixed frontend Tools asking for confirmation in chat instead of using runtime approval (#10166) by 2013xile
[Data source manager] Enable searching relation target collections and target keys in the v2 data source manager. (#10194) by katherinehhh
[Variables and secrets]
- Fixed missing error feedback when submitting duplicate variables in the v2 Variables and secrets settings page. (#10181) by katherinehhh
- Fix validation feedback for v2 environment variable bulk imports and fix Type filtering failures. (#10154) by katherinehhh
[Authentication]
- Fixed incorrect SSO redirects for sub-applications using custom domains (#10170) by 2013xile
- Fixed an intermittent database connection error during application shutdown when Redis cache is enabled (#10151) by mytharcher
[Collection field: Sequence] Fixed v2 sequence rule options not saving entered values and fixed-text rules incorrectly reporting a required-field error. (#10156) by katherinehhh
[Calendar] Add scrolling to the v2 calendar event overlay when many events are shown. (#10138) by katherinehhh
[Block: Kanban] Fixed Calendar and Kanban popup templates not taking effect or being cleared incorrectly when using copied popup templates (#9856) by jiannx
[AI: Knowledge base] Improved AI knowledge-base document processing with clearer PDF errors, upload size validation, timeout protection, and correct segment-list pagination. by cgyrock
[Multi-space] Fixed account switching failures caused by stale space headers during authentication recovery by jiannx
[Version control] Fixed version-control shortcuts becoming inactive after opening settings and improved shortcut preview, save, reset, and navigation behavior by cgyrock
[App SSO] Fixed App SSO failures when the public issuer is unreachable from sub-application servers by 2013xile
[Migration manager]
- Fixed duplicate migration creation on repeated submission and improved v2 migration log and process drawer display. by katherinehhh
- Improve v2 migration error feedback, prevent duplicate migration rule names, and fix environment check modal overflow. by katherinehhh
[Auth: OIDC] Fixed incorrect redirects after OIDC login through a sub-application custom domain by 2013xile
[Workflow: Approval]
- Hide approval configuration controls when UI Editor is off by zhangzhonghe
- Fix occasional errors when opening approval task details directly by zhangzhonghe
- Fix messages overriding by mytharcher
- Fix missing field templates in approval configuration when UI Editor is off by zhangzhonghe

develop

v3.0.0-alpha.5

Release date: 2026-08-02

🎉 New Features

[Backup manager] Added backup and restore support for AI mode portals with an independent setting (#10240) by 2013xile

🚀 Improvements

[Portal manager]
- Use fixed Portal layouts, default AI Portals to Desktop without a layout option, allow cross-layout selection, and fix entry routing (#10230) by zhangzhonghe
- Improve Portal Manager form copy and descriptions. (#10242) by katherinehhh
[Workflow] Workflow create and update nodes now support combining text with variables when assigning string and text fields (#10238) by mytharcher
[AI: Knowledge base] Improved knowledge base page layouts, scrolling, loading states, empty states, and action alignment by cgyrock

🐛 Bug Fixes

[cli] Fixed portal CLI path resolution, deployment, and HTML build behavior for sub-app/custom-domain portals, and preserved existing portal HTML when a portal is disabled. (#10244) by chenos
[Workflow] Fixed an issue where manually executing a workflow with autoRevision=0 could still create a new revision. (#10243) by mytharcher
[UI templates] Fix the issue where table blocks load data after returning to a page with empty filters (#9890) by zhangzhonghe
[Users] Preserve the originating no-code Portal when navigating between sign-in and sign-up. (#10235) by katherinehhh
[Template print] Fixed unwanted spacing between Latin and East Asian text in PDF files generated from DOCX templates. by jiannx
[Workflow: Approval] Fix missing external data source fields in approval views by zhangzhonghe

v3.0.0-alpha.4

Release date: 2026-07-31

🎉 New Features

[Portal manager] Support configuring and routing to an application-wide default Portal. (#10225) by katherinehhh
[AI employees] Added UI navigation for supported LLM service CLI commands, including provider preselection when creating a service. (#10210) by cgyrock
[AI: Knowledge base] Added UI navigation for creating and editing vector databases from CLI commands, with provider preselection for new databases. by cgyrock
[Multi-space] Added default-space configuration so newly created users automatically join the selected default space. by jiannx

🚀 Improvements

[undefined] Added a multilingual plugin development guide for defining AI employee Tools, Skills, built-in employees, and frontend interactions (#10226) by cgyrock Reference: AI employee plugin development
[Portal manager] Portal cards become compact rows grouped by build mode, the settings header drops its white band, and switches, alerts and the API documentation page follow the neutral theme (#10233) by Albert-mah
[AI: Knowledge base]
- Aligned the vector database list styling with other settings tables by cgyrock
- Improved the knowledge base detail page with breadcrumb navigation, tab-based sections, and more responsive content layouts. by cgyrock

🐛 Bug Fixes

[server] Removed the obsolete knowledge base detail redirect that forced legacy Admin URLs into the Settings application. (#10232) by cgyrock
[client-v2]
- Change the settings search shortcut to avoid conflicts with version control shortcuts (#10222) by zhangzhonghe
- Fixed Kanban column quick create records not inheriting the selected group value (#10215) by jiannx
- Fix the issue where the Settings header appears on the OAuth device verification page (#10228) by zhangzhonghe
- Clarify Settings access messages and prevent menus from flashing for unauthorized roles (#10219) by zhangzhonghe
[UI layout] Fix desktop pages using mobile styles on narrow screens (#10229) by zhangzhonghe
[Block: Gantt] Fixed custom record colors not being applied to short Gantt task bars (#10217) by jiannx
[AI employees]
- Fixed the untranslated Settings tab in the AI plugin's client-v2 settings pages (#10234) by cgyrock
- Fix the theme mismatch in unsaved changes confirmation dialogs (#10223) by zhangzhonghe
[Block: Tree] Fixed Tree block searches showing placeholder nodes when no business-field records matched (#10218) by jiannx
[Portal manager] Reject duplicate Portal names with a localized conflict response. (#10231) by katherinehhh
[AI: Knowledge base] Fixed knowledge base detail navigation and aligned the hit-tests page width across Admin and Settings. by cgyrock

v2.2.0-alpha.12

Release date: 2026-07-30

🎉 New Features

[app] Client V2 settings now open in a standalone /settings page while Client V1 remains unchanged (#10187) by zhangzhonghe
[Portal manager] Settings center now opens on the portal gallery, with grouped top-level navigation, nested sidebar menus and a neutral theme (#10196) by Albert-mah
[Access control]  (#10193) by 2013xile
[AI employees] Added an embeddable AI chat box block that supports scoped conversations, AI employee tasks, and shared chat runtime behavior. (#10125) by cgyrock

🚀 Improvements

[undefined] Improved documentation site search: results are now grouped by section with visible headings and paths, more relevant pages rank first, and plugin metadata pages are sorted last. (#10185) by Molunerfinn
[Authentication]  (#10207) by 2013xile
[AI employees]
- Simplified AI knowledge base vector configuration (#10178) by cgyrock
- Improved AI employee reliability across validation, data permissions, record context, attachments, workflow tasks, conversation recovery, and coding editor lifecycle handling. (#10162) by cgyrock
[Workflow] Workflow tasks can now be filtered and navigated by workflow, with per-workflow pending counts (#10173) by mytharcher
[AI: Knowledge base] Vector database and embedding settings can now be configured directly for each AI knowledge base by cgyrock
[Workflow: Approval] Approval application and todo tasks can now be filtered by workflow with per-workflow pending counts by mytharcher

🐛 Bug Fixes

[client-v2]
- Fix JSON field save validation errors after reloading v2 forms. (#10206) by katherinehhh
- Fixed table action buttons remaining disabled after their linkage rule is disabled or removed. (#10186) by hongboji
[cli]
- Fix the Settings page failing to load after deploying extracted frontend assets (#10205) by zhangzhonghe
[Portal manager] Fix portals with an empty type not appearing in Client V2 (#10212) by zhangzhonghe
[Workflow]
- Fixed workflow executions becoming blocked while saving a large number of jobs in one database operation (#10204) by mytharcher
- Fixed workflow canvas version dropdown not showing versions beyond the first 20. (#10190) by mytharcher
[Backup manager] Validate the maximum backup retention count and display save errors. (#10189) by katherinehhh
[AI employees] AI employee chat now validates attachment count and combined size before upload (#10195) by cgyrock
[Data source manager] Enable searching relation target collections and target keys in the v2 data source manager. (#10194) by katherinehhh
[Collection field: Markdown(Vditor)]
- Fixed Markdown Vditor upload test expectations and mock isolation. (#10200) by katherinehhh
- Fixed Markdown Vditor permanent URL upload test coverage. (#10202) by katherinehhh
[Variables and secrets] Fixed missing error feedback when submitting duplicate variables in the v2 Variables and secrets settings page. (#10181) by katherinehhh
[Version control] Fixed version-control shortcuts becoming inactive after opening settings and improved shortcut preview, save, reset, and navigation behavior by cgyrock
[Migration manager] Fixed duplicate migration creation on repeated submission and improved v2 migration log and process drawer display. by katherinehhh

v2.2.0-alpha.10

Release date: 2026-07-28

🎉 New Features

[Web client] Reduced application language responses to the requested resource namespaces, avoiding unnecessary language data. (#10175) by 2013xile
[AI employees] Added support for registering frontend AI tools in JS blocks. (#10121) by 2013xile
[Workflow: Approval]
- Added usage guidance and card-based approval selection to the approval initiation list in client v2. by mytharcher

🚀 Improvements

[client-v2]
- Improved v2 QR code and barcode scan recognition, camera lifecycle safety, and responsive preview behavior. (#10145) by katherinehhh
- Added Myanmar (my-MM) to the languages available in System Settings. (#10131) by hongboji
[client] Added Myanmar (my-MM) to the legacy System Settings language selector. (#10153) by hongboji
[Workflow]
- Improved pending task handling by persisting start, resume, and rerun tasks in the event queue. (#9846) by mytharcher
[File manager] Added independent storage settings for returning original file URLs and allowing public access to file URLs. (#10160) by mytharcher
[AI employees] Fixed issues with saving AI employee model settings, disabled AI employees being able to create conversations, and the mobile chatbox layout. (#10120) by cgyrock
[Workflow: Subflow] Adjusted the waiting queue processing strategy following the workflow engine refactor. by mytharcher
[File storage: S3 (Pro)] Added independent S3 Pro settings for original URLs, public access to file URLs, and unsigned URLs. by mytharcher
[Workflow: Approval]
- Added usage guidance and card-based selection to the approval initiation list. by mytharcher
- Improved the approval timeline with clearer status badges, time information, user avatars, responsive layouts, and connections between multiple submission rounds. by mytharcher
- Added support for remotely searching approval notification channels by title. by mytharcher

🐛 Bug Fixes

[Documentation] Corrected the PLUGIN_PACKAGE_PREFIX examples to ensure that preset plugins use the @nocobase/preset- prefix. (#10179) by hongboji
[flow-engine]
- Fixed v2 table quick edit visibility not being controlled by record-level and field-level update permissions. (#10182) by katherinehhh
- Fixed untranslated default text in secondary confirmation settings when using Simplified Chinese. (#10149) by mytharcher
- Fixed v2 block configuration dropdowns unexpectedly closing when their active trigger was clicked. (#10143) by katherinehhh
- Fixed mobile popups extending beyond the screen and obscuring the close button. (#10118) by zhangzhonghe
- Fixed the Add Block menu unexpectedly disappearing during searches. (#10097) by gchust
[ai] Improved document loading reliability with clearer errors for password-protected PDFs and timeout handling. (#10172) by cgyrock
[client-v2]
- Improved error messages for unsupported and missing pages in the /v/ branch. (#10159) by zhangzhonghe
- Fixed RunJS values not taking effect in v2 date field range limits. (#10157) by katherinehhh
- Fixed v2 table action titles being overwritten by their previous titles after a linkage refresh or page reload. (#10140) by katherinehhh
- Fixed an issue in popup subtable forms where selected association field values were cleared and required-field validation was incorrectly triggered when using the parent record’s data scope. (#10146) by katherinehhh
- Fixed record picker lists not refreshing after a new record was created in client v2. (#10142) by katherinehhh
- Fixed full-height and specified-height settings not taking effect when a JS block was displayed as a card. (#10126) by gchust
- Fixed an error that could prevent approval pages from loading. (#10116) by zhangzhonghe
- Fixed inconsistent route states that could occur when a page tab was renamed immediately after being enabled. (#10117) by zhangzhonghe
- Fixed date filter default values being converted into a single date. (#9854) by zhangzhonghe
- Fixed mobile menus being incorrectly hidden by device type rules. (#10123) by zhangzhonghe
- Removed unwanted border and shadow styles from Markdown H2 headings. (#10107) by katherinehhh
[utils] Ensured that redirect targets for server-side outbound requests also comply with the SERVER_REQUEST_WHITELIST. (#10109) by mytharcher Reference: Environment variables
[resourcer] Fixed pre-action events potentially not being triggered when used together with the approval before-save mode. (#10119) by mytharcher
[database] Fixed an SQL injection risk when reading database view metadata. (#10115) by 2013xile
[server] Prevented uploaded XML and other active content files from executing scripts within the application’s origin. (#10104) by mytharcher
[Backup manager]
- Improved the stability and accuracy of the backup plugin’s frontend tests. (#10184) by cgyrock
- Fixed missing visible error notifications when Backup Manager restore requests failed in client v2. (#10158) by katherinehhh
[AI employees]
- Fixed the Operator variable selector in AI employee workflow nodes so that nested variables could be expanded, and removed the Null option from required fields. (#10167) by cgyrock
- Fixed AI form context not using custom form item labels. (#10168) by cgyrock
- Fixed frontend tools requesting confirmation in the conversation instead of using runtime approval. (#10166) by 2013xile
- Fixed AI employee shortcuts losing block context when a new conversation was started from an existing conversation. (#10169) by cgyrock
- Prevented Nathan from reporting malformed code patches or patches without changes as successfully applied. (#10174) by 2013xile
[Notification: In-app message] Fixed the in-app message template form displaying workflow canvas variables instead of the variables provided by the page. (#10180) by Molunerfinn
[Authentication]
- Fixed incorrect SSO redirects for sub-applications using custom domains. (#10170) by 2013xile
- Fixed intermittent database connection errors during application shutdown when Redis caching was enabled. (#10151) by mytharcher
[Collection field: Sequence] Fixed v2 sequence rule options not saving entered values and fixed-text rules incorrectly reporting required-field errors after values were entered. (#10156) by katherinehhh
[Block: Kanban] Fixed copied popup templates not taking effect or being incorrectly cleared in Calendar and Kanban blocks. (#9856) by jiannx
[Variables and secrets] Fixed validation feedback for v2 bulk imports of variables and secrets, and fixed Type filter failures. (#10154) by katherinehhh
[Workflow] Improved regression test coverage for permanent file URLs, attachment thumbnails, preview downloads, and local storage security response headers. (#10148) by mytharcher
[Calendar] Fixed the v2 calendar event overlay extending beyond the page when many events were displayed by adding a scrollbar. (#10138) by katherinehhh
[App SSO] Fixed App SSO failures when the public Issuer could not be accessed by sub-application servers. by 2013xile
[AI: Knowledge base] Improved AI knowledge base document processing with clearer PDF error messages, upload size validation, timeout protection, and correct pagination for segment lists. by cgyrock
[Multi-space] Fixed account switching failures caused by authentication recovery requests carrying the previous space header. by jiannx
[Migration manager] Improved v2 migration error messages, prevented duplicate migration rule names, and fixed environment check modal overflow. by katherinehhh
[Auth: OIDC] Fixed incorrect redirects after OIDC login through a custom domain of a sub-application. by 2013xile
[Workflow: Approval]
- Fixed some system variables provided in approval message templates rendering as empty. by Molunerfinn
- Prevented restricted approvers from viewing unauthorized fields in the original application content. by zhangzhonghe
- Fixed approvers being able to return applications when the Return action was not enabled. by zhangzhonghe
- Fixed missing field templates in approval configurations when UI Editor was disabled. by zhangzhonghe
- Hid approval configuration controls when UI Editor was disabled. by zhangzhonghe
- Fixed occasional errors when directly opening approval task details. by zhangzhonghe
- Fixed approval submission messages overwriting messages from pre-action events. by mytharcher
[Collection field: Signature] Fixed localization and option filtering issues in the file collection selector for client-v2 signature fields. by katherinehhh
[DingTalk] Fixed DingTalk notification channels losing the selected authenticator when saved from the v2 channel form. by jiannx

Awesome NocoBase: Discover and Share Plugins Built by the Community

NocoBase — Tue, 28 Jul 2026 03:05:50 +0000

Originally published at https://www.nocobase.com/en/blog/awesome-nocobase-community-plugins

From day one, NocoBase has been built on a plugin architecture.

This architecture gives NocoBase the flexibility and extensibility needed for long-term growth. Developers can continuously add new capabilities for different business needs without modifying the core system.

With the rise of AI coding tools, plugin development is becoming easier than ever. With tools like Claude Code, Codex, and Cursor, together with NocoBase’s AI plugin development capabilities, more developers can quickly build their own plugins.

Now, you can discover community-built plugins in Awesome NocoBase, or share your own extensions and help grow the NocoBase plugin ecosystem.

Featured Community Plugins

Currently, Awesome NocoBase features a collection of plugins created by community developers. These plugins are built from real-world projects and experiences. Some address common needs, some extend NocoBase’s core capabilities, and others provide solutions for specific business scenarios.

NocoBase Hooks

Author: Bunnarin

NocoBase Hooks provides an extension mechanism similar to PocketBase’s pb_hooks. Developers can write server-side extensions directly in the storage/hooks/ directory while leveraging NocoBase capabilities such as database events, middleware, custom APIs, ACL, and logging.

It also supports automatic loading, hot reload during development, TypeScript, and independent dependency management.

Global Search

Author: trumanharry

Global Search adds a cross-table search entry to the NocoBase admin interface, making it easier to find information across different data collections such as customers, orders, projects, and contacts.

Office File Previewer

Author: OneTwoSmall

Office File Previewer enhances NocoBase’s file preview capabilities with flexible support for Office documents and other file formats.

For use cases such as knowledge bases, contract management, archives, and internal file systems, users can preview files directly inside NocoBase without downloading files or switching between applications.

Enhanced Table Block

Author: OneTwoSmall

Enhanced Table Block extends NocoBase table blocks with richer data display and interaction features.

It is ideal for scenarios involving reports, inventory, orders, and financial data, allowing users to manage information in a more spreadsheet-like way.

Auth: Email

Author: OneTwoSmall

Supports authentication through email verification codes.

Custom Login Page

Author: JAVA-LW

Custom Login Page allows administrators to configure NocoBase login page themes, styles, and branding directly from the backend.

It is suitable for projects that require a consistent brand experience or dedicated login portals for customers, employees, and partners.

Block: Tabs

Author: zoudeming-vk

Block: Tabs provides a tab block that organizes multiple NocoBase blocks within a single interface.

For information-heavy detail pages and management screens, it reduces scrolling and groups related content into tabs, creating a clearer page structure.

Watermark

Author: fengwenkai168

Watermark adds semi-transparent watermarks to NocoBase pages and can display information about the current user.

Administrators can customize watermark text, opacity, and font size. It is suitable for contracts, customer data, and other sensitive information where reducing screenshot-based data leakage is important.

Role Switcher

Author: michaelxmn

Role Switcher adds a quick role switching option to the top navigation bar.

It helps users with multiple roles switch contexts more efficiently, and makes permission testing easier for administrators and developers.

Per-User Column Settings

Author: Albert-mah

Per-User Column Settings allows each user to save their own table column preferences.

Users can customize visible fields, reorder columns, freeze columns, and adjust column widths without affecting other users. It is especially useful for business systems where different roles focus on different information.

Field Sequence Pro

Author: ericto888

Field Sequence Pro extends the built-in auto-numbering field with support for form variables, value mapping dictionaries, and multi-dimensional isolated counters while keeping the original functionality.

It is suitable for generating unique identifiers such as order numbers, contract numbers, and business serial numbers based on different rules.

HTTP Error Handler

Author: Albert-mahmahuantest

HTTP Error Handler provides global 4xx/5xx error handling for NocoBase.

Administrators can define error handling rules using JS expressions, display unhandled API errors with custom error pages, or redirect users to specific pages automatically.

Workflow: URL Trigger

Author: Albert-mah

Workflow: URL Trigger enables workflows to be triggered by external HTTP requests.

It supports wildcard and regular expression matching, uses request parameters as workflow variables, and can work with the HTTP Response node to build Webhooks, API integrations, and automation workflows.

Workflow: Crypto

Author: Albert-mah

Workflow: Crypto provides AES encryption and decryption nodes for workflows.

It supports variable inputs and automatic JSON parsing after decryption, making it suitable for secure data exchange with external systems.

Workflow: Auth Token

Author: Albert-mah

Workflow: Auth Token generates real NocoBase login JWTs within workflows.

It can be used to create SSO login links and programmatic access tokens, and combined with URL Trigger and Crypto to build complete single sign-on workflows.

Build the NocoBase Plugin Ecosystem Together

If you have created a NocoBase plugin, we welcome you to submit it to Awesome NocoBase.

Our goal is to help more users discover valuable plugins while giving great plugins and their developers more exposure.

In the future, we will continue highlighting outstanding community plugins and the developers behind them.

Weekly Updates：Remote Search for Approval Notification Channels

NocoBase — Mon, 27 Jul 2026 10:23:21 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.1.30

Release date: 2026-07-24

🚀 Improvements

[client-v2] Improved v2 QR code and barcode scan recognition, camera lifecycle safety, and responsive preview behavior. (#10145) by @katherinehhh
[client] Added Myanmar (my-MM) to the legacy System Settings language selector. (#10153) by @hongboji
[Workflow: Approval]
- Added usage instructions and card-style workflow selection to the approval initiation list by @mytharcher
- Improved the approval timeline with clearer status badges, timing details, user avatars, responsive layout, and connected submission rounds by @mytharcher

🐛 Bug Fixes

[client-v2]
- Fix RunJS values not taking effect in client v2 date range limits. (#10157) by @katherinehhh
- Improve error messages for unsupported and missing pages in the /v/ branch (#10159) by @zhangzhonghe
- Fix v2 table action titles being reverted after linkage refresh. (#10140) by @katherinehhh
- Fixed required association values being cleared after selection in popup sub-table forms with parent-item data scopes. (#10146) by @katherinehhh
- Fix record picker lists not refreshing after creating a record in client v2. (#10142) by @katherinehhh
[flow-engine]
- Fix v2 block configuration dropdowns closing when clicking their active trigger. (#10143) by @katherinehhh
- Fixed untranslated default text in secondary confirmation settings when using Simplified Chinese (#10149) by @mytharcher
[Authentication]
- Fixed an intermittent database connection error during application shutdown when Redis cache is enabled (#10151) by @mytharcher
- Fixed incorrect SSO redirects for sub-applications using custom domains (#10170) by @2013xile
[AI employees] Prevented Nathan from reporting malformed or unchanged code patches as successfully applied (#10174) by @2013xile
[Collection field: Sequence] Fixed v2 sequence rule options not saving entered values and fixed-text rules incorrectly reporting a required-field error. (#10156) by @katherinehhh
[Backup manager] Fix missing visible error notifications when Backup Manager restore requests fail in the v2 client. (#10158) by @katherinehhh
[Block: Kanban] Fixed Calendar and Kanban popup templates not taking effect or being cleared incorrectly when using copied popup templates (#9856) by @jiannx
[App SSO] Fixed App SSO failures when the public issuer is unreachable from sub-application servers by @2013xile
[Auth: OIDC] Fixed incorrect redirects after OIDC login through a sub-application custom domain by @2013xile
[Workflow: Approval] Hide approval configuration controls when UI Editor is off by @zhangzhonghe

v2.1.29

Release date: 2026-07-21

🚀 Improvements

[Workflow: Approval] Approval notification channels can now be searched remotely by title by @mytharcher

🐛 Bug Fixes

[flow-engine] Fixed an issue where the Add Block menu could unexpectedly disappear while searching. (#10097) by @gchust
[client-v2]
- Fixed full and specified height settings not working for JS Blocks displayed with a card (#10126) by @gchust
- Fix the issue where date filter defaults become a single date (#9854) by @zhangzhonghe
[Calendar] Add scrolling to the v2 calendar event overlay when many events are shown. (#10138) by @katherinehhh
[Multi-space] Fixed account switching failures caused by stale space headers during authentication recovery by @jiannx

How to Choose a Smartsheet Alternative: 7 Tools Compared

NocoBase — Fri, 24 Jul 2026 17:49:46 +0000

Originally published at https://www.nocobase.com/en/blog/best-smartsheet-alternatives

Smartsheet is one of the first tools many teams consider when setting up project management and collaboration workflows.

It retains a familiar spreadsheet-style interface while adding boards, Gantt charts, forms, automation, reports, and dashboards. For teams that previously relied on Excel to manage projects, the learning curve is relatively low, making it easier to establish consistent processes for task assignment, progress tracking, and project reporting.

However, a tool that works well at the beginning may not remain suitable for every stage of a team’s development.

Recently, we came across a discussion about alternatives in the Smartsheet community on Reddit. The original poster works for a construction company with about 100 employees and belongs to a seven-person department. Previously, everyone managed projects according to their own habits: some used spreadsheets, some relied on personal task tools, and others tracked progress through email and meetings. As the number of projects increased, the team wanted to establish a unified project management and reporting process.

The comments showed that opinions about Smartsheet were mixed.

Users who supported Smartsheet mentioned:

Migrating from Excel is relatively straightforward
Real-time data can be connected across different sheets
Dashboards and reporting are intuitive
Forms, file review, approvals, and automation are well covered
Business teams do not have to wait for IT to develop every system

Users considering replacing Smartsheet mentioned:

Changes to pricing and licensing models
Uneven adoption across departments
Automation is often maintained by only a few advanced users
Complex relational data remains difficult to manage
Maintenance costs increase as data volume and usage expand

Based on these needs, we selected several representative Smartsheet alternatives, including open-source platforms. The following sections introduce each product’s positioning, core capabilities, major differences from Smartsheet, pricing, and suitable team types.

Before examining each product in detail, use the comparison table below to quickly identify options that may better match your team’s needs.

Product	Open Source	Primary Positioning	Similarities to Smartsheet	Key Differences
NocoBase	Yes	Enterprise business system development	Tables, pages, workflows	Focuses on data relationships, permissions, and controlled operations; highly flexible plugin architecture; self-hosted and extensible
Baserow	Yes	No-code database	Spreadsheet-style data management	Open source, self-hosted, relational data
monday	No	Visual work management	Projects, boards, automation	Greater emphasis on boards and team collaboration
SmartSuite	No	Comprehensive work management	Projects, records, processes	Combines data management with project execution
Airtable	No	Relational data collaboration	Tables, views, automation	Stronger at linked data and interface building
ClickUp	No	All-in-one project management	Tasks, dashboards, automation	Task-centric with broad feature coverage
Asana	No	Project and task management	Tasks, dependencies, timelines	Clearer and more standardized project workflows

1. NocoBase: For Teams Moving From Collaborative Spreadsheets to Business Systems

Product Information

Website: https://www.nocobase.com/
Documentation: https://docs.nocobase.com/
Pricing: https://www.nocobase.com/en/commercial
GitHub: https://github.com/nocobase/nocobase
GitHub Stars: 23.4K

What Is NocoBase?

NocoBase is an open-source AI-powered no-code platform for building enterprise business systems such as project management, CRM, contract management, order management, approvals, and ticketing.

Teams can first create related data tables for customers, projects, contracts, tasks, invoices, and other business objects. They can then configure tables, boards, forms, detail pages, charts, and action buttons through a visual interface. As business requirements change, pages, permissions, workflows, and plugins can continue to be adjusted.

Why Can It Replace Smartsheet?

NocoBase provides tables, boards, forms, detail pages, charts, and workflows, covering common Smartsheet scenarios such as project management, data collection, progress tracking, and automation.

For teams with increasingly complex data structures, NocoBase can also create multiple related tables. For example, one customer can have multiple projects, while each project can be linked to contracts, tasks, invoices, and payment records. Sales, finance, project managers, and executives can work from the same underlying data while using different pages and receiving role-based data and operation permissions.

NocoBase also offers two types of AI collaboration capabilities that support both system development and ongoing operations.

The first is AI-assisted development. Teams can connect commonly used AI agents such as Claude Code, Codex, and Cursor to NocoBase, describe business requirements in natural language, and have the AI agent assist with data modeling, page configuration, workflow orchestration, permission settings, and plugin development. The generated system can still be reviewed and adjusted through NocoBase’s no-code interface.

The second is AI Employees. After the business system goes live, AI Employees can understand business context from the current page, data blocks, and selected records. They can invoke relevant skills to query data, organize information, fill in forms, analyze trends, generate reports, and process content. AI Employees can also be orchestrated into workflows, bringing AI capabilities into specific business processes.

NocoBase also supports self-hosting, plugin extensions, and external database connections, making it suitable for teams that want control over their data and deployment environment while continuously expanding business modules.

Key Differences From Smartsheet

Smartsheet mainly uses worksheets as the collaboration entry point, with members typically viewing and updating project data directly in a grid. NocoBase starts with a data model and then configures pages, permissions, operations, and workflows around that data.

In NocoBase, users do not all have to enter the same underlying data table. Administrators can configure separate work interfaces for different roles:

Sales teams can view customers, contacts, and opportunities;
Project managers can view projects, tasks, and delivery progress;
Finance teams can view contracts, invoices, and payments;
Executives can view aggregated metrics and dashboards.

Data modification methods can also be configured according to business risk. Routine fields such as task status and assignee can support quick editing. Critical data such as contract amounts, payment status, and approval results can be entered, validated, confirmed, and submitted through dedicated forms. Once submitted, the system can trigger notifications, approvals, data updates, or other workflows.

AI further expands this system-oriented approach. During development, AI agents can understand NocoBase’s data models, pages, permissions, and workflow configurations to help teams build systems faster. During operation, AI Employees can read business context, analyze data, and perform authorized actions.

This means AI can participate throughout the complete lifecycle of a business system:

Assist with creating data models and pages from natural-language requirements;
Configure role permissions, operation methods, and business processes;
Analyze and process business data after the system goes live;
Continue participating in daily operations through AI Employees or workflows.

For teams already using Smartsheet to manage customers, contracts, projects, and financial data, this design can reduce errors and management pressure caused by multiple people directly maintaining complex worksheets.

Which Teams Is It Best For?

NocoBase is better suited to teams that:

Already use Smartsheet to manage formal business data such as customers, contracts, orders, or payments;
Have complex data relationships across multiple worksheets;
Need different operating interfaces for sales, finance, operations, and management;
Need to control which data different roles can view and modify;
Require validation, confirmation, approval, or auditing for critical data changes;
Want to use AI agents to accelerate business system development;
Want AI Employees to participate in data analysis and business processing after launch;
Need self-hosting and control over data and deployment environments;
Plan to continue adding business modules on the same platform.

🎉 NocoBase lightweight solutions are now available. Try them today!

These focused business solutions are built with NocoBase. They are open source, controllable, and easy to extend or modify around your own processes.

Each solution includes a standard prompt. Give it to an AI agent connected to your instance, and you can reproduce the same system in minutes.

https://www.nocobase.com/en/ai-blueprints

2. Baserow: For Teams That Want to Keep a Spreadsheet-Style Experience

Product Information

Website: https://baserow.io/
Documentation: https://baserow.io/user-docs
Pricing: https://baserow.io/pricing
GitHub: https://github.com/baserow/baserow
GitHub Stars: 5.3K

What Is Baserow?

Baserow is an open-source no-code database and application-building platform. It retains a spreadsheet-like interface, allowing users to manage customers, projects, content, inventory, and other information through tables, fields, linked records, and multiple views. Teams can also build internal applications, dashboards, and automated processes. Baserow additionally provides AI fields, AI formula generation, and the Kuma AI assistant.

Why Can It Replace Smartsheet?

Baserow supports tables, forms, boards, calendars, timelines, and dashboards, covering common Smartsheet needs such as data collection, project tracking, and information presentation. It also supports table relationships, lookups, rollups, and formulas, making it more suitable for related data. For teams accustomed to editing information directly in tables but seeking stronger database capabilities, the post-migration experience is relatively easy to understand.

Key Differences From Smartsheet

Smartsheet places greater emphasis on project management, task dependencies, resource planning, and cross-project reporting, while Baserow is closer to a no-code database. Teams can freely create tables and relationships, then use the application builder to turn underlying data into internal tools or customer portals. Baserow also offers an open-source, self-hosted version, allowing teams to control their deployment environment, data storage, and system extensions.

Which Teams Is It Best For?

Baserow is suitable for teams that are comfortable with spreadsheets, need to manage multiple related data tables, and prefer an open-source or self-hosted solution. It is particularly useful for content management, lightweight CRM, project data, inventory, and internal information management, as well as teams that want to build simple internal tools on top of data tables.

3. monday: For Project Teams That Prioritize Visual Collaboration

Product Information

Website: https://monday.com/
Documentation: https://support.monday.com/hc/en-us
Pricing: https://monday.com/pricing

How Does monday Organize Team Work?

monday is a visual work management platform. Teams can centralize projects, tasks, owners, deadlines, and current status in a Board, then switch among Kanban, timeline, Gantt, calendar, and dashboard views to review progress from different perspectives. It is used for project management, marketing campaigns, product development, operational planning, and cross-functional collaboration, and the platform is also adding AI workflows and AI agents.

Why Is It a Suitable Smartsheet Alternative?

For teams seeking a consistent way to collaborate on projects, monday provides a relatively intuitive starting point. Administrators can use templates to quickly create project spaces, while members work around tasks, status, owners, and milestones. Automation rules can send notifications, update fields, or move tasks when a status changes, a date arrives, or a task is assigned. Dashboards can aggregate project progress, budgets, and team workloads across multiple Boards.

monday’s AI workflows can also add content generation, information analysis, and task assignment to existing processes. Its AI agents can monitor activities, determine the next action, and execute tasks within the context of Boards and workflows, although this capability is still being rolled out gradually.

Key Differences From Smartsheet

Smartsheet retains stronger spreadsheet conventions and is well suited to managing data, formulas, and cross-sheet reports in dense grids. monday focuses more on Boards, statuses, and task progression. Colors, groups, views, and automation make it easier for members to understand who owns each task and how far the work has progressed.

This design is collaboration-friendly, particularly for scenarios that require frequent status updates, owner coordination, and milestone tracking. For complex formulas, extensive cross-sheet references, or relational business data, monday differs significantly from traditional spreadsheets and should be evaluated against each existing Smartsheet use case.

Which Teams Are Better Suited to monday?

monday is better suited to marketing, operations, product, PMO, and cross-functional teams centered on projects, tasks, and team collaboration. When members need to quickly understand owners, deadlines, current status, and project risks while also using boards, Gantt charts, automation, and management dashboards, monday can be more intuitive than maintaining complex worksheets directly.

4. SmartSuite: For Teams Managing Projects, Data, and Business Processes Together

Product Information

Website: https://www.smartsuite.com/
Documentation: https://help.smartsuite.com/en/
Pricing: https://www.smartsuite.com/pricing

What Is SmartSuite?

SmartSuite is a work management platform for business teams. It uses Solutions, Tables, and Records as its basic structure. Within one workspace, teams can manage projects, tasks, customers, contracts, risks, assets, and other business records, then view progress through tables, boards, calendars, timelines, Gantt charts, and dashboards.

SmartSuite is also gradually adding AI capabilities. Users can describe the business they need to manage in natural language, and AI Solution Generator can automatically create a solution containing tables, fields, and relationships. AI Field Agents can use field content from records to generate summaries, classifications, recommendations, or structured results and write those results directly back to the records.

Why Is It a Suitable Smartsheet Alternative?

For teams already using Smartsheet to manage projects, customers, suppliers, or operational processes, SmartSuite provides a similar table view while adding more complete record pages, linked data, and templates for multiple scenarios.

For example, a team can create separate customer, project, and task tables and connect them through linked records. Project managers can manage task dependencies and schedules in Gantt charts, business users can open individual records to view files, comments, checklists, and activity history, and management can monitor overall progress through dashboards.

Key Differences From Smartsheet

Smartsheet retains a strong worksheet-based approach, with many operations centered on rows, columns, formulas, and cross-sheet reports. SmartSuite places greater emphasis on records and the relationships among them. A project record can link to customers, tasks, budgets, risks, and deliverables while providing its own detail page and collaboration information.

This design positions SmartSuite between a traditional project management tool and a business data platform. Teams can use boards, Gantt charts, and timelines to move projects forward while connecting projects with customers, contracts, assets, and other business information. Linked records can also be used across different Solutions, reducing duplicate maintenance of the same data in multiple workspaces.

Which Teams Is It Best For?

SmartSuite is better suited to teams that manage both projects and structured business records, including professional services, marketing operations, product management, construction projects, procurement, supplier management, and lightweight CRM teams. When teams need boards, Gantt charts, and task dependencies while also connecting customers, projects, files, budgets, and risks, SmartSuite is more complete than a task-only management tool.

It is also suitable for teams that want to adopt ready-made templates and cloud services quickly and do not require self-hosting. AI Solution Generator can shorten initial configuration time, while AI Field Agents can automatically organize content, classify information, and suggest next steps after records are updated.

5. Airtable: For Teams Managing Linked Data and Flexible Business Processes

Product Information

Website: https://www.airtable.com/
Documentation: https://support.airtable.com/docs
Pricing: https://airtable.com/pricing

What Is Airtable?

Airtable is a no-code application platform built on a relational database. Teams can enter and organize data much like they would in a spreadsheet while using linked records, lookups, rollups, and formulas to connect customers, projects, tasks, content, products, and other information. Interface Designer can create operating interfaces for different teams from the same data, while automation connects notifications, record updates, and external tools.

Airtable is also strengthening its AI capabilities. Omni can create and adjust tables, interfaces, and automations from natural-language instructions. Field Agents can use record content to conduct research, classify information, generate content, and analyze feedback.

Why Is It a Suitable Smartsheet Alternative?

Airtable provides tables, boards, calendars, timelines, forms, interfaces, and automation, covering common Smartsheet needs such as data collection, project tracking, and team collaboration. It is stronger at linked data. For example, teams can create separate tables for customers and projects, projects and tasks, or products and suppliers, then keep information synchronized through linked records and reduce duplicate maintenance across multiple tables.

Key Differences From Smartsheet

Smartsheet is more focused on managing projects through worksheets, task progress, and cross-sheet reports, while Airtable is built on relational data. Users can create one-to-many and many-to-many relationships through linked records and use Interface to turn underlying data into pages for marketing, product, operations, or management teams.

This structure is suitable for scenarios involving many data objects and complex relationships. However, teams that rely heavily on Smartsheet’s task dependencies, resource management, and project portfolio capabilities should still confirm whether Airtable can cover their existing processes.

Which Teams Is It Best For?

Airtable is better suited to marketing, content, product, research, and operations teams. Common scenarios include content calendars, product roadmaps, campaign management, lightweight CRM, user research, and asset management. Teams that want to retain the flexibility of spreadsheet-style operations while connecting multiple data tables, configuring role-specific interfaces, and adding automation or AI can prioritize Airtable.

6. ClickUp: For Teams That Want to Consolidate Multiple Project Tools

Product Information

Website: https://clickup.com/
Documentation: https://help.clickup.com/hc/en-us
Pricing: https://clickup.com/pricing

What Is ClickUp?

ClickUp is an all-in-one work management platform that brings tasks, documents, whiteboards, goals, chat, calendars, and dashboards into one workspace. Teams can manage projects through list, board, Gantt, and timeline views, and use ClickUp Brain, AI agents, and automation for task summaries, content generation, information queries, and process execution.

Why Is It a Suitable Smartsheet Alternative?

ClickUp can cover common Smartsheet needs such as task assignment, project progress, automation, Gantt charts, and dashboards. Its task structure includes owners, priorities, dependencies, time tracking, and custom fields, while documents, communication, and goal management are integrated into project spaces. It is suitable for teams that want to reduce switching among multiple tools.

Key Differences From Smartsheet

Smartsheet is closer to a spreadsheet with project management capabilities, while ClickUp is centered on tasks and project execution. Team members primarily open tasks to review requirements, update progress, and communicate, making daily collaboration more centralized. Complex formulas, cross-table calculations, and large volumes of structured business data are not its main strengths.

Which Teams Is It Best For?

ClickUp is suitable for product, engineering, marketing, and operations teams, especially those currently using separate task, document, chat, and goal-management tools and wanting to bring them into one platform.

7. Asana: For Teams That Emphasize Ownership and Project Processes

Product Information

What Is Asana?

Asana is a collaborative project management platform organized around projects, tasks, owners, deadlines, and dependencies. Teams can use lists, boards, calendars, timelines, and Gantt charts to move projects forward, while forms, rules, dashboards, and portfolios support cross-team work. Asana also provides AI Studio and AI Teammates for building intelligent workflows, generating status reports, and assisting with project tasks.

Why Is It a Suitable Smartsheet Alternative?

Asana covers common Smartsheet needs such as task assignment, project timelines, dependencies, automation, and progress reporting. Task ownership and project processes are clearly defined, allowing members to see what they are responsible for, when work is due, and which tasks are blocking the project.

Key Differences From Smartsheet

Smartsheet allows teams to organize data freely around worksheets, while Asana places greater emphasis on standardized task execution. It is suitable for breaking plans into projects, milestones, and tasks, but it is less flexible for complex data tables, formula calculations, and relationships across multiple tables.

Which Teams Is It Best For?

Asana is suitable for marketing campaigns, product launches, operational plans, and cross-functional projects, especially for teams that want clear task owners, deadlines, dependencies, and project goals.

Asana is better suited to project execution than directly replacing a complex database. The Advanced plan costs significantly more than Starter, while cross-project management capabilities such as portfolios, goals, and workloads are mainly available in Advanced and higher plans.

Three-Year Pricing Summary

Even when plans are labeled Team, Standard, or Pro, the included project views, automation, permissions, and data management capabilities can differ substantially among products.

The following table provides an approximate view of each product’s budget.

The calculations use publicly listed annual billing prices for five and 15 editable members over three consecutive years. For each product, we selected a representative plan that is more suitable for ongoing team use.

Product	Reference Plan	Three-Year Cost for 5 Users	Three-Year Cost for 15 Users	Pricing Notes
Smartsheet	Business	$3,420	$10,260	Per-member subscription; includes timelines, workload management, and unlimited automation
NocoBase	Standard	$800	$800	One-time license with no user-based pricing; server and maintenance costs are separate
Baserow	Advanced	$3,240	$9,720	Per-paid-user subscription; includes more complete role and field permissions
monday	Pro	$3,420	$10,260	Per-seat subscription; includes higher automation limits and workload management
SmartSuite	Professional	$5,760	$17,280	Per-editor subscription; includes advanced permissions and higher data capacity
Airtable	Team	$3,600	$10,800	Primarily charges for editors; read-only users generally do not require paid seats
ClickUp	Business	$2,160	$6,480	Per-user subscription; AI and some enterprise management capabilities may require additional purchases
Asana	Advanced	$4,498.20	$13,494.60	Per-user subscription; includes portfolios, workload management, and approvals

We hope this article helps you find a Smartsheet alternative that better fits your team. Feel free to share it with teams evaluating project management tools, multi-dimensional spreadsheets, open-source self-hosted platforms, or enterprise business systems.

Related reading:

How a Volunteer Fire Department Manages 200 Callouts a Year with NocoBase

NocoBase — Thu, 23 Jul 2026 07:49:58 +0000

Originally published at https://www.nocobase.com/en/blog/polish-volunteer-fire-department-nocobase-case-study

A Volunteer Fire Department in Poland

Volunteer fire departments are an essential part of Poland’s fire protection system. Although their members serve their communities as volunteers, they take on many of the same responsibilities as professional fire services, including regular training, emergency response, vehicle and equipment management, and tracking personnel certifications.

OSP Radlin II is one of these active units and the busiest volunteer fire department in its county. Its operational team includes 30 fully trained responders and handles around 200 emergency callouts each year.

For every callout, the team must ensure that responders are properly qualified, vehicles are ready, and equipment is available. They also need to accurately record who participated, how long the operation lasted, how far each vehicle traveled, and which supplies were used.

To manage this work more effectively, the members of OSP Radlin II began searching for a system that could better support the department’s real operational needs.

From Google Drive to NocoBase

Previously, OSP Radlin II mainly relied on free cloud storage tools such as Google Drive to store and share information.

As incident records, member details, medical checks, rescue certifications, vehicle inspections, and equipment records continued to grow, important information became scattered across multiple files. There was also no consistent way to structure or update the data.

Cloud storage worked well for keeping documents, but it could not support the workflows needed to run an active fire department.

The team needed a centralized, secure platform that could be fully adapted to the department’s real operational needs.

To find the right solution, they tested more than ten similar platforms. After several rounds of evaluation, they chose NocoBase.

An Operations System Built by the Whole Team

From the start, the system was a collaborative effort. Members contributed to data entry, workflow design, and system maintenance based on their responsibilities, gradually creating a clear division of work.

Some members handle administrative work, including:
- Tracking equipment inspection deadlines
- Managing routine medical checks
- Maintaining rescue certifications
- Handling funding applications and other administrative tasks
Commanders record information from each emergency callout, including:
- Incident records
- Callout details
- Lists of participating crew members

The system is no longer maintained by a single person. Instead, the members directly involved in each area keep the information up to date. Today, it supports most of the fire department’s day-to-day operations.

System Homepage

The homepage gives members a single place to access their work. Calendars, tasks, announcements, member information, and quick actions are all available from one interface, helping each role quickly find what they need.

Track equipment inspection deadlines
Manage routine medical checks
Track rescue certifications
Manage funding applications and other administrative work
Record emergency responses
Add incident descriptions
Maintain crew participation lists

Emergency Response and Incident Management

Members can quickly create emergency response records from a tablet or mobile phone. They can enter departure and return times, incident type, location, vehicles used, participating crew members, and supplies consumed.

NocoBase then turns this information into useful statistics, including the number and types of incidents, vehicle mileage, and the total time each firefighter has spent on emergency responses.

Personnel, Qualifications, and Administration

Beyond incident management, the department uses NocoBase to maintain member profiles, medical clearances, rescue certifications, and other specialist qualifications.

Members responsible for administrative work also use the system to track funding applications and other day-to-day office tasks.

The team has also created a separate project board for non-emergency work, such as fire station renovations, community events, and other internal projects.

Vehicles, Equipment, and Maintenance

Fire engines, trailers, and firefighting equipment are all managed in the same system.

Members can record vehicle usage, mileage, technical condition, annual inspection dates, and upcoming equipment inspection or maintenance deadlines.

Automating Routine Work

As more information was centralized in NocoBase, the department began using workflows to automate tasks that had previously relied on manual checks and reminders.

Deadline Reminders

The system automatically monitors and sends reminders for important dates that may affect operational readiness, including:

Member medical examination deadlines
Fire vehicle inspection dates
Member birthdays and other important dates

Emergency Response Hours

Based on incident records, the system automatically calculates how much time each firefighter has spent participating in emergency operations.

Team Communication

An automated announcement system allows management to share important updates more consistently through both email and in-app notifications.

A System That Continues to Grow

The OSP Radlin II system is now about 90% complete. It covers around 80 members across the organization, with approximately 20 active users regularly entering and maintaining data.

By bringing its data into one place, the department can more easily track emergency callouts, vehicle mileage, equipment status, and the time each firefighter spends on emergency responses.

More importantly, the system is not a one-time project that stops evolving once it goes live. As more members use it, new needs continue to emerge, and the team keeps adding new features, automations, and operational workflows.

OSP Radlin II has no dedicated software development team. Instead, its members have used their deep understanding of the department’s day-to-day work to gradually turn real firefighting operations into a system that can support the organization for years and continue evolving with its needs.

More Customer Stories:

Weekly Updates: Added RunJS API for AI Employee Tasks in JS Blocks

NocoBase — Mon, 20 Jul 2026 08:19:35 +0000

Summarize the weekly product update logs, and the latest releases can be checked on our blog.

NocoBase is currently updated across three branches: main, next, and develop.

main: The most stable version to date, recommended for installation.
next: Beta version, contains upcoming new features and has been preliminarily tested. There might be some known or unknown issues. It is mainly used to collect feedback from test users and further optimize features. Ideal for test users who want to experience new features early and provide feedback.
develop: Alpha version, contains the latest feature code, may be incomplete or unstable, and is mainly used for internal development and rapid iteration. Suited for technical users interested in cutting-edge product capabilities, but not recommended for production use.

main

v2.1.28

Release date: 2026-07-19

🐛 Bug Fixes

[client-v2] Fix mobile menus hidden incorrectly by device type rules (#10123) by @zhangzhonghe
[Workflow: Approval] Fix occasional errors when opening approval task details directly by @zhangzhonghe

v2.1.27

Release date: 2026-07-19

🚀 Improvements

[client-v2] Added Myanmar (my-MM) to the languages selectable in System Settings. (#10131) by @hongboji

🐛 Bug Fixes

[resourcer] Fixed pre-action workflows not triggering when used together with before-save approval workflows. (#10119) by @mytharcher
[flow-engine] Fix mobile popups exceeding the screen and hiding the close button (#10118) by @zhangzhonghe
[client-v2]
- Fix inconsistent route state after renaming a newly enabled page tab (#10117) by @zhangzhonghe
- Fix an error that could prevent approval pages from loading (#10116) by @zhangzhonghe
[utils] Ensured server-side outbound request redirects also comply with SERVER_REQUEST_WHITELIST (#10109) by @mytharcher
Reference: Environment variables
[Workflow: Approval] Fix messages overriding by @mytharcher

v2.1.26

Release date: 2026-07-17

🚀 Improvements

[undefined]
- Updated the data source documentation structure, links, and localized pages. (#10108) by @hongboji Reference: Data sources

🐛 Bug Fixes

[server] Prevented uploaded XML and other active content files from executing scripts in the application origin (#10104) by @mytharcher
[database] Fixed an SQL injection risk when reading database view metadata (#10115) by @2013xile
[client-v2]
- Reset unwanted border and shadow styles on Markdown h2 headings. (#10107) by @katherinehhh
- Corrected the Urdu label and added a separate Uzbek option to the System Settings language list. (#10090) by @hongboji
[AI employees] Fixed an error when sending files pasted into the AI employee chat input (#10106) by @cgyrock
[File storage: S3(Pro)] Fixed S3-compatible file URLs omitting the configured storage path, which caused uploaded logos and attachments to return 404 errors by @mytharcher

v2.1.25

Release date: 2026-07-15

🎉 New Features

[DingTalk] Added DingTalk Stream mode support for organization event synchronization. by @chenzhizdt
[Auth: LDAP] Added LDAP user data sync source support, including optional AD department synchronization. by @chenzhizdt

🚀 Improvements

[ai] Reduced main-process memory usage when parsing uploaded knowledge base documents. (#10083) by @cgyrock
[undefined]
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10047) by @mytharcher
[File storage: S3(Pro)] S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
[RabbitMQ queue adapter] Enhance the channel management and error recovery capabilities of the RabbitMQ adapter by @sdp-ncd

🐛 Bug Fixes

[User data synchronization] Fixed external department sync order so child departments can be reparented correctly when their parent is synced later. (#10028) by @chenzhizdt
[Collection field: Markdown(Vditor)] Fixed iframe sanitization for v1 Markdown rendering and editing. (#10096) by @katherinehhh
[Workflow] Fixed hidden fields being included when workflow serializes appended association data (#10086) by @mytharcher
[AI employees] Fixed AI tool-call approvals to authorize against the message's owning conversation before updating decisions. (#10077) by @cgyrock
[Data source: External NocoBase]
- Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
- Fixed workflow AI employees being unable to read attachments from External NocoBase data sources by @2013xile

v2.1.24

Release date: 2026-07-13

🐛 Bug Fixes

[client-v2]
- Fixed other column content showing through fixed v2 table columns when quick edit is enabled. (#10076) by @katherinehhh
- Fixed v2 scan input camera preview layout issues on iOS Chrome. (#10081) by @katherinehhh
[app] Fixed Redis cache configuration ignoring the dedicated cache URL (#10065) by @2013xile
[Action: Batch edit] Fixed Markdown editor initialization failure when a V2 form includes a process field. (#10080) by @katherinehhh
[AI employees] Fixed AI attachment handling to avoid trusting client-provided file paths or URLs. (#10037) by @cgyrock
[Workflow] Fixed manual workflow execution returning an error when a valid request does not start an execution. (#10049) by @mytharcher
[Redis worker ID allocator]
- Improved Redis worker ID isolation and failure diagnostics by @2013xile
- Restored standalone startup without Redis worker ID configuration by @2013xile
[Workflow: Approval] Filter approval file associations by current user ownership when the temporary switch is enabled. by @mytharcher

v2.2.0-beta.15

Release date: 2026-07-16

🎉 New Features

[client-v2]
- Tabs on pages, subpages and pop-ups support the configuration of linkage rules (#10099) by @zhangzhonghe
- Add an environment variable to configure legacy and modern route entry modes. (#9891) by @Molunerfinn
[AI employees] Added RunJS APIs for triggering AI employee tasks from JS blocks. (#10061) by @cgyrock
[Public forms] In the v1 public form, support creating v2 forms and prohibit creating v1 forms (#10045) by @zhangzhonghe
[Block: Comment]
- Improved comment block settings with data scope, default sorting, selectable page size, optional last-page jumping, and scalar owner field mapping. (#9954) by @jiannx
- Added a comments block. (#9916) by @jiannx
[Notification: Email] Migrated the workflow notification node client to v2, restored channel-specific notification forms, and kept legacy workflow route compatibility for migrated notification configuration. (#9817) by @jiannx
[Workflow: mailer node] Added v2 client support for configuring the workflow mailer node. (#9825) by @jiannx
[Workflow] Migrate the Workflow settings page to the v2 client and share a reusable draggable category-tabs component via @nocobase/client-v2. (#9645) by @Molunerfinn
[Workflow: Database transaction node] Added a client-v2 implementation for the workflow database transaction node while preserving the legacy client entry. by @katherinehhh
[Record history] Added client v2 support for the record history plugin. by @jiannx
[Workflow: Approval] Add approval initiation and todo blocks for v2 pages by @zhangzhonghe
[DingTalk] Added DingTalk Stream mode support for organization event synchronization. by @chenzhizdt

🚀 Improvements

[undefined]
- Updated the data source documentation structure, links, and localized pages. (#10108) by @hongboji Reference: Data sources
- Updated the data source documentation structure, links, and localized pages. (#10108) by @hongboji Reference: Data sources
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10103) by @mytharcher
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10047) by @mytharcher
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9942) by @sembaev-a-a
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9816) by @sembaev-a-a
- Improved AI knowledge base retrieval and documentation. (#9765) by @cgyrock
- Refined Russian documentation translation for improved wording, readability, and terminology consistency. (#9754) by @sembaev-a-a
[client-v2]
- Refactor Markdown Vditor into a unified plugin-backed Markdown engine with compatibility bridges for existing Markdown block and Vditor field plugins. (#9998) by @katherinehhh
- Refactor Markdown Vditor into a unified plugin-backed Markdown engine with compatibility bridges for existing Markdown block and Vditor field plugins. (#9998) by @katherinehhh
[Workflow: Manual node] Show manual workflow tasks in the V2 task center and guide users to the legacy page for processing (#10085) by @zhangzhonghe
[Workflow]
- Unsupported workflow v2 canvas nodes now keep the normal node card actions while showing the node type as unsupported. (#10054) by @mytharcher
- Simplified workflow v2 create/update field assignment, improved selected variable display, and avoided generating unused assign-form model data. (#9887) by @katherinehhh
- Exported workflow v2 canvas extension APIs for downstream workflow node plugins. (#9834) by @katherinehhh
- Migrate the workflow output node configuration to v2 and align v2 workflow result viewers with the legacy display behavior for string results. (#9813) by @Molunerfinn
- Migrate the workflow end node to the v2 implementation. (#9795) by @Molunerfinn
[AI employees]
- Improved AI employee tool settings, data-query guardrails, relation field querying, and malformed tool call diagnostics. (#10042) by @cgyrock
- Improved AI employee web search to reduce unnecessary model reasoning and better use provider-specific thinking controls. (#9996) by @cgyrock
- Removed the deprecated Datasource entry from AI employee settings and context selection in the v2 UI. (#9988) by @cgyrock
- Migrated the AI employee plugin to client-v2. (#9794) by @cgyrock
[Collection: SQL] Not user-facing; added client-v2 unit test coverage for migrated plugins. (#9967) by @katherinehhh
[Block: Comment]
- Improved comment submit actions and fixed related comment/user form submission issues. (#10002) by @jiannx
- Added the new comment block plugin to the NocoBase preset and marked the legacy comments plugin as deprecated. (#9936) by @jiannx
[Users] Improve client-v2 test coverage for the users plugin. (#9975) by @jiannx
[Logger] Added the Logger settings page to the client v2 runtime. (#9933) by @jiannx
[Workflow: Aggregate node] Improved v2 workflow field selection for update and aggregate query nodes, including safer associated collection selection in aggregate query nodes. (#9938) by @katherinehhh
[Workflow: JavaScript]
- Aligned v2 workflow request and mailer node configuration fields with legacy layout and attachment variable behavior. (#9952) by @jiannx
- Migrated the JavaScript workflow node to client-v2 (#9805) by @jiannx
[Workflow: JSON calculation] Migrated the workflow JSON calculation node configuration UI to the v2 workflow canvas while preserving v1 canvas compatibility. (#9902) by @mytharcher
[Backup manager] Tables whose collection dataCategory is marked as 'runtime' are now excluded from backups automatically. (#9804) by @cgyrock
[Workflow: Custom action event] Migrated workflow triggers and bind-workflow settings to client-v2, including action trigger, custom action trigger, request interception trigger, and submit/update action workflow binding settings. (#9845) by @mytharcher
[Workflow: HTTP request node] Migrated the workflow HTTP request node to client-v2. (#9806) by @jiannx
[HTTP request encryption] Added v2 client support for HTTP request encryption so query parameters continue to be encrypted in the v2 client. by @jiannx
[Workflow: Database transaction node] Improved the v2 workflow database transaction node layout so branch labels and the commit marker have better spacing. by @katherinehhh
[AI: Knowledge base] Migrated the AI knowledge base settings pages to the v2 client and fixed layout and loading issues in knowledge base and vector store pages. by @cgyrock
[File storage: S3(Pro)] S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
[Email manager] Moved the department-based mail viewing option to the V1 general mail settings page, prevented service credential saves from overwriting it, and placed V2 General settings before Service provider settings. by @jiannx

🐛 Bug Fixes

[client-v2]
- Corrected the Urdu label and added a separate Uzbek option to the System Settings language list. (#10090) by @hongboji
- Fixed automatic SSO redirect providers failing to preserve authentication order in production builds (#10100) by @jiannx
- Workflow filters now preserve workflow variable expressions and show a clear parsing error when variable metadata cannot be resolved. (#10088) by @Molunerfinn
- Fix an error in v2 workflow value editors when a collection field is named nodeName. (#10067) by @katherinehhh
- Fixed workflow v2 variable editors to preserve saved variable pills, disabled states, and operator labels consistently across trigger, filter, and field assignment forms. (#10041) by @Molunerfinn
- Fixed an issue where v2 workflow assigned fields could still be edited in read-only executed workflow versions. (#10014) by @katherinehhh
- Fix workflow execution revision navigation so creating a new version after manual execution opens the correct workflow page in both legacy and modern shells. (#9955) by @Molunerfinn
[flow-engine] Fixed an issue where users could type extra text after selecting a variable in single-value variable inputs. (#10050) by @katherinehhh
[AI employees] Fixed an error when sending files pasted into the AI employee chat input (#10106) by @cgyrock
[Authentication]
- Fixed declaration generation errors in the v2 authenticator management page (#10095) by @jiannx
- Fixed missing saved Authenticator settings when editing authenticators in the v2 authentication manager. (#10091) by @jiannx
[Notification manager]
- Fix receiver selection saving user IDs as text (#10093) by @zhangzhonghe
- Fix incorrect workflow variables shown in CC configuration (#9937) by @zhangzhonghe
[Workflow: JSON variable mapping] Fix an error when selecting loop scope variables in the JSON variable mapping workflow node. (#10094) by @Molunerfinn
[UI layout] Fix the Mobile settings link losing the current sub-application path (#10078) by @zhangzhonghe
[Workflow]
- Workflow form controls now correctly inherit the disabled state when viewing executed workflows. (#10079) by @Molunerfinn
- Refresh the workflow canvas after updating trigger configuration (#10068) by @zhangzhonghe
- Fixed workflow v2 condition operands to stay on one row by default and wrap correctly when selected variable paths are too long. (#10033) by @Molunerfinn
- Fix display and detail loading issues in the workflow v2 task center (#10001) by @zhangzhonghe
- Fix untranslated workflow result labels and oversized CC configuration dialogs (#9977) by @zhangzhonghe
- Fix workflow context mismatches across bundles so branches and some variable pickers work correctly in legacy workflow pages. (#9951) by @Molunerfinn
- Fix the issue where in-app message content cannot be configured in v2 workflows (#9885) by @zhangzhonghe
- Fix issues after migrated client to v2 (#9929) by @mytharcher
- Restored debounced remote search for workflow collection trigger manual execution and aligned the selector with the v1 200-record fetch behavior. (#9870) by @Molunerfinn
- Fixed the workflow v2 add-node menu so unavailable node types are disabled according to workflow and branch rules (#9855) by @mytharcher
[Workflow: Delay node] Fix delay node duration input and prevent values below the minimum from being saved. (#10056) by @Molunerfinn
[Workflow: Aggregate node] Fix validation rule to allow null filter (#10053) by @mytharcher
[Public forms] Fix the issue where public forms can still be configured when UI Editor is off (#10036) by @zhangzhonghe
[Block: Comment] Adjusted the default action order for new Comment blocks. (#9976) by @jiannx
[Workflow: mailer node] Fixed workflow v2 test failures caused by missing mocks for trigger workflow action registration. (#9863) by @jiannx
[Workflow: JavaScript] Fixed JavaScript workflow node registration failure in the legacy workflow client. (#9826) by @jiannx
[Workflow: Response message] Migrated the workflow response message node to the v2 canvas and fixed unsupported workflow types being able to add it. (#9830) by @jiannx
[File manager] Fixed 404 errors when uploading files to attachment URL fields in external data sources (#9809) by @2013xile
[Verification: TOTP authenticator] Fixed TOTP authenticator bindings so temporary setup secrets are removed and previously verified codes cannot be reused. by @jiannx
[Auth: SAML 2.0] Fixed SAML automatic sign-in redirects for unauthenticated users in the modern client while preserving the original destination path by @jiannx
[AI: Knowledge base] Added an overwrite option for AI knowledge base workflow document creation, allowing workflows to replace existing documents with the same key. by @cgyrock
[Data source: External NocoBase] Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
[plugin-service-platform]
- Restored licensed plugin downloads from the service platform. by @jiannx
- Disabled the service platform plugin download endpoint. by @jiannx
[Workflow: Subflow] Fixed workflow title search in the subflow node configuration selector. by @mytharcher
[File storage: S3(Pro)] Fixed S3-compatible file URLs omitting the configured storage path, which caused uploaded logos and attachments to return 404 errors by @mytharcher
[Auth: OIDC] Fixed OIDC automatic login redirects in production builds and retained the original modern-client path after login by @jiannx
[Workflow: Approval]
- Fix blank approval forms and missing or incorrect action buttons by @zhangzhonghe
- Fixed premature applicant validation and untranslated role labels in the approval workflow manual execution dialog. by @Molunerfinn
- Fix the approval workflow task title remaining editable in executed workflow configurations after production builds. by @Molunerfinn
- Allow users to view approval interfaces and cards after a workflow has been executed by @zhangzhonghe
- Fix workflow form action buttons responding in configuration dialogs by @zhangzhonghe
- Fix display and action issues in approval initiator interfaces by @zhangzhonghe
- Close the Apply new drawer when opening an approval form by @zhangzhonghe
- Fix an error that could prevent V2 pages from opening when approval and notification plugins are enabled by @zhangzhonghe
- Fix approval task form and action issues in the workflow v2 task center by @zhangzhonghe
- Fix v2 approval subtables not displaying correctly in details by @zhangzhonghe
- Fix missing processed approval details in v2 task detail popups by @zhangzhonghe
- Fix empty approval interfaces and fixed assignee IDs by @zhangzhonghe
- Fix the issue where approval tables appear in the block data source list by @zhangzhonghe
- Fix issues involved by migrating to client v2 by @mytharcher
- Fix the error when configuring approval workflow conditions by @zhangzhonghe
- Guide users to V1 pages when approval interfaces cannot be used in V2 by @zhangzhonghe
- Fix approval assignee sorting and hide unsupported legacy configuration entries by @zhangzhonghe
- Fix the error when opening CC node settings by @zhangzhonghe
- Fix missing approval data on approval task cards by @zhangzhonghe
[Collection field: Signature] Fix client-v2 signature field file collection selector localization and option filtering. by @katherinehhh
[WeCom] Fixed WeCom notification channels not saving the selected authenticator. by @jiannx

v2.2.0-beta.14

Release date: 2026-07-15

🎉 New Features

[Auth: LDAP] Added LDAP user data sync source support, including optional AD department synchronization. by @chenzhizdt

🚀 Improvements

[ai] Reduced main-process memory usage when parsing uploaded knowledge base documents. (#10083) by @cgyrock
[undefined] File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10047) by @mytharcher
[Flow engine] Support multi portals for ui build apis. (#10072) by @gchust
[File storage: S3(Pro)] S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
[RabbitMQ queue adapter] Enhance the channel management and error recovery capabilities of the RabbitMQ adapter by @sdp-ncd

🐛 Bug Fixes

[client-v2]
- Fixed other column content showing through fixed v2 table columns when quick edit is enabled. (#10076) by @katherinehhh
- Fixed v2 scan input camera preview layout issues on iOS Chrome. (#10081) by @katherinehhh
[Workflow]
- Fixed hidden fields being included when workflow serializes appended association data (#10086) by @mytharcher
- Fixed manual workflow execution returning an error when a valid request does not start an execution. (#10049) by @mytharcher
[Collection field: Markdown(Vditor)] Fixed iframe sanitization for v1 Markdown rendering and editing. (#10096) by @katherinehhh
[Action: Batch edit] Fixed Markdown editor initialization failure when a V2 form includes a process field. (#10080) by @katherinehhh
[UI layout] Fixed the Mobile settings link opening the main application from a sub-application. (#10075) by @katherinehhh
[AI employees]
- Fixed AI tool-call approvals to authorize against the message's owning conversation before updating decisions. (#10077) by @cgyrock
- Fixed AI attachment handling to avoid trusting client-provided file paths or URLs. (#10037) by @cgyrock
[User data synchronization] Fixed external department sync order so child departments can be reparented correctly when their parent is synced later. (#10028) by @chenzhizdt
[Data source: External NocoBase]
- Fixed workflow AI employees being unable to read attachments from External NocoBase data sources by @2013xile
- Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
[Workflow: Approval] Filter approval file associations by current user ownership when the temporary switch is enabled. by @mytharcher

develop

v2.2.0-alpha.9

Release date: 2026-07-16

🎉 New Features

[client-v2] Tabs on pages, subpages and pop-ups support the configuration of linkage rules (#10099) by @zhangzhonghe
[AI employees] Added RunJS APIs for triggering AI employee tasks from JS blocks. (#10061) by @cgyrock
[DingTalk] Added DingTalk Stream mode support for organization event synchronization. by @chenzhizdt
[Auth: LDAP] Added LDAP user data sync source support, including optional AD department synchronization. by @chenzhizdt

🚀 Improvements

[undefined]
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10047) by @mytharcher
- File URLs now use stable NocoBase access URLs so permissions can be checked before redirecting to storage. (#10103) by @mytharcher
- Updated the data source documentation structure, links, and localized pages. (#10108) by @hongboji Reference: Data sources
[ai] Reduced main-process memory usage when parsing uploaded knowledge base documents. (#10083) by @cgyrock
[Workflow: Manual node] Show manual workflow tasks in the V2 task center and guide users to the legacy page for processing (#10085) by @zhangzhonghe
[File storage: S3(Pro)]
- S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
- S3 Pro uploads now return the created file record with permanent file URLs. by @mytharcher
[RabbitMQ queue adapter] Enhance the channel management and error recovery capabilities of the RabbitMQ adapter by @sdp-ncd
[Email manager] Moved the department-based mail viewing option to the V1 general mail settings page, prevented service credential saves from overwriting it, and placed V2 General settings before Service provider settings. by @jiannx

🐛 Bug Fixes

[client-v2]
- Fixed automatic SSO redirect providers failing to preserve authentication order in production builds (#10100) by @jiannx
- Corrected the Urdu label and added a separate Uzbek option to the System Settings language list. (#10090) by @hongboji
- Workflow filters now preserve workflow variable expressions and show a clear parsing error when variable metadata cannot be resolved. (#10088) by @Molunerfinn
- Fixed v2 scan input camera preview layout issues on iOS Chrome. (#10081) by @katherinehhh
- Fixed other column content showing through fixed v2 table columns when quick edit is enabled. (#10076) by @katherinehhh
[Authentication]
- Fixed declaration generation errors in the v2 authenticator management page (#10095) by @jiannx
- Fixed missing saved Authenticator settings when editing authenticators in the v2 authentication manager. (#10091) by @jiannx
[AI employees]
- Fixed an error when sending files pasted into the AI employee chat input (#10106) by @cgyrock
- Fixed AI tool-call approvals to authorize against the message's owning conversation before updating decisions. (#10077) by @cgyrock
- Fixed AI attachment handling to avoid trusting client-provided file paths or URLs. (#10037) by @cgyrock
[Collection field: Markdown(Vditor)] Fixed iframe sanitization for v1 Markdown rendering and editing. (#10096) by @katherinehhh
[Workflow]
- Fixed hidden fields being included when workflow serializes appended association data (#10086) by @mytharcher
- Workflow form controls now correctly inherit the disabled state when viewing executed workflows. (#10079) by @Molunerfinn
- Refresh the workflow canvas after updating trigger configuration (#10068) by @zhangzhonghe
[Notification manager] Fix receiver selection saving user IDs as text (#10093) by @zhangzhonghe
[UI layout]
- Fix the Mobile settings link losing the current sub-application path (#10078) by @zhangzhonghe
- Fixed the Mobile settings link opening the main application from a sub-application. (#10075) by @katherinehhh
[Workflow: JSON variable mapping] Fix an error when selecting loop scope variables in the JSON variable mapping workflow node. (#10094) by @Molunerfinn
[User data synchronization] Fixed external department sync order so child departments can be reparented correctly when their parent is synced later. (#10028) by @chenzhizdt
[Action: Batch edit] Fixed Markdown editor initialization failure when a V2 form includes a process field. (#10080) by @katherinehhh
[Verification: TOTP authenticator] Fixed TOTP authenticator bindings so temporary setup secrets are removed and previously verified codes cannot be reused. by @jiannx
[Data source: External NocoBase]
- Fixed workflow AI employees being unable to read attachments from External NocoBase data sources by @2013xile
- Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
- Fixed file preview, permanent URL handling, and upload routing for external NocoBase file collections, including S3 Pro uploads by @mytharcher
[Auth: SAML 2.0] Fixed SAML automatic sign-in redirects for unauthenticated users in the modern client while preserving the original destination path by @jiannx
[File storage: S3(Pro)] Fixed S3-compatible file URLs omitting the configured storage path, which caused uploaded logos and attachments to return 404 errors by @mytharcher
[Auth: OIDC] Fixed OIDC automatic login redirects in production builds and retained the original modern-client path after login by @jiannx
[Workflow: Approval]
- Fix the approval workflow task title remaining editable in executed workflow configurations after production builds. by @Molunerfinn
- Fixed premature applicant validation and untranslated role labels in the approval workflow manual execution dialog. by @Molunerfinn
- Fix workflow form action buttons responding in configuration dialogs by @zhangzhonghe
- Allow users to view approval interfaces and cards after a workflow has been executed by @zhangzhonghe
- Filter approval file associations by current user ownership when the temporary switch is enabled. by @mytharcher
- Fix display and action issues in approval initiator interfaces by @zhangzhonghe
- Fix blank approval forms and missing or incorrect action buttons by @zhangzhonghe
- Fix an error that could prevent V2 pages from opening when approval and notification plugins are enabled by @zhangzhonghe
- Guide users to V1 pages when approval interfaces cannot be used in V2 by @zhangzhonghe
[WeCom] Fixed WeCom notification channels not saving the selected authenticator. by @jiannx