# \[DONE\] "Non-admin" mode for admin **URL:** \ **Category:** Ideas & Features\ **Created:** [October 2, 2021, 11:22am UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086 "2021-10-02T11:22:02Z")\ **Posts on this page:** 19\ **Page:** 3
**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:** [December 24, 2025, 12:11pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/54 "2025-12-24T12:11:14Z")
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”. > [@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. ---
**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:** [December 24, 2025, 12:35pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/55 "2025-12-24T12:35:43Z")
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. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [December 24, 2025, 12:47pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/56 "2025-12-24T12:47:11Z")
> [@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. ---
**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:** [December 24, 2025, 1:56pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/57 "2025-12-24T13:56:59Z")
> [@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): 1. Fibery Architects (those who’s sole job is maintaining the Fibery workspace, not work in the workspace. Admin/Architect everywhere) 2. Internal Fibery Champions (those who have a different job, but also run and maintain the Fibery workspace. Admin/Architect everywhere) 3. 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) 4. 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… ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [December 24, 2025, 10:38pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/58 "2025-12-24T22:38:02Z")
I agree with @RonMakesSystems. > [@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 > [@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. - 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. ---
**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:** [December 24, 2025, 11:19pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/59 "2025-12-24T23:19:56Z")
> [@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? > [@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). ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [December 25, 2025, 12:37am UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/60 "2025-12-25T00:37:05Z")
> [@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. > [@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 🤩 ! ---
**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:** [December 25, 2025, 2:06am UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/61 "2025-12-25T02:06:31Z")
> [@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. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [December 25, 2025, 3:24am UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/62 "2025-12-25T03:24:11Z")
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. ---
**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:** [December 25, 2025, 2:04pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/63 "2025-12-25T14:04:20Z")
From reading other replies, I think there’s a difference between “Non-admin” for admins, and “Non-architect” for architects. What was built at the moment is “Non-architect”. “Non-admin” would mean that that the switcher would give the admin the access to space based on the access that was assigned to them, and not be architect everywhere just because they are admin. Then an admin could assign themseves access as they need for their work, then turn on non-admin mode. If their work means they need to an architect in a space, they will still be architect even when non-admin mode is on, since they have assigned themselves as architect. This would not only change UI, but also the entity permissions. Then the “show databases” behavior could be the same as now. The only difference is if an admin wants to configure a space they are not assigned to as an architect, they must change to Admin Mode, then Show Databases, then make the changes. This might get a bit confusing though… And I believe you said you wouldn’t go for it: > [@mdubakov](#): > > Now you have to turn on architect mode, and then turn on databases in space you need. We will not go for it. Note that this will only be needed for spaces where you didn’t assign yourself as an architect. Lots of moving parts! Curious to hear other people’s thoughts as well. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [December 26, 2025, 2:26am UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/64 "2025-12-26T02:26:11Z")
> [@RonMakesSystems](#): > > I think there’s a difference between “Non-admin” for admins, and “Non-architect” for architects From my standpoint, this is a helpful clarification. Initially, I was definitely anticipating the “non-admin” mode, and not the “non-architect” experiment we have now. I still need to play around some more with the new experimental behavior to develop my thoughts more. ---
**Author:** ![Jonathan1](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jonathan1/32/10038_2.png) [@Jonathan1](https://community.fibery.io/u/Jonathan1)\ **Post date:** [December 26, 2025, 11:53pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/65 "2025-12-26T23:53:44Z")
> [@Chr1sG](#): > > 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’s an option, I didn’t thinked about adding a Space as Favorite but I prefer to keep the main things on the Workspace section _(opened by default when I open Fibery)_ and specific things I need to focus, on Personal section. In the point of view of an architect, I think that the personal section is secondary and should not become the main one. I have only Views I want to keep an eye regularly and some personal documents or notes. If I want to change something on the Space of a View I have in Favorite _(and I don’t want to keep the whole Space as Favorite)_, I will need to go back to the Workspace section. I think that building my proper Workspace inside my Personal section can be a temporary solution but I’m not sure that’s the right direction in the long term. > [@Michael\_Ichter](#): > > 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. For me this is another feature. And I would like to have it one day on Fibery : be able to see the same as a selected User sees. On Salesforce for example, you can “login as…” and see what another User see. This is very useful for debugging. > [@RonMakesSystems](#): > > What was built at the moment is “Non-architect”. Agree with you. > [@RonMakesSystems](#): > > “Non-admin” would mean that that the switcher would give the admin the access to space based on the access that was assigned to them, and not be architect everywhere just because they are admin. > [@RonMakesSystems](#): > > This would not only change UI, but also the entity permissions. That’s it. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [January 5, 2026, 10:51am UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/66 "2026-01-05T10:51:21Z")
I’ve turned the experimental feature off now. I found that I was too frequently switching between architect and non-architect modes. The declutter from removing certain UI elements was overpowered by the clutter of showing all databases for me. I much prefer being able to control this behavior per Space. Also, not showing menus/pages in settings continued to be pretty disruptive for me. ---
**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:** [January 7, 2026, 8:46am UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/67 "2026-01-07T08:46:58Z")
@RonMakesSystems is right, it is essentially **non-architect** mode. It appeared a harder problem than we thought initially. So far we are thinking about these improvements - enable proper access to Settings pages even in User mode - add a shortcut to switch to this mode fast (like Shift - Shift) - tone-down the button and make it less “in your face” - ??? hiding spaces from Admins can be weird, since if we do it, all spaces will be hidden from admins till the admin adds herself to these spaces explicitly. So we maybe solve it in a different feature that is not related to architect mode > [@Jonathan1](#): > > On Salesforce for example, you can “login as…” and see what another User see. This is very useful for debugging. This is indeed another feature and I hope we will do it someday. ---
**Author:** ![rabrunos](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rabrunos/32/13629_2.png) [@rabrunos](https://community.fibery.io/u/rabrunos)\ **Post date:** [January 16, 2026, 12:50pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/68 "2026-01-16T12:50:07Z")
That makes sense, what exists today is “Non-architect”, and it already helps a lot with UX / reducing visual noise (not seeing databases/settings when you just want to _use_ the system). But the problem I (and others) am trying to solve is different: **being able to actually test and live the real permission rules**. Right now, even in “User mode”, I still have the admin override behind the scenes. So I can’t reliably validate things like: - “Can I really not edit this field?” - “Does this approval truly require the correct approver?” - “Does this workflow truly block users without permission?” - “Are automations/integrations respecting the rules?” **Real example:** I have an approvals database/workflow. A user submits an approval request, and only a specific group should be able to approve/reject. But as an admin, I can approve everything even when I shouldn’t, so I can’t test the rule with confidence unless I create a test account or ask someone else to test for me. So the suggestion would be a **“Non-admin” (or “Respect permissions mode”)** that is not only UI: - It **disables the admin override** and treats me based on the permissions I _explicitly_ have per Space/Database. - If I added myself as Architect in a specific Space, that’s fine, in that Space I would still be an Architect even with “Non-admin” enabled. - But if I don’t have access/role in a Space, I shouldn’t be able to bypass restrictions just because I’m an admin. I agree that “hiding spaces from admins” can be weird as a default behavior. But maybe it can be framed like this: - **Non-admin mode = enforce permissions** (including entity-level permissions, not only UI). - Navigation/space visibility could remain similar to today (or be optional), the key point is real enforcement. - And when I need to configure something outside my assigned permissions, I consciously switch back to **Admin mode**. This would solve a very practical problem: **admins being able to build and validate security + complex workflows without needing test users**. If that’s too big for now, an initial version that would already help a lot: - A “Respect permissions” toggle that affects **entity permissions** (create/edit/delete/approve), not only “show databases”. - A clear UI indicator while it’s active. Thanks for engaging with this, I think “Non-architect” and “Non-admin” solve different pains, and both are valuable. ---
**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:** [January 16, 2026, 1:19pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/69 "2026-01-16T13:19:13Z")
> [@rabrunos](#): > > **being able to actually test and live the real permission rules**. This is a different use case, which we know about, and intend to work on. Yesterday’s release is not intended to address that. ---
**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:** [January 22, 2026, 3:45pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/70 "2026-01-22T15:45:46Z")
Architect/Non-Architect case released > [@January 22, 2026 / 🎛️ Architect mode, many AI and validation rules improvements](https://community.fibery.io/t/january-22-2026-architect-mode-many-ai-and-validation-rules-improvements/10284): > > 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 … ---
**Author:** ![nathan\_jay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nathan_jay/32/11899_2.png) [@nathan\_jay](https://community.fibery.io/u/nathan_jay)\ **Post date:** [January 27, 2026, 10:58pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/71 "2026-01-27T22:58:30Z")
> [@Jonathan1](#): > > On Salesforce for example, you can “login as…” and see what another User see. This is very useful for debugging. Yes please do it and vote here: [View as another user for admins](https://community.fibery.io/t/view-as-another-user-for-admins/6111) Really important for Architects setting up new systems because it’s difficult with overlapping access for Space, DB, Entity and extending. Great to set it up, test the views, and then roll it out to users. Every time I “think” I have understood it then someone else tells me “I can’t access that” ---
**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:** [June 11, 2026, 6:04pm UTC](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086/72 "2026-06-11T18:04:11Z")
Closed on June 11, 2026, 6:04pm UTC [Previous page](https://community.fibery.io/t/done-non-admin-mode-for-admin/2086.md?page=2)