Permission to edit Scenarios only

Sydnie

We have use cases where we do not want someone to have edit or admin permissions to a project, but we would like them to be able to enable/disable scenarios entirely or the steps within them. This is in addition to being able to run the scenario of course. We are thinking about the case where there is a failure or need to stop the projects and the project owner /admins are away. Someone such as myself (a developer) may not be considered operations and would not have admin permissions, but does know the project well enough to prevent further failures by stopping. rerunning or partially re running scenarios. We have dependent projects and there are cases where it makes sense to disable scenarios on another project while troubleshooting failures.

Turribeach

This sort of permissioning granularity does not exist in the product out of the box. However you do have all the tools available for a custom solution using a Dataiku Webapp and the Dataiku Python API. A Dataiku Webapp is basically some Python code with some HTML/CSS/JS code. While there aren't any examples on how to run scenarios on a Dataiku Webapp this Webapp example shows how to list and delete a selection of projects. Users only need read permissions on the project where the webapp lives and you can apply further permissioning checks in your webapp itself (mke sure you set the app to be authenticated). For instance you can list all their Dataiku groups and only allow them to perform valid actions according to their permissions. Crucially the Dataiku Webapp itself will run with a higher level account which is permissioned to perform the actions on the user's behalf. Finally the best kept secret is that Dataiku users only need a Dataiku Reader license to run Dataiku Webapps. Dataiku Reader licenses are effectively free so speak with your account manager to get them added to your license if you don't have any Readers allowed.