coder
diff --git a/‎docs/admin/provisioners.md
Lines changed: 16 additions & 0 deletions b/‎docs/admin/provisioners.md
Lines changed: 16 additions & 0 deletions
diff --git a/‎docs/images/admin/provisioner-tags.png
34.8 KB b/‎docs/images/admin/provisioner-tags.png
34.8 KB
@@ -148,10 +148,18 @@ coder templates push on-prem-chicago \
   --provisioner-tag datacenter=chicago
 ```
 
+This can also be done in the UI when building a template:
+
+> ![template tags](../images/admin/provisioner-tags.png)
+
 Alternatively, a template can target a provisioner via
 [workspace tags](https://github.com/coder/coder/tree/main/examples/workspace-tags)
 inside the Terraform.
 
+> [!NOTE] Workspace tags defined with the `coder_workspace_tags` data source
+> template **do not** automatically apply to the template import job! You may
+> need to specify the desired tags when importing the template.
+
 A provisioner can run a given build job if one of the below is true:
 
 1. A job with no explicit tags can only be run on a provisioner with no explicit
@@ -170,6 +178,14 @@ However, it will not pick up any build jobs that do not have either of the
 `environment` or `datacenter` tags set. It will also not pick up any build jobs
 from templates with the tag `scope=user` set.
 
+> [!NOTE] If you only run tagged provisioners, you will need to specify a set of
+> tags that matches at least one provisioner for _all_ template import jobs and
+> workspace build jobs.
+>
+> You may wish to run at least one additional provisioner with no additional
+> tags so that provisioner jobs with no additional tags defined will be picked
+> up instead of potentially remaining in the Pending state indefinitely.
+
 This is illustrated in the below table:
 
 | Provisioner Tags                                                  | Job Tags                                                         | Can Run Job? |