Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2526
IMO introducing `EXECUTE` permission makes sense. For instance.
1. A shared notebook (dashboard) contains important indices and it requires
large query executions. Thus I don't want to allow readers to change dynamic
forms (dropdown). **It will be used only view-mode**
2. I have another notebook made for cooperation between UI team and
developer team. the developer team wrote queries and UI team will change
dynamic forms and execute queries. But the developer also wants to allow a
manager of the project sees the notebook but not execute.
for case (1), we need READ-ONLY permissions.
for case (2). we need to support READ-ONLY + EXECUTE permissions.
**introducing `EXECUTE` permission gives Zeppelin users flexibility can be
applied to multiple use cases**
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
