Automate365's Dynamic Content feature lets you create templates that automatically adapt to each scenario during provisioning. Instead of manually editing templates for each new site or project, you can use tokens (placeholders) that our system replaces with specific information.
Why use Dynamic Content?
Imagine you frequently provision new SharePoint sites or Teams for individual client projects. Each project requires the client's name to appear in the site title, specific document library names, or perhaps a welcome message on the homepage. Without dynamic content, you'd have to manually edit your template or the newly created site or team for every single client, a process prone to errors and very time-consuming.
Dynamic Content streamlines provisioning by using smart template placeholders. Users input data once when requesting a workspace (or it's auto-pulled), and Automate365 populates all relevant fields throughout the template during provisioning. This drastically reduces manual work, ensures perfect consistency across unique project workspaces, and significantly boosts provisioning speed and effectiveness.
Add tokens to your blueprint workspace
A blueprint workspace is an existing site, team, plan, dashboard (or similar) used as the foundational template to provision new, standardized workspaces.
To use dynamic content, simply insert $(YourTokenName) into your blueprint workspace, wherever you want information to be automatically filled in.
Example use cases:
$(DepartmentName): In a document titledWelcome to $(DepartmentName).docx, the token can become "Welcome to Marketing.docx."$(ProjectYear): A folder namedReports_$(ProjectYear)could deploy asReports_2025.
Import tokens when creating your template
When you create a template from an existing workspace in Automate365, our system will automatically detect all the $(token) placeholders you've added.
During this step, you'll specify which of these identified tokens should be used.
If selected, the token will be replaced during provisioning.
If unselected, it will remain as text "$(token)" in your deployed content.
Automate365 populates dynamic content during provisioning
Regardless of the provisioning method, Automate365 will always replace all selected tokens with your specific dynamic content during provisioning.
The way dynamic content is replaced depends on your deployment method:
Automated Provisioning (unattended, using Automations)
This is the most efficient way to use dynamic content, especially for large-scale or recurring deployments. With automated projects, you can map tokens directly to data sources. This means the system automatically pulls the correct information for each token, eliminating manual input during deployment.
Some examples are:
User Information: Map
$(SiteOwner)to the person requesting the site, or$(RequestedByEmail)to their email.Dates: A
$(DeploymentDate)token can be automatically populated with the exact date of deployment.Project Details: Connect
$(ProjectID)or$(BudgetCode)to fields in a connected SharePoint list, database, or Excel file.
On-demand provisioning (manual)
When provisioning a template from the BindTuning App, Company Catalog, or SharePoint catalog, you'll be prompted to fill in dynamic content fields during the installation process.
These fields correspond to the tokens you defined e.g., if you created a
$(DepartmentName)token, you'll enter the department name here.
In our original example, token replacement for a "Marketing" request would result in:
