+
+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.
+
+
+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.
+
+
+Organise your workspace the way your organisation actually works. Let Teams handle the rest.
+
+
+### Why This Changes Everything
+
+**Before:**
+
+❌ Assign the same role 15 times for every teammate
+
+❌ Reconfigure access every time someone joins or leaves
+
+❌ No clean way to reflect your org structure
+
+❌ Hard to audit who has access to what
+
+**After:**
+
+✅ **Group people into Teams**—Engineering, Design, Sales, Ops, anything
+
+âś… **Assign one role to the team**, and everyone inherits it
+
+âś… Onboard / off-board with a single action
+
+âś… **Crystal-clear permission logic** with smart inheritance
+
+âś… Clean, consistent, enterprise-ready access management
+
+---
+
+**Create Team**
+
+
+
+**Invite Teams to Workspace**
+
+
+
+**Team List**
+
+
+
+**Table permissions using Teams**
+
+
+
+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)
+
+## 🚀 Introducing NocoSync — Effortless, Automated Data Sync from Your Favorite Tools
+
+> I update tickets in GitHub, but my NocoDB tables stay outdated. I keep exporting and importing CSVs just to stay in sync.
+
+> 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.
+
+> 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.
+
+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.
+
+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.
+
+Say goodbye to silos. Focus on insights, not syncing. [Learn more →](https://nocodb.com/docs/product-docs/noco-sync)
+
+
+
+### How Sync Works?
+
+**General configurations**
+
+
+**Select Sources**
+
+
+**Review**
+
+
+
+**Monitor Progress**
+
+
+
+**Sync Data in NocoDB Tables**
+
+
+
+### **What Next?**
+
+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.
+
+
+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.
+
+---
+
+## Other updates
+
+### Performance Improvements
+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.
+
+### UTF-8-BOM Support for CSV Exports
+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.
+
+---
+
+
+
+
+
+
diff --git a/content/changelog/meta.json b/content/changelog/meta.json
index 72ac1716..bb5d1faa 100644
--- a/content/changelog/meta.json
+++ b/content/changelog/meta.json
@@ -1,3 +1,3 @@
{
- "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"]
+ "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"]
}
diff --git a/public/img/changelog/20251100/release.png b/public/img/changelog/20251100/release.png
new file mode 100644
index 0000000000000000000000000000000000000000..9d156dc772a6b4b36cb466969863c7f77ef34f61
GIT binary patch
literal 1870153
zcmV(^K-IsAP)AjDcFd<3OaqmHm!FLlWnVjf-Bz
zHt`8S9jQm|H^w&w^iy#x$1DDM@K^lf7sUT5sk3@RPA=Ri<;BIfNzmT$INd6!d;Pr2>HQ*1P&HjduV-|JuA5Ot}~qvpEC|F}YNQ0W-1aS^2>
zKs7#wY`5u8_@6)%g4EoK;pAT5RQ*-