Extend Launch role to support additional workflow configuration, dataset management, and pipeline invocation
complete
Rob Newman
The current
Launch
role in Seqera Platform is too restrictive for many use cases. Users with the Launch
role cannot supply additional workflow configuration, add datasets, invoke pipelines not registered in Launchpad, or modify certain pipeline parameters at launch time. This creates friction for teams that want to empower scientists to run pipelines without granting full
Maintain
-level access. The Launch
role should support configurable permission extensions so admins can selectively allow dataset creation, additional config overrides, resource label management, and pipeline invocation for Launch
role users.Rob Newman
updated the status to
complete
Modifying the default
Launch
role or creating a custom role to include additional permissions is possible using Fine Grained Auth (FGA) which is now available in both Cloud and Enterprise.Rob Newman
Merged in a post:
Allow Launch users to invoke pipelines not bound to Launchpad
G
Gold Orca
Is there anyway we could request that
Launch
role participants be given permission to invoke pipelines not stored in launchpad? If we make an update to a pipeline, we would then have to re-register against every workspace that uses that pipeline. It can be scripted/automated, but seems like an unnecessary layer/complication?Rob Newman
Merged in a post:
Launch role users cannot supply additional workflow config
Jon Manning
I have a Launch role user who currently needs to supply some additional config to
nf-core/fetchngs
. I directed him to the launch settings to supply the snippet there, like:process{
withName: 'SRATOOLS_FASTERQDUMP' {
ext.args = '--split-files --include-technical'
}
}
But he has reminded me that
Launch
role users are unable to access the launch settings. Could you advise as to how
Launch
role users might supply such runtime configuration?Rob Newman
updated the status to
acknowledged
Automation incorrectly assigned this as complete. This is not complete.
The status was updated to
complete
Rob Newman
updated the status to
acknowledged
Merged all relevant feature requests
Rob Newman
Merged in a post:
Extend label usage to users with Launch role
S
Shamrock green Lizard
We have users that would like to make use of the
label
function. However, the minimum required role is "Maintainer" which grants too many other privileges. Can you extend label usage to users assigned the "Launch" role?Rob Newman
Merged in a post:
add data preview to 'launch' profile permissions / custom profiles
N
Neon carrot Goldfish
I would like my "launch" level users to be able to preview data. Basically, I have users that don't need to be messing with launch or any other settings, but also would benefit from having an easy point and click method of previewing the data from platform.
I wonder if it would be possible to allow admin to create custom permission profiles and maybe to select from among the set of permissions that already exist within the launch/maintainer/... profiles?
Rob Newman
Merged in a post:
Allow launch role to download files from Data Explorer
C
Crimson Koala
We think the Launch role in a workspace should have the ability to download files from the Data Explorer. When a Launch role user launches a pipeline run, the user should be able to download the data files that are output from the pipeline run. Please let us know if this makes sense, and if so, if this could be part of a future release. Thanks!
L
Lime Tuna
This would also be really useful for us. We have many users who monitor and intervene when runs fail due to certain errors, so only require "Launch" permissions. But they also really value the ability to label runs with information about errors or for other grouping reasons. We can't give these users "Maintainer" permissions as config etc. needs to be managed by a dedicated team.
Load More
→