Severity
Block multi-tenant deployments but tenants can be deployed to individually
Version
2026.1.11242
Latest Version
I could reproduce the problem in the latest build
What happened?
Scenario:
- There are two tenants, Tenant 1 and Tenant 2.
- User is assigned to two Teams in Octopus: Team 1 and Team 2.
- Team 1 has Project Deployer scoped to Tenant 1.
- Team 2 has Project Deployer scoped to Tenant 2.
Deploying to either tenant individually for a user in this scenario succeeds but attempting to deploy to multiple tenants at once you are shown an error: You do not have permission to perform this action. Please contact your Octopus administrator. Missing permission: DeploymentCreate
Reproduction
- Create two tenants and scope them to a project.
- Create two teams and apply the Project Deployer user role to both of them, scoping the teams to only one of the two tenants created.
- Assign a user to both of those teams.
- Attempt to deploy a multi-tenant release.
Error and Stacktrace
You do not have permission to perform this action. Please contact your Octopus administrator. Missing permission: DeploymentCreate
More Information
No response
Workaround
Tenants can be deployed to individually, this could also be scripted in order to perform the action more quickly in the case of large tenant environments. Alternatively and potentially 'easier', move the permissions scopings into the same team.
Severity
Block multi-tenant deployments but tenants can be deployed to individually
Version
2026.1.11242
Latest Version
I could reproduce the problem in the latest build
What happened?
Scenario:
Deploying to either tenant individually for a user in this scenario succeeds but attempting to deploy to multiple tenants at once you are shown an error:
You do not have permission to perform this action. Please contact your Octopus administrator. Missing permission: DeploymentCreateReproduction
Error and Stacktrace
You do not have permission to perform this action. Please contact your Octopus administrator. Missing permission: DeploymentCreateMore Information
No response
Workaround
Tenants can be deployed to individually, this could also be scripted in order to perform the action more quickly in the case of large tenant environments. Alternatively and potentially 'easier', move the permissions scopings into the same team.