Seqera Platform Feature Requests

Update the current user role permissions to manage more fine-grained permissions (Role Based Access Control, etc).

Nextflow Secrets provide built-in support to allow users to handle and manage sensitive information used inside a Nextflow task in a safe manner. This can be used to include keys to access secure databases or APIs tokens for use in external services. Seqera Platform has already implemented management of Nextflow Secrets at the Workspace and User levels. This iteration introduces improvements to the secrets across Seqera Platform to expand the support of Secrets to Azure.

Allow access and role assignment in Seqera Platform based on 3rd-party authentication groups such as OIDC LDAP groups.

Enable the creation of a Service Account that doesn't require an active email address or associated user identity and can be managed by Admin users. This Service Account should be able to generate an API Token which allows for job submission.

We use an on-premises mail server to handle logins. However, for sending email notifications from Seqera Platform/Tower for access and login requests by non-trusted email domains, we want them sent from another email address but this is not currently possible.

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?

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?

Enable access to a workspace using a publicly accessible URL. A user can share a link to the workspace and the user, provided they have a Seqera Platform account, can access successfully.