October 8, 2026 / 🫣 Hide Space data from Admins

[mdubakov]

Hide Space data from Admins

The day has come. You can hide salaries, one-to-one meeting notes, and executive tasks from Admins. They will still be able to see and manage all Spaces, just not the data inside.

The mechanism should be familiar to the nerdiest of you. Whenever you share a Space, you can click on the little x to exclude data. Click on the same cross now to hide data from Admins:

Admins will still see the Space in the sidebar and will be able to configure its Databases, Fields, and Views. The Views, however, will look empty to them — unless you explicitly share certain Databases or Entities.

You can click that cross as long as there’s at least one person (not necessarily an Admin) with full access to the Space. Otherwise, you can end up with data accessible to no one but NSA. For example, give your CFO full Architect access to the Finance Space before hiding data from Admins.

You might ask: “Seriously?! Showing that pathetic little cross took you all that time?”. Well, unlike for Jesus, the cross wasn’t the main challenge for us. We had to ensure there’s no way an Admin can bypass the permissions via API, export, scripted Rules, or by simply moving a secret Database to the Space where they have full access.

Now we are pretty sure all checks are in place, so we are making the functionality widely available, skipping the Experimental Lab. You’ll still need a Pro or Enterprise plan, though.

Check out the new user guide section for caveats and let us know if your Admin problem is solved now.

BPMN shapes on Whiteboards

You can now create BPMN diagrams with a dedicated set of shapes. Open the Shapes panel, choose events, tasks, or gateways, and connect them with arrows to build your process.

Flip objects on Whiteboards ↔

You can now mirror objects on a Whiteboard in one click, so there’s no need to redraw a shape or arrow just to point it the other way. Select any shape, icon, image, or drawing and choose Flip horizontal or Flip vertical from the the context menu or use the shortcuts Shift+H and Shift+V.

Mo dogs

More new illustrations, fewer old emojis. You can now enjoy fresh artwork in empty states like “No publicly shared items” and “No active webhooks” in Settings, as well as “Nothing found” in various search panels, “Shared with me” panel” and Watchlist panels.

Stricter validation for Automations

Automations are now validated more strictly when you create, update or enable them. If an Automation Rule or Button references a deleted Field, uses a formula the editor rejects, or has an action that is no longer available, saving it fails. This also helps Fibery AI create correct Automations.

A small number of existing Automations already have such problems. They keep running exactly as before, and you can still turn them off, duplicate them or restore them from history. However, you will not be able to edit or re-enable them until you fix the errors.

Improvements

• Fields: Now you can see all Views and Access Templates where a field is used when you try to delete a field (or just click Field Usage action)
• Desktop: Upgrade Electron to 43.4.1 to enable background-tab warming on Windows
• Usage: Usage status bar in the help menu popover updated to include more info

Fixed Bugs

• Mobile: Error on downloading video from whiteboard
• Custom Apps: Entity links opens in the same tab for app in standalone mode
• Reactions: set emojis are cut on NON retina displays
• History & Audit Log: History shows create and set default checkbox values as separate history items but it should be just created
• Rich Text:
  • Inline comment popup shows a comment from another line when a resolved comment spans both
  • Basic Text Table Block: Horizontal scroll left in table after fitting to width for Wide page width
  • Basic Text Table Block: Lack of auto scroll on dragging to the columns out of visible area
  • Basic Text Table Block: Column with min width fails to be selected
  • Basic Text Table Block: Selection is displayed out of field area
  • Basic Text Table Block: Width of column/row placeholder and really added column/row are different
  • Suggest changes button is shown in actions even if there is no rich-text field at all
  • Suggestions get reordered in sidebar when you try to add a comment to the first one if they belong to the different rich-text fields
  • Suggestion mode indicator is missed in embedded doc header
  • Suggestion details show empty text for added entity or user mention
  • Suggestions get duplicated when duplicate Entity
  • Comment from the rejected suggestion appears in Unlinked tab only after page refresh
  • Suggestions tab gets empty on switching between locked/unlocked mode
• Integration: Sync failed icon looks like a close/delete action

P.S. How is your October, folks?

[papertroll]

@mdubakov

Well, unlike for Jesus, the cross wasn’t the main challenge for us

But, like Jesus, Fibery is the way and the truth and the life.

Well done on finally delivering this feature! Sounds like it will be a massive relief for you all to finally have it out of development, and will unlock a lot more uses for teams. This is definitely the case for my team, at least!

[ID.000]

Thank you so much! This is a very important and essential tool for large companies!
[Hide space data from Admin]

[christamae]

@mdubakov

Hide Space data from Admins

Immediately starts POC for Performance Management space

[myg_ge]

Popcorn night!

1. Love dogs
2. BPMN – did you guys ever consider marrying whiteboards with automation rules (perhaps with the help of AI), so that BPMN, for example, could be not just drawing but actually a living automation rule tree?
3. Hide Space data from Admins

Thank you!

PS: It’s such a joy developing Fibery apps with MCP, remembering the effort, time, and money it was taking in the older days to build something comparable…

[Michael_Ichter]

@mdubakov

