> ## Documentation Index
> Fetch the complete documentation index at: https://kasava.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Templates

> Customize the output format of @kasava commands

Navigate to **Settings → Templates** to customize the output format of @kasava commands for each platform and action type.

## What Are Templates?

Templates control how Kasava formats responses when team members use `@kasava` commands in GitHub issues, Linear issues, and other connected platforms. Each combination of platform and action type has a template that determines the structure and content of the generated response.

For example, when someone uses `@kasava summarize` on a GitHub issue, the template for the "GitHub + Summarize" combination determines how the summary is formatted.

## Accessing Templates

<Steps>
  <Step title="Open Settings">
    Click your avatar in the bottom-left sidebar and select **Settings**
  </Step>

  <Step title="Navigate to Templates">
    Click **Templates** in the left navigation menu
  </Step>
</Steps>

## Template Interface Overview

The Templates page consists of several key elements:

| Element              | Description                                                  |
| -------------------- | ------------------------------------------------------------ |
| Platform Tabs        | Switch between GitHub, Linear, and other connected platforms |
| Action Type Selector | Choose which action type's template to edit                  |
| Variables Panel      | View available template variables with descriptions          |
| Template Editor      | Edit the template content                                    |
| Preview Tab          | See how the template looks with sample data                  |

## Selecting a Platform

Use the platform tabs at the top of the page to switch between different platforms:

* **GitHub** - Templates for GitHub issue responses
* **Linear** - Templates for Linear issue responses
* **Asana** - Templates for Asana task responses
* **Jira** - Templates for Jira issue responses

Each platform may have slightly different available variables based on the platform's data model.

## Selecting an Action Type

Use the action type dropdown to choose which command's template to customize:

1. Click the **Action Type** dropdown
2. Select from available built-in actions (Summarize, Document, Plan, etc.)
3. Actions with custom templates show a **Custom** badge

<Tip>
  Click the **+** button next to the action type dropdown to create a new custom action type. See [Action Types](/docs/account/settings/action-types) for details.
</Tip>

## Using Template Variables

The Variables panel on the left shows all available placeholders you can use in your template. Variables are inserted using double curly brace syntax:

```
{{variableName}}
```

Common variables include:

| Variable          | Description                          |
| ----------------- | ------------------------------------ |
| `{{title}}`       | The issue or task title              |
| `{{description}}` | The issue body or description        |
| `{{author}}`      | The person who created the issue     |
| `{{labels}}`      | Applied labels or tags               |
| `{{assignees}}`   | Assigned team members                |
| `{{content}}`     | Generated AI content for this action |

The exact variables available depend on the selected platform and action type. Hover over any variable in the Variables panel to see its description.

## Editing Templates

<Steps>
  <Step title="Select Platform and Action">
    Choose the platform tab and action type you want to customize
  </Step>

  <Step title="Edit the Template">
    Modify the template content in the editor. Use the available variables from the left panel.

    The editor supports Markdown formatting for rich output.
  </Step>

  <Step title="Preview Changes">
    Click the **Preview** tab to see how your template looks with sample data
  </Step>

  <Step title="Save Template">
    Click **Save Template** to save your custom template
  </Step>
</Steps>

## Template Actions

The editor toolbar provides several actions:

| Button               | Description                                                   |
| -------------------- | ------------------------------------------------------------- |
| **Preview**          | Generate a preview with sample data                           |
| **Reset to Default** | Restore the original built-in template                        |
| **Delete Custom**    | Remove your custom template (only shown for custom templates) |
| **Save Template**    | Save your changes                                             |

## Custom vs Default Templates

* **Default Templates** - Built-in templates provided by Kasava. These are used when no custom template exists.
* **Custom Templates** - Your organization's customized versions. When saved, custom templates override the default for all team members.

An alert at the bottom of the editor indicates when you're using a custom template that overrides the default.

## Previewing Templates

The Preview tab shows how your template will look when rendered:

<Steps>
  <Step title="Click Preview Tab">
    Switch to the **Preview** tab in the top-right
  </Step>

  <Step title="Review Output">
    The preview shows your template with sample data filled in, rendered as Markdown
  </Step>
</Steps>

Preview updates automatically as you edit the template.

## Resetting to Default

To restore a template to its original state:

1. Click **Reset to Default** in the editor toolbar
2. The template reloads with the built-in default content
3. Click **Save Template** to save the reset, or continue editing

## Deleting Custom Templates

To remove a custom template and revert to the default:

1. Click **Delete Custom** in the editor toolbar (only visible for custom templates)
2. Confirm the deletion when prompted
3. The default template will be used going forward

## Best Practices

1. **Keep it concise** - Responses should be scannable and actionable
2. **Use consistent formatting** - Maintain similar structure across action types
3. **Include context** - Reference issue metadata like `{{title}}` and `{{labels}}`
4. **Test thoroughly** - Preview templates with different scenarios before saving
5. **Document conventions** - Let your team know about any custom templates

<Tip>
  Custom templates apply organization-wide. Coordinate with your team before making significant changes.
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Action Types" icon="wand-magic-sparkles" href="/docs/account/settings/action-types">
    Create custom @kasava commands
  </Card>

  <Card title="Integrations" icon="plug" href="/docs/integrations/overview">
    Connect platforms for templates
  </Card>
</CardGroup>
