Skip to main content
Every Data App has one owner, whose data connections run it. This page covers what that means for everyone else, and how apps are shared across a workspace. It applies to Next Gen and Classic apps alike, except that only the owner can refresh a Classic app.

Ownership and permissions

Every Data App has a single owner — initially the person who created it. When a Data App refreshes, its pipeline runs using the owner’s data connections, no matter who triggered the refresh or whether it ran on a schedule. Because the owner’s credentials execute the app’s code, changing the app is reserved for the owner:
  • Owner: everything — canvas and chat editing, publishing, refreshing any version, restoring versions, settings, editors, delete.
  • Editors (added under Settings > Editors), workspace Developers, and org admins: trigger Refresh now (the run still executes under the owner’s account), change settings and the schedule, publish a built version, and inspect the app’s drafts — see below. Developers and admins can also manage the editor list and delete the app.
  • Everyone else in the workspace: view the published app, star it, clone it, and ask questions in chat — provided they can discover it (see Publishing) or have the direct URL.
Private apps narrow this list.

Inspecting without editing

Where the owner sees the Edit pencil, editors (and Developers/admins) see a History & source icon instead. It opens the same editor layout read-only: browse the version history, read the source code, and see what changed in each version. The header reads Read only · owned by followed by the owner’s name. You can’t change anything from there, but the header offers Claim ownership when you’re eligible, and Clone is in the ⋯ menu.

Claiming ownership

If you need to change an app you don’t own, you have two options:
  • Clone it (⋯ menu) to get your own copy with an independent history.
  • Claim ownership (⋯ menu, or the shortcut in the read-only header) to take the app over in place. Claiming is available to the app’s editors, workspace Developers, and org admins.
Claiming makes you the owner: starting with the next refresh — including any existing schedule, which keeps running — the app’s pipeline runs using your data connections, including queries you didn’t write. A confirmation dialog spells this out before you claim. The previous owner stays on the app as an editor, so they keep visibility into its versions and settings. Ownership is never transferred to someone by someone else — the person whose credentials will run the app must claim it themselves.

Publishing and discoverability

Publishing a version (see Draft and publish) controls what content viewers see. Separately, publishing the app controls who can find it in the workspace. By default, a new Data App is only visible to its owner and to Developers (who can see everything). To make it discoverable by Explorers and Viewers, toggle the Publish icon in the top bar or on the listing page. When you publish, you also choose a release mode. This controls discoverability, not access. Anyone in the workspace can still open a Data App if they have the direct URL — publishing just determines whether it appears in the listing for Explorers and Viewers. The exception is an unpublished private app, which only its owner and editors can open.

Listing page tabs

The Data Apps listing organizes apps into tabs: Viewers see only the Starred and Published tabs.

Starring and cloning

Starring — Click the star icon on any Data App to add it to your Starred section in the sidebar. Starred Data Apps also float to the top of the listing page. Cloning — Choose Clone from the ⋯ menu to create a copy of any Data App you can view. Anyone with a role in the workspace can clone; in organizations that restrict what Viewers can create, Viewers can’t. The clone starts with the same pipeline and output but has independent version history — and you own the copy.

Private apps

An app becomes private automatically when its pipeline uses a private MCP connection. There’s no toggle, and it’s one-way: the app stays private even if it later stops using that connection. While a private app is unpublished, it shows a Private lock badge next to its title and in the listing. Its tooltip reads: “Uses a private connection — hidden from your workspace unless you publish it.” A private app differs from a regular one in two ways:
  • Only the owner and editors can find or open it, even with the direct URL, until it’s published to the workspace. Publishing shares it like any other app and removes the badge.
  • Developers get no special access, even after it’s published. They can’t inspect drafts, change settings, manage editors, delete the app, or claim it. Only editors the owner added explicitly can claim it.
An unpublished private app also can’t post to Slack.