> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/white-label-feathery/offer-custom-form-templates.md).

# Offer Custom Form Templates

Build your own custom form templates to offer your users.

Feathery offers a number of out-of-the-box form templates that users can take advantage of. However, in your white label product, you may want to offer custom form templates. To do so, you can follow these steps.

1. In your white label admin account, create a form that you want to make available as a template to your users.
2. Navigate to its form settings. Under tags, include the `EnabledTemplate` tag - this exposes the form as a template in the library available to your user workspaces. If there is at least one enabled custom template, Feathery's default template library will be replaced.
3. You can also set the following two optional tags for additional customization:
   1. `FeatheryCategory`: A custom category of templates that your form belongs to. Categories will display to your users when selecting templates.
   2. `FeatheryIconURL`: The image to show to the user when choosing their template. This should typically be a preview image of the template form.

If you turn your form off, it will no longer show up as an available template for your users.


---

# 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.feathery.io/platform/white-label-feathery/offer-custom-form-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.