Workspace admins should NOT bypass security when launch import actions
As a "workspace admin" flagged user, I would like to have the behavior consistent with the security and roles set up to the user when it is launched an import action.
Currently, when a user is flagged as "workspace admin" if launches an import action can update data cells that the user does not have access (through "security selective access" or DCA flags).
I do not find any advantage that a user has the ability to update read-only data cells (or cells that the user does not have access) only because he/she is flagged "workspace admin". This is happening even the role associated with the user is other than "Full access".
Maybe this was implemented to have a high-level user to bypass the front-end restrictions, but, in my opinion, it is more important to have the user consistent with their role and security when using the front-end.
The "workspace admins" are consistent with their security and roles when they are using the front-end, except when they launch import actions. Why have this exception? 🙂
I hope it will be solved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.