> For the complete documentation index, see [llms.txt](https://fleetdocs.hyvikk.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fleetdocs.hyvikk.space/explore-features/settings/frontend-settings.md).

# Frontend Settings

{% hint style="info" %}
If **Admin Approval Required?** is off then customer can pay directly from website while adding new booking.&#x20;

Make sure you have enabled google places API in API settings and stored **"**[**Web API Key for google maps**](/explore-features/settings/api-settings.md)**"** in Driver Maps section of API settings.
{% endhint %}

> ### Any changes made in the frontend settings will be reflected on the frontend/website.

<figure><img src="/files/7LJ6MqnQKcsomrzYThrQ" alt=""><figcaption></figcaption></figure>

**o   About us**: Add About us information for the frontend or Website.

**-130 characters only**    &#x20;

**o   Contact Details**: Add Customer Support, Email & Contact Number.

**o   About Fleet**: Add fleet manager description.

**o   Language**: Choose the language to show from the frontend.

**o   FAQ Link**: Add FAQ Link.

**o   No.of Cities Serving**: Add the number of cities serving.  &#x20;

**o   No.of Vehicle Serving**: Add the number of vehicles serving.

**o   Add Hours to Book(Now):** Add Hours to book (Now).

**o   Cancellation:** Add cancellation terms in the form of a Web URL.

**o   Terms:** Add Terms and Conditions in the form of a Web URL.

**o   Privacy Policy:** Add Privacy Policy in the form of a Web URL.

**o  City Description:** Add the city description, it will be displayed on the About Us page on the frontend.

**o  Vehicle Description:** Add the city description, which will be displayed on the About Us page on the frontend.

**o  About City Image:** Add the city image in the specified dimensions.

**o About Vehicle Image:** Add the city image in the specified dimensions.

**o  Social Media Links:** Add Different Social Media Links.

**o  Footer menu link**: Add the Footer menu name with the link for the frontend setting  &#x20;

**o  Sign Up content**: Add the file, Title of content, and  subtitle for the frontend

#### **Admin Approval Required?**

This setting is required to display multiple payment options on the frontend or website; however, the admin must select the desired payment options from the payment settings.

<figure><img src="/files/jJDGewVFSPVYktyaSYrf" alt=""><figcaption><p>Admin panel>Frontend settings</p></figcaption></figure>

### Fleet Frontend - Payment options

The customer can make a payment by selecting the payment options.

<figure><img src="/files/Vls7WVkDprrgVlRcPZlu" alt=""><figcaption><p>Fleet fronted- customer login</p></figcaption></figure>

## For more details, read the Fleet Frontend Documentation!!!

[https://app.gitbook.com/o/WoXZFEs33ioROvY3SSIy/s/-LtZONQkdJdM-241mjfe/\~/changes/511/fleet-frontend-documentation](/fleet-frontend-documentation.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 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://fleetdocs.hyvikk.space/explore-features/settings/frontend-settings.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.