Hide Space data from Admins

Thank you!!! We can finally bring in some workflow and info that we’ve been keeping separate from everything else. I heart Fibery.

[timothy]

Celebration time!
The hide data from admins is HUGE for us!

& BPMN shapes on whiteboard is a big plus! as well as all the other improvements. Keep it up!!

[RonMakesSystems]

Love it!! I know a few workspaces where this opens up a lot of possibilities.

Petition to name “Almighty Architect” everywhere in Fibery?

And love the dogs :))

@mdubakov

Automations are now validated more strictly when you create, update or enable them. If an Automation Rule or Button references a deleted Field, uses a formula the editor rejects, or has an action that is no longer available, saving it fails. This also helps Fibery AI create correct Automations.

Sometimes i find it a bit annoying I can not save things as I am working on things, so i feel this is a bit of the opposite of a feature in my mind (if understand it correctly).

If there is a broken automation, I want to be able to fix it but it might involve a few back forth trips to check the fields, relations, etc.

How about validation on enabling the automation, and when saving an enabled automation, but not on saving a disabled automation?

[mdubakov]

Not sure what you mean here for automations. AI is very creative and without strict validations it can abuse formats and save rules that are just not correct, now we prevented that

[RonMakesSystems]

What I understand is that this feature restricts saving automations if they are with any errors.

When building in Fibery, sometimes there may be an error in automation, the automation is disabled, and i need to edit a different field in that automation because I am doing a migration of that specific field, not worrying about firing the automation quite yet. (I did this just last week)

If I understand correctly, I can now not save an automation unless I fix ALL the broken fields in one. My point is that preventing users from saving their work I think is not a good idea. Which is why I suggest to allow the automation to be saved as disabled, and validate when enabling.

If I misunderstood this change, let me know.

[mdubakov]

You can update and save disabled rules even if they are not correct

[RonMakesSystems]

I just tested it to check if I understood correct and it seems indeed I can not save rules if they have an error, even if they are disabled.

[Sergey_Truhtanov]

We will fix that, so you will be able to edit disabled Automations.

Hopefully tomorrow.

[Artur]

Thanks for shipping this! Our use case: we have an architect who builds automations across the whole workspace, so he needs Admin, but there are a couple of departments we’d like to keep private from him. Tried it on a test Space and two things got in the way:

1. Scripted automations stop working. Scripts run with Admin permissions, so once data is hidden from Admins, scripts can’t read it either. Hiding the data means losing the automations in that Space.
2. Admins still see the Space itself: Views, Docs, Wiki pages. For a private department that’s still more than we’d like to show.

Two things that would solve it for us: an option to hide a whole Space from specific Admins rather than from all of them at once, or letting Architects run scripts in their Spaces, so they wouldn’t need Admin in the first place. That said, I may well be missing a better way to set this up, so I’d really appreciate any advice. Thanks again!

[antoniokov]

As for the scripts that cannot read data from hidden Spaces, this is a known current limitation — a sacrifice that we’ve made to release sooner. If there’s enough demand, we’ll allow to run scripts under service users — and it’ll be up to you what access to grant to them, incl. access to Space data hidden from Admins. This would also allow non-Admins to write scripts.

The second part is more tricky, and we’d be curious about what use cases pop up. For the wiki specifically, we recommend using Databases instead of Documents as Views — those will be locked from Admins. Why you’d like to hide Whiteboards is clear, I think. Why would you like to hide Views? Could you please give a couple of examples where Admins seeing Views despite them being empty is still a no-no?

[Artur]

Thanks! Service users would actually solve most of it for us: our architect only needs Admin to write scripts, so with service users we’d simply not make him Admin, and normal sharing would hide the private Spaces completely.

On Views: with Custom Apps, a lot of Spaces are now apps in their own right. Even empty, an app (plus view names, fields and rules) shows how a department works, and for things like Finance or an internal R&D tool, the tool itself is the sensitive part. So for us the cleanest model is simply: a Space either exists for someone or it doesn’t.

[Chr1sG]

@Artur

for things like Finance or an internal R&D tool, the tool itself is the sensitive part

Can you elaborate on this? I am sure that many companies have tools for payroll/HR etc. but I’m struggling to imagine how an employee knowing that a tool exists, and how it works, is revealing anything sensitive.

[Jonathan1]

@mdubakov

Hide Space data from Admins

Thanks for that, will do a try.

[Artur]

Two things. First, wiki docs: a Document view is the content itself (payment setup, tax and banking notes, salary policy), not “how the tool works”, and Admins can still read it.

Second, payroll is generic, but some tools carry the sensitive part inside them. Say performance review is built as a Custom App. The rating scale, the bonus multiplier for each rating and the promotion criteria live in the app itself, not in rows. Calibration also has a “Planned exit” option, and there’s a view for the Q1 restructuring. So an Admin who opens the empty Space still learns how bonuses are calculated and that cuts are coming, before anyone has announced them. They might even be on that list themselves.

The Admin who needs scripts is often a technical hire or a consultant, trusted to build but not to see every department. So for some Spaces it has to be “you have it or you don’t”.