NocoDB 2026.08.0 released on 05-08-2026

NocoDB 2026.08.0 is out now. Admins and developers benefit from Interfaces (beta) for building focused, app-like pages on top of bases, alongside platform-wide security hardening and new self-hosting controls.
See the full release notes on the NocoDB GitHub and consult the Interfaces documentation for examples and configuration details.
What’s in this release
- Interfaces (beta): create focused pages (review queues, dashboards, forms, internal tools) that present only the data and actions each audience needs; available on NocoDB Cloud (Plus plan and above) and licensed self-hosted deployments (Business plan and above). Includes visual examples and Interfaces docs.
- Security hardening and self-hosting controls: stronger validation of filters, redirects, connection and OAuth params; consistent enforcement of view filters/hidden fields and record-level security across realtime and cached paths; session token rotation and OAuth flow improvements; embedding protection via frame headers and dependency updates. Self-hosted additions include license plan management, a toggle to hide paid-feature badges on unlicensed instances, and three NC_AI_* environment variables to tune AI assistant token budgets.
- Data, API and formula improvements: dynamic conditions for Record-Level Security referencing current user, email, teams and system fields; a WEEKNUM(date, [startDayOfWeek]) formula matching spreadsheet behaviour; v3 API link updates scoped to requested records, v3 field-options delete accepting option titles, fixes to server-side createRecordsAsync, and safer behaviour when duplicating records so linked records are not silently detached.
Upgrade notes
- API change: PATCH /api/v1/users no longer alters default workspace access. Migrate integrations that relied on that behaviour to the v3 endpoints: POST /api/v3/meta/bases/{baseId}/members (grant base access) or POST /api/v3/meta/workspaces/{workspaceId}/members (grant workspace access).
- If you need to revert, confirm the release assets you require are available on GitHub before rolling back — missing standalone binaries from earlier releases were addressed in this cycle.
Share how the upgrade goes: open an issue on GitHub or post feedback through the NocoDB community channels.


