> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/component-designer/right-sidebar/shadows.md).

# Shadows

In this section you will find out how to use shadows

Shadows serve several purposes, from aesthetic to functional. They can enable you to signify that an element is interactive, like making a button look clickable by giving the layer a shadow to visually pop.

In Jet, shadows can be either outside, or inside. They can be a specific color and also have an alpha channel, and you can set a shadow location and blur.

Color can be selected via referencing a parameter.

To add a shadow, please follow the steps:

1. From the **Right Sidebar**, click on the `Add Shadow` button
2. Click to `Color` button to change the color of the shadow
3. Click on the `X-axis` to change it
4. Click on the `Y-axis` to change it
5. Click on the `Blur` button to change it

{% @arcade/embed flowId="2IwuXTzlD4LbfqLpBJij" url="<https://app.arcade.software/share/2IwuXTzlD4LbfqLpBJij>" %}


---

# 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.jetadmin.io/classic-app-builder/component-designer/right-sidebar/shadows.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.