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.