November 6, 2025 / Contributor Space access is being deprecated, Edit entities you create, Hide empty "No parent" groups

News & Announcements Changelog
1

Contributor Space access is being deprecated

Now that we have a new beautiful (and consistent!) set of Space access levels, we will gradually deprecate the legacy Contributor access:

image
image2134×1512 159 KB

Quick reminder: Contributors can see and comment on all entities in the Space as well as create new ones. Additionally, Contributors can edit entities they have created or are assigned to.

Contributor access is an echo of dark times when you couldn’t share a Database or automatically share Entities with assigned people. Now that you can do both, there are no good reasons for Contributor to exist.

All Users and Groups that currently have Contributor access will keep it ~forever, but on May 1, 2026 Contributors will lose the ability to edit entities they create or are assigned to. Also, you won’t be able to grant new Contributor access.

Check out our migration guide for advice on what to replace Contributor with. If you’re having any trouble migrating, please don’t hesitate to reach out.

Edit entities you create

We regularly get questions like “why has the card I’ve just created disappeared?” or “why do I have to refresh the page to be able to edit the task I’ve just created?”.

This usually happens when someone receives Submitter access to a Database that doesn’t have the automatic access via Created By enabled:

image
image2244×1858 206 KB

In 100% of the cases, the solution was to simply enable the automatic access.

To prevent such issues in the first place, we’ve made two tweaks:

  1. All new Databases will have automatic Editor access via Created By enabled by default.
  2. If someone has the permission to create but not edit Entities in some Database and the automatic access is off, we’ll show a hint suggesting enabling it.

If you don’t necessarily want people to edit Entities they create, you can disable the automatic access or revoke it on schedule.

Hide empty “No parent” groups in Smart Folders, Tables, Lists and Gantt views.

You can now hide empty “No parent” groups (like “No Phase”, “No Project”, “No Status”, etc.) when they contain zero items. Simply enable the “Hide Empty ‘No…’ Groups” toggle in the Filter tab in view settings to keep your views clean and focused on actual content. Empty sections will automatically reappear when you add items to them.

:butterfly: Improvements

  • Files field:
    • Delete all files in any file field. Click … above files and select Delete all files action
    • Download all files from selected entities on any view in a batch. Just select as many entities as you want, click Download all files action, and you will get an email with the link to the archive. It can be handy if you want to download all invoices for latest month, for example.
  • Intercom integration: sync assigned users as native People Fields.
  • HubSpot integration: sync Owners and other User properties as native People Fields.

:shrimp: Fixed Bugs

  • Whiteboard:
    • Fixed 500 error in browser console when open a whiteboard with not found image
    • Fixed the case when text is displayed above the control elements during editing
    • Fixed a case when a new section is being created instead of a connection between two sections
  • Shared entity:
    • Fixed a situation when it was impossible to open parent entity on shared page
    • Fixed sharing links reordering if turn on/off extended access for some of them
  • File Field:
    • File fields should be hidden if user has no permissions to add files and field is empty
    • Disabled ‘Run’ button if files uploading is still in progress for automatic actions via buttons
  • Gantt View: Fixed crashes when ‘Hide is empty’ selected for the Milestone db
  • Notifications: Fixed a case when more/less is always visible when message contains emoji
  • Google Calendar Integration: Fixed a bug when Google Calendar sync generating incorrect end date for all-day events

P.S. Check our fresh customers page. What do you think?

10 Likes
3

Oh, it’s Thursday? :slight_smile:

Happy to see you guys fixing and improving all the time as well as rolling out new things. Hope docs will update accordingly.

“No parent”-like stuff is great.

I’ve almost finished the agency template with contractor and client spaces, sort of portals. I tried to make sure everything works not requiring a Pro subscription. But permission system although looking clear in the docs, in practice feels a bit complex. I think when I do 10k hours with it, I will feel easier.

1 Like
4

Noble attempt, but it will not always be the case :slight_smile:

1 Like
5

Thank you!!

6

I LOVE the new customers page, btw – And it’s NOT ONLY because I’m personally quoted at least twice on it :laughing::grin:

I love all the wins and dopamine shared there, along with the direct user requests that have (or in some cases, have not yet) been implemented. Awesome idea, and continues your company’s laudable commitment to transparency (and being responsive to user requests)

7 Likes
7

Thank you for the effort you put into the Whiteboard. Most of my team uses Miro, and I am happy that the most common use-cases are now fully functional straight inside of Fibery!

3 Likes
8

Lovely update! I made a “reaction video” if you will, to this week’s update, I hope to keep these up every week when I can. Here’s the link if you’re interested: https://youtu.be/mXQ3z1ZfUI0

