-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipelines that are set to "Read only" should be visible and executable by users #580
Comments
Summary: When the pipeline is in public - read only mode, it is correct that others cannot change the pipeline. But it should be possible for others to not only copy the pipeline, but also to run the pipeline |
Moreover, we also need to discuss if a public pipeline started by one user can be seen and controlled by another user |
When a pipeline belongs to a user privately, and an admin runs it, the user cannot see it in the monitor. I think the user should not have the permission to cancel it, but should at least be able to see it because he is the owner. |
If the pipeline was executed by user A (normal user), it is his execution and user B (normal user) should not be able to control executions of user A. Currently, if user A creates a pipeline and executes, user B (with admin rights) can see such pipeline execution. |
So a suggest to solve the issue - When the pipeline is in public, read only mode, it should be possible for others to not only copy the pipeline, but also to run the pipeline - then we can discuss what should be adjusted next |
Why not to improve permissions model to be 'unix like' with rwx flags per pipeline? |
Hi, currently pipelines with access rights set to "Read only" can be seen by all users, but they cannot execute the pipelines. The only possible action is "Copy", and users have to use "Copy" to create private pipelines and then modify and execute them. I think the expected outcome is all users can see and also execute pipelines directly, but only creators and admins can modify them.
The text was updated successfully, but these errors were encountered: