The ability to fork a version to edit on your own is a great opportunity for any user to modify and enrich an existing applet, but many times we want the power of an advanced UI without ability for end user to make modifications or see even the code without first requiring a dev team/process to pull git repo and host somewhere else which increases the technical limitations on a no-code app.
For instance, I can build a powerful applet to connect natively to a gsheet and allow a user to add/modify/delete records within that connected file, but would not want that same user the ability to modify code base calculations built within the applet. The risk I see is that even if they are prompting a modification to a date format to better read in their time zone on a forked version, it’s still connected to the same gsheet and such prompting might incidentally affect duration calculations without them aware and be a hidden problem.
A couple options come to mind for solving this issue in the future:
-
add a new “Reader” authorities role that denies remix, code, and chat views for the applet
-
create a robust RBAC config panel that allows applet owner to decide on sharing permissions (see screenshot below for sample taken from Tableau):
