NocoDB 0.301.4 released on 17-03-2026
NocoDB 0.301.4 is out now. Workspace-level roles and permission inheritance replace the old Organisation model with a Default Workspace model so users invited at workspace level inherit access across all bases, and advanced workspace-level controls are now available for self-hosted deployments.
See the full notes on GitHub or read the Workspace & Base collaboration docs for details and the complete changelog: changelog (0.301.3…0.301.4) and Workspace & Base collaboration.
What’s in this release
- Permission model: a unified Default Workspace with roles (Owner, Creator, Editor, Commenter, Viewer, No Access) that grant inherited access across all bases in a workspace; existing base-level permissions continue to be respected.
- Bug fixes and security patches: fixes for view-edit lock inconsistencies, slow grid performance with Links/Lookup columns, metadata/PATCH errors (including primary key and checkbox constraints), Data API v3 primary key omission, clipboard and package resolution issues, text overflow in multilingual UI, rollup/currency formatting, shared-base/view issues, and XSS vulnerabilities.
- UX, views and features: keyboard shortcuts and menu access, map view experiments, timeline2, autonumber field type, drag-files-to-create-records, cross-section view drag-and-drop, Excel import, Dashboard V3 API, and responsive UI and sidebar refactors.
Upgrade notes
- No change to existing base-level permissions — previously configured base access is still respected; review the Workspace & Base collaboration docs for how workspace-level roles apply.
- If you need detailed API, deployment or bugfix information, consult the full changelog on GitHub for the compare 0.301.3…0.301.4 to see the closed issues and pull requests.
Share your experience with the update — what worked, what didn’t, and any quirks you spot when moving to workspace-level roles.