---
title: stack kb cases create-case-template cli command
description: Create a case template 
url: https://www.elastic.co/elastic/docs-builder/docs/4118/reference/elastic-cli/cli/stack/kb/cases/create-case-template
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview
---

# stack kb cases create-case-template cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack kb cases create-case-template \
  --definition <definition> \
  --owner <owner> \
  [options]
```

Create a case template

## Options

<definitions>
  <definition term="--definition string required">
    The template definition as a YAML string: case defaults (name, severity, category, tags, assignees, connector, settings) and a `fields` array of inline field definitions or `$ref` entries pointing into the owner's field library. Stored field values appear on cases under `extended_fields` keys shaped `<field_name>_as_<storage_type>`.
  </definition>
  <definition term="--owner enum required">
    **Values:** cases, observability, securitySolution
  </definition>
  <definition term="--dry-run">
    When true, validates the request without creating the template and returns `{"valid": true}`.
  </definition>
  <definition term="--description string">
    A description of the template.
  </definition>
  <definition term="--is-enabled">
    Disabled templates are hidden from the case creation flow.
  </definition>
  <definition term="--name string">
    The template identity name, unique per owner (case-insensitive). May be omitted when the YAML definition provides a case-default title (`name:`), which is then used as the identity name.
  </definition>
  <definition term="--tags string[]">
    **Repeatable:** pass `--tags` multiple times to supply more than one value
  </definition>
  <definition term="--input-file string">
    path to a JSON file to use as command input
  </definition>
</definitions>


## Global Options

<definitions>
  <definition term="--json">
    output as JSON
  </definition>
</definitions>