May 21, 2026 / 🫣 Manage users visibility, Send web request action in automations

[mdubakov]

Manage users visibility

By default, every user in your workspace can see every other user (only Guests can’t see each other).

This is great…until you start collaborating closely with your clients and contractors and invite them as Members or Observers. Your customer base gets exposed, sensitive email addresses get leaked, and your GDPR compliance goes out of the window.

Not anymore. Now you can prevent people outside of your org from seeing other users’ profiles:

Change the default visibility to Everyone with a trusted domain in Users → Access so your employees can freely browse each other as well as external people, while outsiders will not see other outsiders — regardless of their user role.

If you haven’t configured your trusted domains yet, do so in Settings → Security.

More freedom to configure users visibility is coming next:

• Allow users with the same email domain to see each other.
• Allow users that belong to the same User Group (e.g., Team or Role) to see each other.
• Allow users working on the same entity (e.g., Project or Initiative) to see each other.

Send web request (post to webhook) action in automations

We’ve added Send Web Request action to automations, so now all Architects can call external API or webhook easily. Here are some use cases for your inspiration:

• Notify a chat / on-call channel. Slack/Discord/Teams incoming-webhook URLs when an entity changes state, an SLA is at risk, a Highlight is created, etc.
• Trigger some automation. Send request to Make, n8n, Zapier or other services to initiate some workflow.
• Call any APIs (one-way). Push event to a CRM, billing system, or a homegrown service.
• Kick off external pipelines. CI/CD, data refresh, document generation, whatever.
• Feed agents (one-way). Push entity events to external AI Agents that consume them asynchronously and do something useful (hopefully)

Authorization tokens are secured and encrypted, and even you can’t see them after save (only replace). Use Import from cURL button to fill some fields faster.

You can set formulas for URL field and use markdown templates for Body field.

Deprecations

Last autumn, we sunset two pieces of legacy access controls. Today we deprecate them to simplify Fibery:

• Entities shared to web now always use access templates instead of mimicking the permissions of the sharer. We’ve migrated the remaining legacy links using the most conservative Viewer access so that nobody sees what they shouldn’t. The URLs stay the same.
• People with the legacy Contributor access to Spaces won’t be able to edit entities they create or are assigned to. If that’s what you need, consider enabling automatic access via People Fields instead.

Improvements

• Colors: Fibery reports default palette is tailored to the current theme.
• Whiteboard: Twemoji set is added to Whiteboard, available in Shape panel.

Fixed Bugs

• Table View:
  • Copy/paste in table view of relation that have comma in the name creates new entity unexpectedly
  • Error in console when user creates entity in table cell via required form and enters something into rich-text field
• Relation Views: Quick Search does not find all entities if Show All was not clicked
• Permissions: Guest can’t select Users database when create a view in Private
• Copy Action: No need to show the Deep copy option if a Database has no collections
• User Management:
  • Hide drag and drop and ‘add new’ for domain user groups on Views
  • Technical field ‘User group’ is available in views setup
• Documents / Rich Text:
  • When Documents are disabled in Fibery Workspace, remove Duplication for documents as well
  • Markdown parser doesn’t work correct for list in some cases
• MCP Server: Create view tool does not include all filter options for relations

[helloitse]

@mdubakov

can call external API or webhook easily

I noticed the Body section is a code block. I think the header setup is nice but wonder why going this route was preferred when the feature requests largely centered a UI for building the body? I can see having text/code as an option. But it appears to be the only option.

[RonMakesSystems]

@mdubakov

Manage users visibility

This is pretty fantastic!!! Finally!

The only thing I’m confused about is the terminology and the behavior. Especially because testing this required one to create a different account and logging in.

The default (the way it’s worked until now) is “Everyone but guests”? Or is the default functionality changing?

Can guests see all users? Can guests see other guests in the “Everyone including guests”? Admins are always seen by everyone? We can’t turn that off so that admin’s emails are not seen? Everyone with a trusted domain can be seen by guests as well?

I’d see it as:

“Can be seen by:”
“Can see:”

I feel like it’s a bit confusing to understand this dropdown personally… And testing it is not a simple task.

[RonMakesSystems]

Follow-up question:
Are you planning to allow access to extend to the users database based on a relation? I realized recently that it doesn’t work. For custom access templates, as well as a normal “Extended” sharing for to-many people relation.

This way you can:
Automatically share Team with Members with extended access into the members. This solves the problem of giving access to the members, no?

My use case was sharing publicly. I wanted to share an entity and show the user who created that entity, but I wasn’t able to…

[Chr1sG]

@RonMakesSystems

The only thing I’m confused about is the terminology and the behavior.

Access to Users

[ccollins]

@mdubakov

Copy/paste in table view of relation that have comma in the name creates new entity unexpectedly

While copy/paste relationship bugs are being addressed. Can this one be looked at - Copy-Pasting Non-Unique Relationships ? It is a huge data hygiene issue where you copy/paste a relationship and a completely different relationship is pasted than the one you copied.

[RonMakesSystems]

Perfect, much clearer thanks!! Might be good to have this shown in the product, based on what the user picks.

[antoniokov]

@RonMakesSystems

The default (the way it’s worked until now) is “Everyone but guests”? Or is the default functionality changing?

We haven’t touched the default, we are not that reckless .

@RonMakesSystems

Can guests see all users? Can guests see other guests in the “Everyone including guests”? Admins are always seen by everyone? We can’t turn that off so that admin’s emails are not seen? Everyone with a trusted domain can be seen by guests as well?

Yeah, the dropdown might be tricky to understand — that’s why there’s a detailed user guide with boring tables. Still thinking of how to find the balance between clarity and simplicity in the product itself.

@RonMakesSystems

Automatically share Team with Members with extended access into the members.

That’s exactly what’s coming .

@RonMakesSystems

My use case was sharing publicly. I wanted to share an entity and show the user who created that entity, but I wasn’t able to…

That’s a great use case! Should become possible as soon as Users are supported in access templates (WIP).