sounds awesome!
Sorry, I’m late to the party, but I also want this.
Kinda in line with my FRQ for Admins’ abilities to view Fibery as a different role, I would love as an Admin to be default in a non-config mode and only enable “Edit Mode” when necessary.
For example:
- Single-selects automatically add options for Admins, I’d want that to be a conscious choice
- Spaces automatically get me into the database list
- Hiding/rearranging views happens easier
In the end, some of my team members will be Admins or Editors in spaces and will inadvertently “re-arrange” things that should not be re-arranged. Sure, we can argue that they need to be careful, but to me it’d be easier to be generally in an “User” mode and have a toggle somewhere on the top to switch into a “Config Mode”. Over time, that config mode will be less and less used anyway as things solidify.
Thanks!
1 Like
What I would like in non-admin mode, is that all links/relations that now require Alt-click in order to become a clickable link, to just be a clickable link. This is for my users the most workflow hindering feature, which assumes that you always want to edit a link instead of merely using it. Examples are the pinned fields at the top of entities, and the relation fields in lists and boards.
1 Like
Why do you feel that this is a need specific to a non-admin mode? Wouldn’t you like this to be the case for admins and non-admins?
Yes, not having to use alt-click to navigate to a relation would be my preference for admins and non-admins.
But I see that my answer did not directly relate to the ‘non-admin’ switching feature requested. I was more pointing to an improvement of the user interface that better suits content creators and users than the structure creators/admins.
I think that whether a field is a clickable link or en editable fields, needs to be a field setting.
For example if a relationship to a parent item has more the purpose of navigation 99% of the time, it needs to be a direct link. If it is a tag field, then still I’d prefer it to be clickable links, since they are mostly used one time during creation of the entity, after that they are used to navigate by users (to list the tagged entities).
I am interested in this feature too, at least to have a switch to exclude all schema/fields/views editing in a workspace - just being able to create and edit entities, also to avoid unwanted modification.
Do you believe you request could merged with this one?
10 posts were merged into an existing topic: View as another user for admins
A post was merged into an existing topic: View as another user for admins
We are going to implement this feature in nearest future, if you want to share some ideas please go ahead. So far we are going to mainly hide things in Entity View and left Sidebar (and thinking about Views settings, but not sure yet)
What if the “Show Databases” toggle per space was the thing that toggled this? It would make that space into “Architect Mode” and the admin and creator features become visible.
There would need to be a shortcut in an entity view probably. Maybe in the breadcrumbs next to the space name?
Then the “Show Databases” in the main nav (currently just toggling the User’s DB) is the Architect Mode for the workspace and auto toggles all the other ones on/off with it.
Logic is that when you are configuring the space, you generally press the “show databases” button, then when you’re done, you hide them again.
This solves the issue of creators who are not admins, it’s per space. And it doesn’t live in a separate config screen, but just a mode using a toggle we’re already used to!
Sidenote: Admins accidentally changing global filters instead of personal filters has been quite a pain in one of my workspaces.
If they need to handle billing, but have no idea how to use Fibery?
Since this is being planned, I’ll add to the idea above: this also allows you to then change the icon from a database icon to a gear icon, which is a lot more recognizeable and understandable as to what it is. All users who I’ve shown Fibery to have no idea what the database icon is.
We are going to completely remove these elements from UI in User mode, but in Architect mode all databases will be visible by default
2 Likes
Good idea! A great step forward towards a more intuitive UI 
1 Like
I see, the only trouble I see with this is that some people have architect access to only one space. So from what I understand, they will also have the global architect mode toggle, right?
I feel that could be a bit weird to turn on a global toggle, and have only affect a few spaces, but not sure.
Maybe having the ability to toggle per Space, and also a global toggle to turn all on or all off? Just spitballing.
Yes, and we don’t want to complicate things here, one toggle is easy to get and it will be accessible by a single click or a shortcut
2 Likes