Be able to hide "sections" of variables in a project template on a tenant and envrionment. For example: I have single-sign-on configuration in web.config. If the checkbox "Enable Single-Sign-On configuration" is checked is not checked I would like to remove the configuration variables bellow the checkbox.

Having tons of these sections really clutters the overview and making it hard to configure.

Also being able to group variables into +/- sections with a header would be really great.

I would like to extend this even further on a tenant level using tenant variables to enabling features such as the "Enable feature Single-Sign-On" in the example above".

I know you have said that you do not like to make variables and their existance to complex as it could make deployment difficult (I saw a response regarding it in the support forums).

But it could really be as simple as a binding syntax on the field.

Tenant A has single-sign-on. A project-tenant specific variable is set to EnableSingleSignOn="True", default="False"

The project-tenant-environment specific project template variable
UseSingleSignOn could then have it's default value set to the binding

{configurable-if EnableSingleSignOn}False{/if}

If EnableSingleSignOn is "False" then the default value would always be set and the field would not be visible.

Same goes to the keys of the single-sign-on configuration.
The key "ClaimDomain" would have the default value #{configurable-if UseSingleSignOn}{/if} and would be configurable/visible only if
UseSingleSignOn is set to true.

As you do not support optional variables you can just leave it as a empty string. I am using the workaround of an empty global variable called #{AllowEmpty} which I put in all fields that are allowed to be empty.

In this case I would use #{configurable-if [Single-Sign-On-Key]}{#AllowEmpty}{/if} to allow empty values when the feature isn't active or enabled on the environment.