In short: The ability to switch to a mode in which all settings (links) available to administrators are not visible. Why: In day-to-day work in a “flow” state, all these unnecessary links (apps, buttons, menu items) are very distracting. Excessive cognitive load. Solution options: The solution is generally universal and most likely has already been discussed on the forum. A set of pre-configured interface types, with the ability to switch between them. As an example, how this is implemented in Planfix: Planfix allows you to customize your interfaces for different users of the system. An interface customized for a specific group or a specific user is called a Workspace. Workspaces make it possible to significantly simplify the use of Planfix, since the user will only see the amount of system functionality that he needs in his work. Several workspaces may be available to the Planfix user. Switching between them allows you to quickly move from one operating environment to another. This is especially true for managers and those employees who are involved in the work of different departments of the company. [image]

Architect/Non-Architect case released [image] January 22, 2026 / 🎛️ Architect mode, many AI and validation rules improvements Changelog control_knobs Architect vs. User modes Today we’re introducing a new way to keep Fibery calm and safe for everyday work: Architect vs. User modes. Admins and Architects can now switch between two modes: User mode: a cleaner, focused interface for daily work. Advanced controls are hidden: no accidental field edits, no surprise layout changes, fewer dangerous actions like Delete Relation Field in your face. Architect mode: the full power view for workspace design. Architect mode can be …

I think it’s nice for the most part. The main thing that feels off for me is that the UI tends to feel too cluttered when admin mode is active, because all the databases are now showing. It’s pretty rare that I’m needing to look at the databases of more than one space at a time, though I do tend to have more than one space expanded. Not that huge of a deal as the “collapse all” button quickly makes the sidebar more manageable, but it is a bit disruptive for the time being. I’m wondering if it makes sense for architect mode to not automatically make databases appear (or maybe only automatically make the User database appear). Another thought I had is for User mode to hide the spaces/entities/whatever that I have access to ONLY because I’m an admin. I’m usually using the user mode when I want to get a good feel of the UX for our staff, or when I’m orienting a new person into our workspace, or when I want to see what things are viewable to everyone in the workspace (which currently I need to ask someone to let me use their account to test this last scenario).

I like it a lot! Only bug I found so far is the settings page. It shows the workspace settings, but when pressing any page it says “Page not found”. [image] Michael_Ichter: The main thing that feels off for me is that the UI tends to feel too cluttered when admin mode is active I agree here as well. I would like to being able to turn it on one space at a time, with an option to toggle all on or off. One of the big issues I will have is the lack of “New View” button without architect mode on. And with architect mode it shows the databases which will clutter. I have a “Playground” space which has no databases, and has most the views of the workspace. I do this in order to allow the users to create views as they need, without being architects of the data. It works quite nicely. With this feature, it will add more confusion to the end users instead of simplify. If they want to make a view, they need to first toggle Architect mode, then turn it off. If they leave it on, it shows the space settings and (the lack of) databases with the option to create a new database. Maybe this architect vs user switcher is something that can be turned on or off per user? Maybe default for admins but not for users? And if a user has Architect access to more than 50% of the spaces, it shows a message “Do you want the architect switcher”? Or something.

If we keep database switcher per space it will be even more complicated. Now you have to turn on architect mode, and then turn on databases in space you need. We will not go for it. Alternative is to remove this architecture mode completely and keep old behavior.

[image] RonMakesSystems: It shows the workspace settings, but when pressing any page it says “Page not found”. Oh ya, I forgot about this! This is definitely not good design: if user mode is on, some of the settings menus are listed but then clicking on that menu item just brings up the “Page not found” message. User mode should hide any settings menus that aren’t accessible. But honestly, the architect mode as is doesn’t add any value for me (and even adds some clutter). So I’ll let others speak to this more.

