Skip to content

Commit 1a80ddc

Browse files
authored
Merge pull request #484 from nocodb/docs/release-nov
docs: release notes
2 parents fc10615 + c0cc459 commit 1a80ddc

File tree

14 files changed

+132
-1
lines changed

14 files changed

+132
-1
lines changed

content/changelog/2025.11.0.mdx

Lines changed: 131 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,131 @@
1+
---
2+
title: '2025.11.0'
3+
description: 'Feature release : Introducing Teams & NocoSync'
4+
---
5+
6+
![Image](/img/changelog/20251100/release.png)
7+
8+
## 🚀 Introducing Teams — Smart, Scalable Access Control for Modern Workspaces
9+
10+
> Our engineering team changed structure, and now I’m manually updating access for every single person across multiple projects.
11+
12+
> Someone joins or leaves the company, and suddenly I’m hunting through dozens of bases to update their permissions individually.
13+
14+
<img src="/img/changelog/20251100/teams-slide.png" alt="Image" width="80%"></img>
15+
16+
You've finally set up the perfect permission model for one project—carefully assigning roles to every individual user. Then a new teammate joins, or someone switches departments, and suddenly **you're repeating the same permission updates** across multiple bases. Add Viewer here. Editor there. Remove access somewhere else. Each change is manual, repetitive, and easy to get wrong. Your workspace grows, and so does the permission chaos.
17+
18+
19+
Introducing **Teams**. Group your users once, assign a role to the team, and every member instantly inherits the right access. New people join? Add them to the team. Someone moves? Switch their team. Access updates everywhere—automatically. No more chasing individual permissions or fixing inconsistent setups.
20+
21+
22+
Organise your workspace the way your organisation actually works. Let Teams handle the rest.
23+
24+
25+
### Why This Changes Everything
26+
27+
**Before:**
28+
29+
❌ Assign the same role 15 times for every teammate
30+
31+
❌ Reconfigure access every time someone joins or leaves
32+
33+
❌ No clean way to reflect your org structure
34+
35+
❌ Hard to audit who has access to what
36+
37+
**After:**
38+
39+
**Group people into Teams**—Engineering, Design, Sales, Ops, anything
40+
41+
**Assign one role to the team**, and everyone inherits it
42+
43+
✅ Onboard / off-board with a single action
44+
45+
**Crystal-clear permission logic** with smart inheritance
46+
47+
✅ Clean, consistent, enterprise-ready access management
48+
49+
---
50+
51+
**Create Team**
52+
![Image](/img/changelog/20251100/team-add-member.png)
53+
54+
55+
**Invite Teams to Workspace**
56+
![Image](/img/changelog/20251100/team-invite.png)
57+
58+
59+
**Team List**
60+
![Image](/img/changelog/20251100/team-list.png)
61+
62+
63+
**Table permissions using Teams**
64+
![Image](/img/changelog/20251100/team-table-permission.png)
65+
66+
67+
Teams are built for speed and scale—your workspace grows without the chaos. Say goodbye to repetitive permission management and adopt structured, scalable access control that evolves with your organisation. [Learn more →](https://nocodb.com/docs/product-docs/collaboration/teams)
68+
69+
## 🚀 Introducing NocoSync — Effortless, Automated Data Sync from Your Favorite Tools
70+
71+
> I update tickets in GitHub, but my NocoDB tables stay outdated. I keep exporting and importing CSVs just to stay in sync.
72+
73+
> Every time a ticket is updated, I have to repeat the entire import process. I just want my data in NocoDB to stay up to date automatically.
74+
75+
> I plan dashboards in NocoDB, but the real activity happens in GitHub or Zendesk. Without a way to sync them, our data stays fragmented across tools.
76+
77+
Data lives everywhere—**GitHub, Gitlab, Zendesk, Freshdesk**—while your reports and dashboards live in NocoDB. Every time you need a single view, you export CSVs, run scripts, normalise fields, and stitch everything together. And the moment something changes, you repeat the whole process.
78+
79+
Introducing **NocoSync**. Connect your external tools and bring data directly into NocoDB. With predefined schemas, automatic relationships, and scheduled updates, your tables stay up to date—no manual imports, scripts, or patchwork workarounds.
80+
81+
Say goodbye to silos. Focus on insights, not syncing. [Learn more →](https://nocodb.com/docs/product-docs/noco-sync)
82+
83+
<img src="/img/changelog/20251100/sync-slide.png" alt="Image" width="80%"></img>
84+
85+
### How Sync Works?
86+
87+
**General configurations**
88+
![Image](/img/changelog/20251100/sync-setup.png)
89+
90+
**Select Sources**
91+
![Image](/img/changelog/20251100/sync-sources.png)
92+
93+
**Review**
94+
![Image](/img/changelog/20251100/sync-review.png)
95+
96+
97+
**Monitor Progress**
98+
![Image](/img/changelog/20251100/sync-progress.png)
99+
100+
101+
**Sync Data in NocoDB Tables**
102+
![Image](/img/changelog/20251100/sync-table.png)
103+
104+
105+
### **What Next?**
106+
107+
Phase-2 (expected in Jan 2026) will expand NocoSync's capabilities significantly. You will be able to sync additional categories such as **CRM, File Storage, HRIS, ATS, Accounting**, and more, covering the full spectrum of tools your teams rely on. Each category will support multiple integration sources, allowing you to consolidate data from several platforms into a **single schema**, eliminating silos entirely.
108+
109+
110+
With **Unified APIs**, you'll be able to query, analyze, and build workflows across all connected sources from one place, without worrying about field mismatches, inconsistent naming, or manual data normalisation. This means you can create cross-tool dashboards, generate reports combining data from multiple systems, and automate processes that span several platforms—all directly in NocoDB. Phase-2 will make NocoSync not just a sync tool, but a **centralised integration layer** for your entire workspace.
111+
112+
---
113+
114+
## Other updates
115+
116+
### New Integrations: Make, Zapier, and Workato
117+
New integrations with **Make** (using v3 APIs), **Zapier**, and **Workato** expand your automation possibilities across the tools you already use. With these additions, you can connect NocoDB to hundreds of external systems, trigger workflows based on data changes, and streamline cross-platform operations without writing code. These integrations make it easier to embed NocoDB seamlessly into your existing automation ecosystem.
118+
119+
### Performance Improvements
120+
We introduced a series of performance optimisations across the API layer to deliver faster, more responsive interactions throughout the product. These improvements include more efficient query execution paths, smarter caching at critical junctions, and streamlined permission checks. Together, these enhancements significantly lower API response times—especially for complex operations—resulting in a smoother, more predictable experience as your data grows.
121+
122+
### UTF-8-BOM Support for CSV Exports
123+
CSV exports now support the **UTF-8-BOM (utf-8-sig)** encoding option, ensuring special characters are preserved accurately across tools that require a byte-order mark for proper rendering. This enhancement improves compatibility with spreadsheet applications—especially those that previously misread accented characters, non-Latin scripts, or symbols—so your exported data opens reliably without encoding issues.
124+
125+
---
126+
127+
128+
129+
130+
131+

content/changelog/meta.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
{
2-
"pages": ["2025.10.2", "2025.10.1", "2025.10.0", "2025.09.0", "2025.08.0", "2025.07.0", "2025.06.0", "2025.05.0"]
2+
"pages": ["2025.11.0", "2025.10.2", "2025.10.1", "2025.10.0", "2025.09.0", "2025.08.0", "2025.07.0", "2025.06.0", "2025.05.0"]
33
}
1.78 MB
Loading
387 KB
Loading
302 KB
Loading
429 KB
Loading
3.41 MB
Loading
389 KB
Loading
749 KB
Loading
358 KB
Loading

0 commit comments

Comments
 (0)