marketplace entitlement (see Availability).
What you can install today
The catalog is curated by Dippr. It holds five kinds of listing, and each has its own verb:
You cannot publish your own listings yet.
What a listing shows
Select a listing to open its page. Everything an install will do is stated there before you commit to it:
Use the filters on the Browse tab to narrow the catalog by type, publisher tier or the data source
you use, or type in the search box to match a listing’s name, summary or publisher.
Publisher tiers
The tier states the support commitment behind a listing, in words, next to the publisher’s name:What an install does, and does not do
- It copies the listing’s definitions into your tenant as drafts you own. They appear on the Semantic layer tab for their type, in the state Draft, and nothing is served to agents or metric queries until you propose and certify them.
- It reads none of your data. A semantic-model listing asks for a catalog and a schema so the drafts are bound to your tables; the install stores those names and nothing else.
- It records the install on the Installed tab, with the version, who installed it and its status, so you can see what came from the Marketplace.
- Updates never apply on their own. A newer version of a listing installs as a new set of drafts; the drafts you already hold are not changed or replaced.
- Removing an install forgets the record only. The drafts stay where they are.
Availability
The Marketplace is included in the standard tenant bundle through themarketplace entitlement. A platform administrator can disable it for a
tenant. In a tenant without it:
- The Marketplace entry is not in the sidebar.
- Opening a direct link to the page shows “The Marketplace is not included in this workspace. Ask your platform administrator to enable it.”
- Every Marketplace call is refused with
this tenant does not include the "marketplace" entitlement.
semantic_layer entitlement, which is in the standard bundle, because the
drafts land in the semantic layer. Without it an install ends as Failed with the semantic layer’s
refusal as the reason.
Adding a pipeline needs the pipelines entitlement, also included in the standard bundle. In a tenant
without it the pipeline’s listing page says
“Adding it needs Pipelines, which this workspace does not include.” and Add to workspace is disabled. An agent listing needs the agents entitlement the same
way: without it the page says “Adding it needs Agents, which this workspace does not include.”
Limits
- You use the Marketplace from the console. An API key or
dipcannot browse, install or add listings. - The catalog is curated by Dippr. You cannot publish your own listings yet.
- A listing installs once per version in a tenant. Installing the same version again is refused; remove the record first if you want a fresh copy.
- Installing never certifies anything, and never changes a draft, proposed or certified definition you already hold.
Related
Install a listing
The two-step install, the Installed tab, removing a record and what a failed install means.
Semantic layer overview
Where the drafts land, and how a draft becomes certified.
Entitlements
The
marketplace flag and the rest of the per-tenant bundle.Roles and permissions matrix
Who can browse the Marketplace and who can install from it.