Main points:

  1. Allow access to entites to be hot-reloaded when automations change or formulas get loaded. “Created by” access is the best UX for end-users, but give least control to architects. Or have formulas calculated on creation and not after creation. It’s a real need also because access can not be extended using the Created By field. Having both solutions proposed above together would be great (then formulas and automations both work, with automations needing to wait a second for it to run and update on the frontend, and formulas would be instant)
  2. “Hide Empty ‘No…’ Groups" is quite confusing. I’m not even sure I fully understood it yet…? Why not just have it within the “Hide empty groups” toggle, and have that toggle work on all parent hierarchies. This is one thing where I think the more flexibility does not outweigh the higher complexity. But maybe I just never encountered the place it was needed.
  3. Did this update remove the fact that required parents automatically has the “No …” hidden? Or was this never a thing and I’m hallucinating?
  4. Download all files should be on right click as well (both on bulk and on single entity). At the moment bulk download does not work in relation views.

Good stuff!!

4 Likes
9

Fantastic! Love it! Thank you!

1 Like
10

Thats a very nice reaction video ! keep them coming Maestro!
Tips:

  • can you post-edit the screen recording to zoom into details you show, that would make it easier for the eyes.
  • You may also want to create a 10 seconds default intro section to introduced fibery to new watchers or refer to a series.
2 Likes
11

Imagine the following Projects and Tasks:

  • Project 1
    – Task A
    – Task B

  • Project 2
    – Task C
    – Task D
    – Task E

  • Project 3
    …none

  • ‘No Project’ (tasks not currently assigned to any Project)
    …none

Maybe you don’t want the clutter of showing the ‘No Project’ since it is very rare that people will drag a Task from belonging to a Project to not belonging to any Project.
In this case you choose Hide Empty 'No ...' Groups.

If you were to choose Hide Empty Groups then Project 3 will also disappear, which will prevent people from moving a Task from Project 1 to Project 3 using drag and drop.

3 Likes
12

Hi Ron!

Thank you for sharing your confusion: it’s invaluable and really helps to figure out something better :slight_smile:

The goal of the feature was to tackle specific issues reported by users, mostly around Smart Folders, and we kind of carried those patterns over to other views rather by inertia.

Smart Folders have a different structure: there’s no grouping, and “no …” containers aren’t nested inside each other. So in that context, the toggle actually makes much more sense in my opinion.

I agree that on the List/Table/Gantt view it does look like a sub-option of “hide empty groups,” but technically it’s not.

The thing is, for a regular parent–child hierarchy, you can just use a standard filter to hide empty parents. But that doesn’t work for “grouping items at inner levels” or “no …” items — so we need both toggles to handle all cases.

I agree it looks a bit clunky for now, and some generalization would help, but we’re not at that convergence point yet.

The toggle label is also my personal pain point: that was just the best name I could come up with. Totally open to suggestions on how we can call THIS THING.

Regarding the confusion with required fields, I think it currently only applies to select/multi-select fields, and we just missed this edge case when implementing the “required fields” feature.

4 Likes
13

I see. Yeah, this makes sense. Thanks for explaining it! There’s value in being able to turn that off (less clutter). (would be nice in board view too actually now that I understand it).

But I think the current implementation of it makes things really confusing for a couple reasons, then I also have a suggestion to make things more intuitive.

  1. When you “Hide empty groups” that includes “Hide empty “No…” Groups” in cases of single “Group by” hierarchy. So having one on and the other off doesn’t make sense. (But in complex hierarchy this isn’t true)
  2. Using the same terminology “Group” for “Group by” functions and “Levels” functions, when like you said, they work quite differently.

My suggestion would be to just have empty “No…” levels hidden by default without the option to turn it on. If it is really needed as an option to drag into, those levels can appear when the user initiates drag and drop. Although I think in 90% of cases, you drag items from “No…” into a group as opposed to vice versa. And if users need a “No Parent” to always show, they can make that into an parent entity, or “Other”.

I will just add one more thing here I disagree with:

Allowing “Hide empty parents” on normal levels would be quite nice as well. (configurable per level). Filtering works, but it doesn’t take search/personal filters into account. I really like how the “Hide empty groups” makes empty groups disappear as the user searches in the view.

I think I got confused because it does actually work like this on board view, and I think it’s my most used view type.

Curious to get your thoughts!

Thoughts I had about naming if it stays using the current mechanism that ended up going no where useful… It’s really tricky:

Regarding name (if you choose to keep it as is), maybe invert it? “Show all empty levels”? Naming is a tricky thing indeed haha. Because now if this is on, you should not be able to turn on “Hide empty groups” as those two contradict each other.

This is really confusing…

We want the ability to:

  1. Show all empty things (Groups and “No…” Levels)
  2. Show empty levels, but hide “No…” Levels.
  3. Hide empty levels, but show “No…” levels.
  4. Hide all empty things.

Maybe “Hide empty “No…” levels”? It’s really tricky to get right ://

14

:clap:
Wow! Bravísimo! That is easily among the top-20 web pages I have ever visited:

  • innovative by communicating through feedback dialogs
  • fun: dopamine = positive, cortisol = potentially negative
  • visually themed: blue = positive, yellow = potentially negative but some with the positive :check_mark:
  • informative without being boring

And the ‘Hide empty “No parent” groups’ is a really great quality-of-life improvement for users of the system. Thank you.