# September 25, 2025 / Disable public sharing in a workspace, Rename "Name" field **URL:** \ **Category:** Changelog\ **Created:** [September 25, 2025, 2:28pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680 "2025-09-25T14:28:21Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 25, 2025, 2:28pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/1 "2025-09-25T14:28:21Z")
## Disable public sharing in a workspace 💰 This feature is available in Enterprise plan only If your organization doesn’t mess around with security and wants to prevent any information leaks to the internet, you can now disable public sharing in the entire workspace: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/38f440309f7b5b44f3ccefe324dceab3d765dc08.jpeg) This would make it impossible to publicly share Entities, Documents, Whiteboards, Reports, Spaces, or Forms. The existing shares won’t be affected though. To restrict public sharing, go to `Settings → Public Sharing` and enable the corresponding toggle. Why a separate page, you ask? Well, you have to see what’s already been shared — this is coming next, stay tuned! 😉 ## Rename “Name” field We’re continuing to remove weird limitations in Fibery. > Why I can’t rename a Name Field? It’s driving me nuts. In Airtable, I can. and > Fibery is AMAZING, and the devs have done a great job, but there are these limitations that seem weirdly simple that they can’t or won’t resolve. I really don’t understand. Finally, you can rename the **“Name”** field! It’s still not possible to delete it (and it never will be), but at least you can make it more semantically relevant. ![Screenshot 2025-09-25 at 5.25.35 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b42956450ba60bc59e3e4c630c3b332be8807cdf.png) ## 🦋 Improvements - **Sync data from Slack is back!** Slack postponed a decision to [change API rate limits to ridiculously low](https://api.slack.com/changelog/2025-05-terms-rate-limit-update-and-faq) at least till March 2026, so we’ve got back Slack Integration to templates and integration sources. We hope they will reconsider and keep things as is, or we will find new ways to keep it working. We’ll see. - **Performance:** We’ve improved performance for views when entities contain large collections. In the past we loaded all the data, now we load first 1000 items. It could affect some super rare cases when you copy cells or export grids with huge collections, but most likely nobody will hit such problems. ## 🪦 Deteriorations We’ve [deprecated](https://community.fibery.io/t/why-we-re-sunsetting-the-referral-program/9682) the Referral Program and removed the referral page (along with the option to copy your invite link) from the UI. If you’ve already shared a link or have any credits — no worries, they’ll stay active and can be redeemed until January 31, 2026. 🪙 Our initial bet was that the program would help amplify our already well-working word-of-mouth channel. But after 6 months live and two iterations, fewer than 100 users invited anyone. Cold-start problem? Misaligned incentives? Maybe. We’ll explore better uses for credits later on. ## 🦐 Fixed Bugs - **Undo:** It’s quite unexpected that after restoring drop-down values are not displayed while they were actually restored - **Integrations** : - Wrong title for field mapped to People - Wrong field name for People - Assignees Emails instead of Assignees - User relation is unexpectedly skipped even when was selected - **Entity View** : - Multi-Entity View Rules are applied for Publicly shared entity - Error when Non-Creators try to edit rules - **Rename/Delete Space/Database/Field** : Not user-friendly text of the message on deleting some Spaces in the workspace - **History & Audit Log** : Entity logs show access template id instead of name P.S. We’ve completed 6-weeks-long migration of all accounts to new v2 permissions model. You will see and feel nothing, but for us it finally unlocks next permissions improvements, makes permissions calculations way faster, and now Fibery can hold 10K users in a single account (maybe, we will find out soon). ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 25, 2025, 2:28pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/2 "2025-09-25T14:28:28Z")
---
**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\ **Post date:** [September 25, 2025, 2:43pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/3 "2025-09-25T14:43:04Z")
Haha love the Age of Empires 2 theme 🏰 My favourite update here is to the option to Rename the “Name” field. It’s a “nice to have” not a “must have”. But nice to make some data make a bit more sense. ---
**Author:** ![timothy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/timothy/32/11812_2.png) [@timothy](https://community.fibery.io/u/timothy)\ **Post date:** [September 25, 2025, 2:49pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/4 "2025-09-25T14:49:07Z")
This made my day! ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [September 25, 2025, 3:11pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/5 "2025-09-25T15:11:58Z")
> [@mdubakov](#): > > it finally unlocks next permissions improvements, makes permissions calculations way faster, and now Fibery can hold 10K users in a single account (maybe, we will find out soon). Super exciting!! Is the “Define Access to User Database” on the roadmap for new permissions features? > [@mdubakov](#): > > Finally, you can rename the **“Name”** field! It’s still not possible to delete it (and it never will be), but at least you can make it more semantically relevant. Very nice! It’s interesting how it automatically aggregates the field, not matter the naming: ![Screenshot 2025-09-25 at 15.58.33](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b3816a410fd3f78b4a5c0ab77129aa38ac240bc3.png) Long term, it would be nice to be able to split / group different fields as well. I will note that it isn’t grouped in Filtering and Sorting. This is expected and in line with other fields, but the merging of the Name is different to other fields so maybe it makes sense to merge in sort and filter as well? Not sure… This solves the pain point of needing to name things in the same way in order to group them in views, (+filters and sorts), but only for Name field, and not for others. I don’t have an idea for a solution though. Keep em coming! ---
**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\ **Post date:** [September 25, 2025, 5:33pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/6 "2025-09-25T17:33:54Z")
Release Thursdays are my favorite day of the week! 🥳🙌 The Name field improvement is so small yet so helpful for space customizations. Love it! ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [September 25, 2025, 8:20pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/7 "2025-09-25T20:20:41Z")
Years ago I would have jumped up and down for the ability to rename “Name” fields but the more I work with API & Scripts I’ve loved Fibery’s imposition that the primary field be called name consistently across a workspace. That said, for UI only teams, this is a huge win! ---
**Author:** ![Wilco\_Boode](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/wilco_boode/32/9985_2.png) [@Wilco\_Boode](https://community.fibery.io/u/Wilco_Boode)\ **Post date:** [September 26, 2025, 6:31am UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/8 "2025-09-26T06:31:39Z")
Thank you for recognizing weird limitations and removing them. Keep it going, already looking forward to next Thursday, its my favorite day of the week by now 🙂 ---
**Author:** ![Sev](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@Sev](https://community.fibery.io/u/Sev)\ **Post date:** [September 29, 2025, 11:35am UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/9 "2025-09-29T11:35:30Z")
> [@mdubakov](#): > > Finally, you can rename the **“Name”** field! It’s still not possible to delete it (and it never will be), but at least you can make it more semantically relevant. Hi. This is wonderful. **Thank you! ❤** Before, it took me a bit to decide on what to call the name of a contact (we landed on “raw name”). Now it will be “label” for the ex-name and “name” for the ex-“raw name”. We always (for ourselves and for clients) use a formula-generated label, since it blends key info with context and improves the ux of scanning search results and lists. ---
**Author:** ![AdVhPkgKad](https://avatars.discourse-cdn.com/v4/letter/a/7993a0/32.png) [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\ **Post date:** [September 29, 2025, 10:04pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/10 "2025-09-29T22:04:52Z")
Wololooo 🙏 ⛪ A question I had since you’ve been changing weird behaviour: are there any plans to allow multiple workflow field types per database? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 29, 2025, 10:27pm UTC](https://community.fibery.io/t/september-25-2025-disable-public-sharing-in-a-workspace-rename-name-field/9680/11 "2025-09-29T22:27:21Z")
No plans. Single select fields offer pretty much everything that the workflow field does, so no real reason to allow more. Is there something specific that you want from a workflow field that isn’t possible with a single-select?