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

# Template inputs and secrets

> Understand which template values are required, which are sensitive, and how they affect rendering and upgrades.

<Tip>
  **Live.** This area is documented as current, user-reliable behavior.
</Tip>

## Goal

Avoid misconfiguring a service by treating template inputs as throwaway form fields.

## Prerequisites

* A template detail page or deploy flow

## Workflow

<Steps>
  <Step>
    Review required inputs before starting deployment.
  </Step>

  <Step>
    Treat secret inputs differently from ordinary defaults.
  </Step>

  <Step>
    Expect future template upgrades to reuse saved inputs where possible.
  </Step>
</Steps>

## Required vs optional inputs

The template detail page shows how many inputs a template needs and how many are secret. Required inputs must be supplied before the template can render into a stack; optional inputs fall back to the template defaults.

## Secrets are handled differently

* Secret inputs (passwords, API keys, tokens) are treated as sensitive rather than plain defaults.
* Provide real values at deploy rather than leaving placeholders in a secret field.

## Inputs and upgrades

Saved inputs are reused when you upgrade a template-backed stack to a newer version, so you do not re-enter everything. When a newer version introduces a new required input, the upgrade preview flags it as missing so you supply it before applying.

## Expected result

<Check>
  Template deployment inputs are supplied deliberately and with less surprise at upgrade time.
</Check>

## Related guides

<CardGroup cols={2}>
  <Card title="Deploy from a template" href="/templates/deploy-from-a-template">
    Launch a curated service by supplying template inputs, choosing placement, and reviewing the rendered summary.
  </Card>

  <Card title="Updating template-backed stacks" href="/templates/updating-template-backed-stacks">
    Preview diffs, resolve missing inputs, and apply the latest published template version safely.
  </Card>

  <Card title="Template upgrade safety and service notes" href="/templates/template-upgrade-safety">
    Understand why an upgrade is safe, risky, or blocked, and how template readiness notes should influence operator decisions.
  </Card>
</CardGroup>