> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/settings/customizations.md).

# Customizations

CARTO provides robust customization options that help you adapt the platform to align perfectly with your brand and organizational needs. These include configuring your organization’s basemaps and tailoring the appearance and branding of the platform.

**Configuring your basemaps**

In this section, you have the flexibility to manage the types of basemaps available in Builder, including default CARTO basemaps, Google Maps basemaps, and custom basemaps. You also have the option to upload your own custom basemaps in supported formats, ensuring your maps precisely meet your organizational specifications.[ Discover more about basemap configurations here](/carto-user-manual/settings/customizations/configuring-your-organization-basemaps.md).

**Customizing your branding**

For customers aiming to make their brand more visible throughout the product, you can modify the appearance of both Workspace and Builder. This level of customization minimizes the presence of the CARTO brand to only basemap attributions, rendering publicly shared maps neutral for seamless integration into your own portals and websites. [Explore more about branding customization here.](/carto-user-manual/settings/customizations/customizing-appearance-and-branding.md)

**Configuring custom markers**

Manage a shared set of custom point markers for your whole organization from a single place. Admins import icons once, and Editors pick from them when styling point layers in Builder instead of re-uploading the same files into every map. [Learn more about custom markers here](/carto-user-manual/settings/customizations/configuring-custom-markers.md).

<figure><img src="/files/Rma1ohISVamVwxC846xg" alt=""><figcaption></figcaption></figure>


---

# 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.carto.com/carto-user-manual/settings/customizations.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.