> For the complete documentation index, see [llms.txt](https://dg-market.gitbook.io/dg-live/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dg-market.gitbook.io/dg-live/business-manager/scenes.md).

# Scenes

### Overview

Scenes allow you to manage the appearance and layout of your metaverse NFT store. This section covers various aspects of scene management, including scene panorama, scheduling, groups, sharing, and deletion.

#### Scene Panorama

1. Click on the **Scenes** tab in the Business Manager dashboard.
2. Use the scene panorama to view all your existing banners and variables for a specific scene.

#### Scene Scheduling

1. Schedule elements on your scene to react at specific times or on specific days.

#### Scene Groups

1. Organize scenes components into groups for easier management.
2. Retrieve information of a specific group of elements on scenes at once with a dedicated endpoint.

#### Sharing a Scene

1. Share your scenes with others and give them permissions to manage that scene

#### Deleting a Scene

1. Permanently remove a scene by clicking the **Delete** button within the scene's settings.

### Why are scenes useful?

Scenes are essential for creating an engaging and visually appealing metaverse NFT store. They allow you to showcase your items in an organized and aesthetically pleasing manner, making it easier for potential customers to browse and make purchases. Additionally, scenes enable you to adapt your store's appearance to align with promotions, events, or other marketing initiatives.


---

# 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://dg-market.gitbook.io/dg-live/business-manager/scenes.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.