Sounds like maybe you are after a way to temporarily turn off admin capabilities, no?
It looks like yes. The option create different “Roles” and posibility to easy switch between avaliable Roles with different permisions will be more customizable and efficient.
Related topic: View as another user for admins
I’ve already voted for this before, but I’d still really, really like to see this implemented.
Our use case is that I have the need to add some users as an admin (e.g. our CEO) so that they “have control”, but don’t want to add all the additional UI complexity to their day-to-day views, and avoid the potential for accidental configuration changes which that brings.
Why do they need control if they cannot be trusted to make configuration changes?
Is it a psychological thing?
Haha perhaps it’s time to make a “VIP” class that feels like they are the most important person there but they have less rights than an admin (without knowing 
)
Now over 6 months of building stuff in Fibery, this issue is happening a lot more often.
I have only just starting using more complicated cases with Custom Access Templates. The flexibility of these combined with auto linking is really incredible, wow!
But with that great flexibility is even more need for the Architect to actually see the outcome.
So far when I’ve got it wrong there hasn’t been too much “damage” by accidentally over sharing. But as user numbers grow and I bring in more sensitive information into Fibery, I’m worried I’ll over share something. One wrong toggle to “extend” and suddenly the whole company can see private information and I have no idea because I can’t “see what they see”.
Yes, this is drafted by Claude - I wrote some horrible rambling monstrosity, and Claude said “no man, don’t post that.” I agreed:
I know the architect toggle exists, and I appreciate the intent. But it doesn’t fully solve the problem it’s trying to solve.
When I toggle off architect mode, I still see all the same spaces. I can’t tell what an editor-level user actually sees — which spaces are visible to them, which views appear in their sidebar, which fields are hidden. The only way I can check is to screenshare with a staff member and have them walk me through their experience. Then I go back to my screen and click around hoping my changes land correctly.
This is a significant barrier to building a usable workspace. The people most motivated and most able to configure Fibery (architects) are the ones with the least visibility into how their configuration affects other users. It’s like designing a house but never being able to walk through the front door — you can only look at the blueprints.
The ask: Let architects impersonate a specific user or at least a specific permission level. When active, the architect sees exactly what that user or role sees: same sidebar, same spaces, same hidden/visible fields, same view access. No guessing.
Even a simpler version would help: a “preview as Editor” mode that hides everything an editor can’t access, so I can audit the experience without needing someone else’s screen.
This would dramatically reduce the trial-and-error cycle that currently makes Fibery hard to roll out to less technical team members.
I think there’s a lot of complexity in trying to define this. Based off of your use of “Editor”, I’m guessing you are referring to a space-level permission, but you are also referring to “same sidebar, same spaces”, which sounds more like a workspace user role to me.
For example, I would expect a non-admin mode to treat the admin as if it were a user “Member”, being a workspace-level feature. So all the spaces, entities, etc. that are viewable only because of being an admin would disappear while this toggle is switched on.
But let me know if I’m misunderstanding you. I think some sort of permission-level view, whether workspace-wide or narrower, would be very helpful.