Templates
Use Statsig experiment templates to standardize hypothesis, metrics, and review workflows across your experimentation program for higher quality tests.
How templates work
Templates enable you to create a blueprint for gates, dynamic configs, and experiments to enable standardization and reusability across your project. Templates can help enforce a rollout sequence, or make it easy for new experimenters to start with your standard team settings for experimentation.
Organization admins can enforce templates at the org level (through Organization Settings and Role-based Access Controls) or at the Team level. The sections below describe the levels of controls and permissions available for templates.Creating templates
There are two primary ways to create a new template:
- From the Templates page under Product Configuration
- From a gate or experiment you want to turn into a new template
Creating templates from project settings
To create a new template from Project Settings, navigate to Settings -> Project Configuration -> Templates and click the +Create New CTA, then select whether you want to create a gate, experiment, or dynamic config template.
Converting an existing config into a template
To convert an existing config into a template, tap the "..." menu in the config and select Save as Template. Enter a name and description, then save.
Managing templates
To manage templates, go to the Templates setting under Product Configuration.
Statsig controls who can create or modify templates through Role-based Access Controls in People → Roles. By default, org and project admins can modify or delete any template.
Creating configs from templates
To create a config using a template, select a template from the template selector at the time of config creation. If templates are required at the organization or team level, you can't proceed with config creation until you select an approved template. Team admins configure the list of template options in the drop-down (refer to the section below).
Template settings and permissions
There are two key layers of settings governing templates:
- Org level
- Team level
Org-level templates settings
Within Experiment and Gate Policies (Settings -> Project Configuration -> Feature Management/ Experimentation - Organization Tab), you can enforce that a template is used for any new gate, dynamic config, or experiment creation. Only organization admins can configure this setting.
You must create at least 1 experiment/gate template for users to choose if you toggle on this setting, otherwise they're blocked from creating new configs.
Team-level templates settings
At the team level, you can configure which templates members of that team can choose from at the time of config creation, and whether to require use of a template.
This setting only applies if templates aren't already required at the organization level, which overrides any team-level configuration.
To configure team-specific templates, navigate to Settings -> People -> Teams -> choose a team -> Settings and then choose which templates are allowed for gates, dynamic configs, and experiments.
Known limitations
- Statsig doesn't support renaming experiment templates. To rename a template, create a new experiment using the template, then create a new template from that experiment with the desired name.
- Statsig doesn't support modifying templates through the Console API.
Was this helpful?