Skip to main content

Automate365 Release - June 2026

Written by BindTuning Team

This release focuses on improving how templates are deployed across different teams and scenarios, without compromising their original design or governance model. This helps teams adapt templates to specific needs without modifying the original configuration.

It introduces more flexibility during template installation by allowing key settings, such as logos and storage limits, to be adjusted at the point of deployment, instead of being locked in the template definition. This change aligns with current behavior of other settings, including sensitivity labels or privacy.

For administrators and template owners, this reduces the need to maintain multiple versions of the same template while ensuring that key settings remain aligned with organizational standards.


Configurable Logo and Storage during template deployment

When creating a template in Automate365, template creators could already define a Logo and a maximum Site Storage limit.

Until now, anyone installing that template had to accept those values, as there was no way to adapt them without editing the original template.

Two changes improve this behavior:

· Configurable flexibility during template creation

· Adjustment of Logo and Storage at installation time

Configurable flexibility during template creation

The template creation wizard now includes an option per setting (Logos and Storage) to explicitly allow or restrict changes during installation.

Adjustment of Logo and Storage at installation time

When the option is enabled, the installation wizard gains a dedicated step for each, where the installing user can adjust Logo and Storage independently to fit their needs - without touching the template itself.


This update strengthens the balance between governance and flexibility in template deployment. It ensures that templates remain consistent by design, while still allowing controlled variation where needed.

These changes reduce duplication, simplify template management, and provide a more predictable setup experience. They also establish a clearer foundation for scaling template usage across teams without introducing fragmentation.

Did this answer your question?