> 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/use-app-templates.md).
# Use app templates
Browse templates, choose a starting point, and understand the available template categories.
Templates give you a ready-made starting point for a common business process. Select a template, then customize its structure and data for your workflow.
## **Open the template gallery**
{% stepper %}
{% step %}
### **Open Home**
In the main navigation, click :house: **Home**.
{% endstep %}
{% step %}
### **Choose a template**
Click **Use a template**. The template gallery opens.
{% endstep %}
{% step %}
### **Preview and install**
Use a category to narrow the gallery. Select a template to open its preview.
The preview shows its image, description, usage guidance, and category. Select **Add AI-generated sample data** to include example records, then click **Install** to create an app from the template.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
**Template translations**
When you change the language setting in your profile, content in an app installed from a template is translated too. The data in records remain untranslated.
{% endhint %}
## **Available templates**
The gallery groups templates by business area. Select **All** to browse every available template.
* **My organization** lists templates published by other workspaces in your organization. Learn how to [publish app templates](/builder-hub/design-your-app/create-and-manage-apps/publish-app-templates.md) to make an app available there.
* Use **CRM**, **Finance**, **HR**, **Operations**, or **Project management** to find templates for that area of work.
Each template gives you a practical starting point for your business process.
Templates labeled **No code version** use simple logic rather than advanced logic. This makes them easier to customize.
* **Time tracking (No code version)** provides a simple starting point for recording hours.
* **Time Tracking** supports general time tracking.
* **Expenses & Receipts (No code version)** tracks expenses and annual budgets. Totals, remaining amounts, and budget use are calculated from expense records.
* **Inventory & Lending (No code version)** manages equipment and loans in one app. Its dashboard shows available, lent, and overdue items, plus open loans by due date.
* **Contacts (No code version)** brings companies, contacts, and communication history together. Its home page maps company status and identifies contacts that need attention.
* **Contact Management** helps you manage contacts and build CRM-related apps.
* **Incident Management** supports incident management, tasks, and documentation.
## **Make the app your own**
Installing a template creates an app you can adapt to your process. Change its tables, fields, views, and pages as needed. For example:
* Add or change fields in [Add and edit data fields in your tables](/builder-hub/design-your-app/add-and-edit-data-fields-in-your-tables.md).
* Organize records with [Work with views](/builder-hub/visualize-and-organize-your-data/work-with-views.md).
* Build dashboards with [Create and customize pages](/builder-hub/visualize-and-organize-your-data/create-and-customize-pages.md).
---
# 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/use-app-templates.md?ask=&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.
