Skip to content
Docs

Data apps

A data app is an interactive dashboard backed by live queries. Unlike a static chart, it re-runs against your warehouse when someone opens it or changes a filter, so it stays current instead of freezing the numbers at the moment it was built.

Prerequisites

  • A data source bound to the workspace, since the app queries it live.

  • Editor role to create or edit; Viewers can open and use existing apps.

Creating one

Ask for it in a conversation:

“Build a dashboard of spend and ROAS by channel for the last 90 days, with a filter for country.”

Adverity Atlas plans the layout, writes the queries, applies your brand design, and returns a working app. Behind the scenes it runs a planner then a designer, so what comes back is a composed dashboard, not a single chart.

How the data is wired

A data app does not run arbitrary SQL when someone uses it. It declares a fixed set of named queries with typed parameters, and the filters in the UI feed those parameters. This is what makes it safe to share, a viewer changes a country filter, not the query itself.

  • Named queries: Each chart or metric is backed by a defined query, not free-form SQL entered at view time

  • Typed parameters: Filters map to declared parameters, so inputs are validated before they reach the warehouse

  • Bound data sources: An app can only query sources bound to its workspace; it cannot reach across into another workspace’s data

Editing

Refine an app by asking in chat, no rebuilding from scratch:

  • Change a visual: “Make the spend chart a line chart”, “sort by ROAS descending”

  • Adjust the data: Update a query or its parameters when the question changes

  • Add or remove: Panels, filters, and metrics

Each edit produces a new version. Anyone viewing a live copy picks up the new version on refresh.

Changing one element

When an app has several similar charts, point at the one you mean instead of describing it.

  1. With the app open in the panel beside the conversation, click Select an element to edit in the panel header.

  2. Click an element of the app, for example a chart, KPI, table or section. A prompt box opens next to it with the element’s name.

  3. To include more elements, Shift-click them. You can select up to three.

  4. Type the change in “Ask for a change…” and press Enter, or click Send. Adverity Atlas changes the selected elements.

To write a longer request instead, click Add to chat. The selected elements move into the main message box, and you finish the message there. Done selecting leaves select mode.

The Select an element to edit button appears only for members who can create artifacts (Editor and above).

Activity log

The Activity log shows what a data app is doing as you use it: each query and saved-data call as one line with its result and timing, alongside app events and any errors the app hits. It is the first place to look when a panel stays empty or a filter does not seem to apply.

  1. Open the log with the Activity log button in the artifact panel in Chat, or in the header of the full-screen view.

  2. Narrow it with the filters: All, Queries, Storage, Events, or Errors.

  3. Click a line to see its details. Click it again to collapse it.

  4. Click Clear to empty the log.

Note

In the full-screen view, the Activity log button appears only for people who can edit the app.

Rearranging the panels

Some data apps lay their panels out as a dashboard grid you can rearrange yourself, by dragging panels around and resizing them. Where one does, an Arrange button appears in the app’s header.

  1. Click Arrange. The panels become draggable and resizable, and the button changes to Done.

  2. Move and resize panels. Each change saves as you drop it, so there is no separate save step.

  3. Click Done to leave arranging mode.

Two toggles sit beside the button while you are arranging:

Control

What it does

Everyone

Saves the arrangement as the shared default that everyone opening the app sees. Available to people who can edit the app

Just me

Saves a personal arrangement only you see, leaving the shared one alone

Reset

Clears the layer you are editing. Clearing your personal layout falls back to the shared default; clearing the shared one falls back to the layout the app was built with

Your own arrangement wins over the shared default, which in turn wins over the layout the app shipped with, so a personal layout is never overwritten by someone else saving a shared one.

Note

Arrange appears only on apps built as a dashboard grid. Anyone signed in who can open the app can save a personal arrangement, including someone it was shared with read-only; only people who can edit the app get the Everyone option. A visitor arriving on an anonymous public link sees the shared arrangement and has no controls at all.

Sharing

Data apps are the format sharing was built for: a colleague opens the link, uses the filters, and sees live data, without touching Chat or holding an Adverity Atlas seat, depending on how you share it. See Sharing for viewer versus collaborator access.

One thing is specific to data apps. Because the app queries live, a public link needs an identity to run those queries as, so publishing provisions a service account for it automatically. You do not pick one, and deactivating it later is how you cut a published app off from data. See Sharing for how that works.

Tip

Because the data is live, a data app is the right choice for something people return to, a weekly performance view. For a snapshot of how things looked at one moment, a report or presentation fits better.

What’s next?

Was this page helpful?