While reusable policies provide a robust foundation for consistent governance across your Automate365 environment, you might encounter scenarios where a specific template requires unique governance rules. Template-specific policies allow you to define and apply governance settings that are exclusive to a single template, providing granular control tailored to its specific purpose.
This article guides you through the process of defining these unique policies during template creation in Automate365.
Policies during template creation
To create a template-specific policy, you must be in the process of creating a new template. If you haven't started yet, please refer to our guide on Understanding Templates before proceeding.
As you progress through the Automate365 template creation wizard, you will encounter the "Policies" step within the left-hand navigation of the wizard. This is where you can define policies that will be exclusively applied when a workspace is provisioned using this particular template.
Define a template-specific Policy
Within the "Policies" step, you will find sections corresponding to different types of governance policies, similar to those available for global reusable policies (e.g., Naming convention, Blocked words, External sharing, Group, Teams policies). For each policy type, you'll see a "+Create now" link at the bottom of the section.
To define a template-specific policy:
Click the "+Create now" link under the specific policy type you wish to configure.
This action will open the same intuitive configuration interface you use for creating global reusable policies. Fill in the desired settings and rules for your policy. These settings will only apply to workspaces created from this specific template.
After configuring your policy, you will be presented with options to define its scope. To ensure the policy is exclusive to this template, select the option "Use only for this template". Choosing this will save the policy settings as part of this template's draft.
No further action is needed for the policy itself at this stage; the template-specific policy will be saved automatically when you finalize and save the template draft. Once the template is published and used, this policy will be automatically applied to all new workspaces provisioned using it.
If you select "Save to Policies", a reusable policy will be created and stored in your central Policies list, accessible for use across multiple templates.
Let's now dive into the specifics of each policy type. Begin by understanding how to establish consistent naming standards for your workspaces.