Your Setup:
- SeaTable Cloud, Self-hosted (both current version 6.2.12)
Describe the Problem/Error/Question:
One of our users locked herself out from her own app. According to her, she was under the assumption that the “roles” within the app did not affect the editing side of the app, but only the display side. She also assumed that editing rights for the app came solely from the base administration rights, and not from within the app.
This is what the tried in order to have a clean view on the base (screenshot using my admin user for demonstration purposes)
I succeeded to restore access by exporting in importing the base via .dtable file. Obviously, that file does not contain App user data. Good for us, though she had to redo all the App user data.
Questions:
- Was the Export / Import the only way to save the app?
- Shouldn’t the system prevent such an Admin lockout?
Personal remark: As far as I can tell, the permission to edit an app (in addition to the permission to lock yourself out, see above) is linked to the “Admin” role for the whole base, right? And that role is deducted from the role in a group, if the base belongs to a group?
That repeatedly clashes with our organisational structures: A lot of times, we need to enable collaborators to work only on the app. For example, our graphics specialist needs to add graphics to an app page, or our BI specialist needs to add statistics. As far as I know, I have to make them both Administrators in the relevant group, thus giving them full access to all bases and apps of that group? Which is not ideal, assuming that they are not SeaTable specialists.
Or am I missing something?
