> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/design-your-app/create-and-manage-apps/publish-app-templates.md).

# Publish app templates

Publish an app as a template for other workspaces in your organization.

Publish an app to help other workspaces start with a structure that works for your organization. They can install it as a template and customize their own copy for their workflow.

{% hint style="info" %}
Only admins can publish an app template.
{% endhint %}

{% stepper %}
{% step %}

### **Open App settings**

Open the app you want to publish. In the app navigation, click **App settings**.

Turn on **Builder mode** if **App settings** is not visible.
{% endstep %}

{% step %}

### **Open the publish dialog**

In **Publish to your organization**, click **Publish template**.
{% endstep %}

{% step %}

### **Add template details**

Enter a **Name** and a **Short description**. The short description can contain up to 30 words.

Use the rich-text editor in **Full description** to explain what the template does and how to set it up. Structure the description with headings, paragraphs, and lists.

Verify the pre-selected organization where your app template will be published.

Enter a **Category**. The category can contain up to 20 characters.
{% endstep %}

{% step %}

### **Add preview images**

Add up to three preview images. The first image becomes the template’s main image.

Use images that are at least 800 pixels wide.
{% endstep %}

{% step %}

### **Publish and share the template**

Click **Publish**. Other workspaces can find the app in the template gallery. They select **My organization** to install it as a template.

After publishing, **App settings** shows the template name and **Template ID**. Use this section to copy the ID or withdraw the template.
{% endstep %}
{% endstepper %}

Learn how workspace users find, install, and customize published templates in [Use app templates](/builder-hub/design-your-app/create-and-manage-apps/use-app-templates.md). 

## **Update a published app template**

Update a template by changing the app, withdrawing the published template, then publishing it again.

{% stepper %}
{% step %}

### **Update the app**

Make the required changes to the app.
{% endstep %}

{% step %}

### **Withdraw the published template**

Withdraw the current template by following the steps below.
{% endstep %}

{% step %}

### **Publish the updated template**

Publish the app again by following the publishing steps above.
{% endstep %}
{% endstepper %}

## **Withdraw an app template**

Withdraw a template to remove it from the template gallery. Users who already installed it keep access to their app.

{% stepper %}
{% step %}

### **Open App settings**

Open the published app. In the app navigation, click **App settings**.

Turn on **Builder mode** if **App settings** is not visible.
{% endstep %}

{% step %}

### **Copy the template details**

In the template section, note the **Template name** exactly as shown. Then copy the **Template ID**.
{% endstep %}

{% step %}

### **Withdraw the template**

Click **Withdraw template**. Enter the **Template name** and **Template ID**, then click **Withdraw**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Withdrawing removes the template from the gallery. It does not remove apps that users already installed.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ninox.com/builder-hub/design-your-app/create-and-manage-apps/publish-app-templates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.