> For the complete documentation index, see [llms.txt](https://docs.cremawork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cremawork.com/v2.0/customization/footer-type.md).

# Footer Type

If the footer is enabled, then we have provided the option of setting the type of Footer. The user can set the type of footer during run-time and in development mode by following the under-written steps:-

**Setting the Footer type in Run Time:-**

Click on the settings button on the right corner of the screen just below the notification icon, a drawer will open in which you will find a footer type select dropdown and by using that dropdown, you can choose the footer type.

**Setting the Footer Type in development mode (setting default Footer Type):-**

To set the default footer type,  go to the following file:-

```
src/@crema/utility/ContextProvider/defaultConfig.js
```

In this file, you will find a property named 'footerType'. You need to set the value of 'footerType' according to your choice from the accepted values. You can find the accepted values of 'footerType' in the file with the path:-

```
src/shared/constants/AppEnums.js
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cremawork.com/v2.0/customization/footer-type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.