requires a dialog component for this (same as editor)

michaelneale what permission should be used to control availability of the "Create Pipeline" button? I know there is a "create" permission available within each pipeline, although we can't really rely on that in the "first use" scenario (when there are no pipelines available in Jenkins).

Link to James' Sketch file.
https://www.dropbox.com/s/9tacojva7b2n9du/blueocean.sketch?dl=0

cliffmeyers well per pipeline permissions won't work here as we are creating a new pipeline. I would say for starters as long as they aren't read only we can at least offer to let them try to create a pipeline. If the permissions are more fine grained than we realise at the backend, we will see errors, and can adjust course

vivek do you know of any existing permissions in jenkins, perhaps that blue ocean already exposes via the API, that could be used to decide if the create pipeline link should be shown or not?

michaelneale Nothing that serves permission outside of pipeline api. Backend can check if user has create permission (anonymous or logged in).

As discussed - we want the inverse of the logic that decides if the login button should be shown. If the login button is shown then create should not be shown. If the login is not shown, the create should be shown.

PR: https://github.com/jenkinsci/blueocean-plugin/pull/567