Scoping a Team with the LibraryVariableSetEdit permission to an Environment affects ability to edit Script Modules

[LewisJohnsonOctopus]

Severity

No response

Version

Tested on 2026.1.11242, 2026.1.11349

Latest Version

None

What happened?

When scoping a team with the LibraryVariableSetEdit permission to an Environment and attempting to edit a script module, this causes an error message stating the LibraryVariableSetEdit permission is missing.

You do not have permission to perform this action. Please contact your Octopus administrator. Missing permission: LibraryVariableSetEdit
This action requires permission to edit library variable sets. At least one of your teams has this permission in a limited scope, but this doesn't cover the project or environment in question.

Reproduction

Have a Team with a UserRole that contains the LibraryVariableSetEdit permission (Picture 1)
Scope this Team to an Environment (Picture 2)
Attempt to edit a Script Module (See error in What Happened? section)

Picture 1

Picture 2

Error and Stacktrace

You do not have permission to perform this action. Please contact your Octopus administrator. Missing permission: LibraryVariableSetEdit
This action requires permission to edit library variable sets. At least one of your teams has this permission in a limited scope, but this doesn't cover the project or environment in question.

More Information

No response

Workaround

Remove scoping to Environments.
The safest way to do this would be to create a new UserRole with the LibraryVariableSetEdit permission and have this unscoped. You will also need to remove the LibraryVariableSetEdit permission from your current UserRoles that are scoped.