[image] mdubakov: Now you have to turn on architect mode, and then turn on databases in space you need. This isn’t what I mean. Imagine the “Show Databases” button becomes a “Architect Mode” button. All entities and views in spaces that have architect mode on become shown with architect controls. Then there’s a global on and off that simply turns all spaces “Architect Mode” on or off. So it’s still a single toggle like now if you want to turn all on or off, but also the ability to turn Architect mode on or off per space. The global control will only shown to admins who can Architect everywhere. But this still wouldn’t solve the problem I have with the “Playground” space… There are the following actors (in my mind): Fibery Architects (those who’s sole job is maintaining the Fibery workspace, not work in the workspace. Admin/Architect everywhere) Internal Fibery Champions (those who have a different job, but also run and maintain the Fibery workspace. Admin/Architect everywhere) Admins for billing/power purposes (those who have no idea how Fibery works, but need to be able to invite users, manage billing, etc. Admin, but not architect) General users who need to create views of data. (just have architect for the sake of making views and not for database or management.) This switcher is most useful for nr 2 and nr 3 I think. Nr 1 and 4 would perfer things as they currently are. 1: Needs to always see the architect controls, and current implementation allows for a cleaner sidebar most of the time 2: Needs to work in the workspace more often, so turning off architecture stuff is helpful 3: Probably shouldnt be touching architecture stuff in the first place. 4: Turning on architect mode just to create/edit views, then turning it off for a cleaner sidebar every time isn’t a nice experience. (explained more in previous post) Not sure about the best solution. Maybe keep the “New View” even when Architect mode is off? Or even better, allow control for non-Architects to create views. But I think that’s more complex…

I agree with @RonMakesSystems. [image] RonMakesSystems: Nr 1 and 4 would perfer things as they currently are. 1: Needs to always see the architect controls, and current implementation allows for a cleaner sidebar most of the time [image] RonMakesSystems: 4: Turning on architect mode just to create/edit views, then turning it off for a cleaner sidebar every time isn’t a nice experience. (explained more in previous post) I think this switch radically changes the way an architect works in their workspace, and not in a good way. I find the current behaviour to be better and more flexible. My vision of an “non-admin” mode for admin is the following : removing the power to see everything, keeping the power to do everything. It means that if I’m on User mode : I shouldn’t be able to see Spaces where I’m not a member. I shouldn’t be able so see entities that aren’t shared with me. These points joins what @a2say said on his first post : [image] a2say: Why: In day-to-day work in a “flow” state, all these unnecessary links (apps, buttons, menu items) are very distracting. Excessive cognitive load. I should be able to do everything I can do as an Architect : create Views, Rules, Buttons, etc… Without needing to switch to another mode. I think that this would be a good start.

[image] Jonathan1: My vision of an “non-admin” mode for admin is the following : removing the power to see everything, keeping the power to do everything. Have you tried making use of the Personal section of the sidebar and adding things (spaces, views, etc.) as Favorites? [image] Jonathan1: I shouldn’t be able so see entities that aren’t shared with me We will soon make it possible for Admins to be Architects in a space without necessarily having access to all the entities in the space (unless explicitly shared with them).

[image] Chr1sG: Have you tried making use of the Personal section of the sidebar and adding things (spaces, views, etc.) as Favorites? Yes, I have a few views saved as favorites. I’m not sure I understand your point. [image] Chr1sG: We will soon make it possible for Admins to be Architects in a space without necessarily having access to all the entities in the space (unless explicitly shared with them). Good news :star_struck: !

[image] Jonathan1: I’m not sure I understand your point I just meant that if you don’t want to see everything, but still want to be able to do anything, then only showing certain spaces in Favorites (and thereby implicitly hiding the rest) gets you part way there. It doesn’t prevent you from seeing entities you don’t care about, but it keeps you from being distracted by spaces/views you don’t care about.

If I’m not mistaken, I think Jonathan’s point is that non-admin mode is to “see what the user sees”, for the purposes of testing non-admin UX, and not for the regular workflow of the admin him/herself. Using Favorites doesn’t really satisfy this purpose in my mind.

[DONE] "Non-admin" mode for admin

Ideas & Features

mdubakov January 22, 2026, 3:45pm 70

Architect/Non-Architect case released

Topic		Replies	Views
View as another user for admins Ideas & Features permissions	30	761	July 30, 2026
Fibery Product Report: November 2024 News & Announcements	45	1006	December 5, 2024
Private database - my space Ideas & Features	34	1230	October 8, 2026
Feature Request: Share Space but restrict entity views Ideas & Features permissions	53	935	March 29, 2025
October 8, 2026 / 🫣 Hide Space data from Admins Changelog	22	486	October 17, 2026

[DONE] "Non-admin" mode for admin

Related topics