A scene saves the camera angle and layer visibility you are looking at right now, so you can jump straight back to it later. Use scenes to compare massing options side by side, step through project phases, or return to the exact framing you used for a client walkthrough, without resetting pan, zoom, and layer toggles by hand every time.
What does a scene save?
Each scene stores:
A map camera position (zoom, bearing, pitch, and center)
A small preview image of the map, captured at the moment you saved the scene
The visibility of every layer, and which layer is active
The scenarios that were visible
Whether the map was in 2D, 2.5D, or 3D view
The sun position, based on the date and time set for the project
A scene does not save any annotations or markup drawn on the map. It only captures the camera and layer state.
How are scenes different from views?
Scenes and views both save a camera position and a layer state, and both live in their own panel. Views are built for presenting your project: they support a compare-views slider, and they drop directly into the Presentation layout and the Report Builder. Scenes are built for your own navigation while you work. Click a scene to fly back to it as you move between areas of a site or between design options.
See What is a view? to learn about the Views panel.
Where scenes live
Scenes live in their own panel, the same way Layers and Properties do. It is not part of any default layout, so add it the first time through the panel picker. Then you can capture your first scene.
Who can create and edit scenes
Scenes belong to the project, not to any one person. Everyone with access to the project sees the same list of scenes.
Anyone with edit access to the project can create, update, rename, delete, and reorder scenes. Anyone with view-only or guest access can open and fly to existing scenes. They cannot create, edit, or delete them.