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

# Application templates

> Add applications to Iru Identity from a catalog of ready-made templates, then customize SAML or OIDC settings by ejecting from the template.

An **application template** is a ready-made definition for a known service.
Creating an app from a template fills in the standard configuration - protocol
settings and attribute mapping - so you only supply what is specific to your
tenant, such as the web addresses for your instance of the app.

Templates live in the **App Templates** catalog. Each template has an icon and
one or more **versions**, and is identified by a short slug.

<Tip>
  Templates are the fastest way to add an app. Reach for the catalog first, and
  only build a [custom SAML](/en/identity/applications/saml-applications) or
  [OIDC](/en/identity/applications/oidc-applications) app when no template fits.
</Tip>

## Create an application from a template

<Steps>
  <Step title="Open the catalog" icon="magnifying-glass">
    In **Apps**, choose to add an application and search for your service by
    name. Recommended templates appear as you type; you can also browse the full
    template library.
  </Step>

  <Step title="Pick a template and version" icon="layer-group">
    Select the template, then choose the **version** you want. Different versions
    cover different configurations of the same service.
  </Step>

  <Step title="Fill in tenant-specific values" icon="pen">
    Set the **display name** that will appear in your dashboard, and provide any
    values the template asks for - these vary by template, and are typically the
    web addresses or identifiers unique to your instance of the service.
  </Step>

  <Step title="Create the app" icon="circle-check">
    Iru creates the application from the template and opens it. The protocol
    settings and attribute mapping are already in place.
  </Step>

  <Step title="Assign access and activate" icon="user-check">
    Assign the users or groups who should have the app, then activate it. See
    [Assigning access](/en/identity/applications/assigning-access).
  </Step>
</Steps>

## Working with a template-based app

An app created from a template stays linked to it. On the app's page, the header
shows which **template** and **template version** it came from. You can change
the selected version or update the tenant-specific values, and Iru keeps the
standard configuration aligned with the template.

<Note>
  Because the standard configuration is managed by the template, the protocol
  settings on a template-based app are not freely editable. To take full control,
  eject the app from its template.
</Note>

## Eject from a template

**Ejecting** detaches an app from its template so you can edit every setting
directly, exactly like a custom app. Use it when you need to diverge from what
the template provides.

<Steps>
  <Step title="Open the app's actions menu">
    On the application's page, open the actions menu in the header.
  </Step>

  <Step title="Choose “Eject Template”">
    Confirm the action. The app keeps its current configuration but is no longer
    linked to the template.
  </Step>

  <Step title="Customize freely">
    All protocol settings and attribute mappings are now editable. Edit them in a
    draft and set it as current, the same as any other app.
  </Step>
</Steps>

<Warning>
  Ejecting is one-way. Once an app is detached, it no longer receives template
  updates and cannot be re-linked. Eject only when you genuinely need to
  customize beyond the template.
</Warning>

## Where to go next

<CardGroup cols={2}>
  <Card title="Applications overview" icon="grip" href="/en/identity/applications/applications-overview">
    How apps, protocols, and versioning work in Iru.
  </Card>

  <Card title="SAML applications" icon="file-signature" href="/en/identity/applications/saml-applications">
    Configure an ejected or custom SAML app in detail.
  </Card>

  <Card title="OIDC applications" icon="key" href="/en/identity/applications/oidc-applications">
    Configure an ejected or custom OIDC app in detail.
  </Card>

  <Card title="Assigning access" icon="user-check" href="/en/identity/applications/assigning-access">
    Grant the app to users and groups.
  </Card>
</CardGroup>