Reference
Marketplace
A governed catalogue of shareable agent and workflow templates. Installing one creates a draft in your workspace from its safe configuration — never a live agent, and never anyone's credentials, secrets or data.
What the marketplace is for
The marketplace is a shared, cross-tenant set of published templates that capture the configuration of an agent or workflow so it can be reused. Alongside the shared catalogue you also see your own workspace's draft and submitted contributions. Other tenants cannot see those until they are published.
A template is a
configuration snapshot only. It carries
behavioural settings and nothing else: an agent's objective,
instructions, declared risk and the tool slugs
it uses, or a workflow's ordered steps. It never
carries credentials, integration secrets or another tenant's
data.
Each template is one of two kinds: an agent template or a workflow template. Some are marked Built-in: library presets the platform seeds, with no authoring tenant.
Browsing and installing
The catalogue groups templates by category and lists published ones first. Filter by name (search) or by kind (agent or workflow). Open any card to see its detail page.
A template's detail shows its full configuration snapshot. For an agent that is the objective, instructions and declared risk; for a workflow it is the ordered steps, each naming the agent role it plays, that role's objective and the tools it declares. None of this is live data; it is configuration only.
The detail page also shows an install preview of the declared tools, split in two:
- Available, granted on install: tools that are already connected and permitted in your workspace. The new draft is assigned these.
- Suggested, not granted: tools the template declares that you cannot use yet. Installing surfaces them as suggestions but never grants them. Connect them yourself first.
Selecting Install confirms in a dialog, then creates a draft agent or workflow and takes you straight to its editor. The install never publishes or activates anything.
Install always produces a draft. A template can only copy in safe configuration. You still review the draft and publish it through the usual agent or workflow gate before it can run — nothing from the marketplace ever goes live by itself, and high-risk tools stay gated by your approval policy.
Submitting, publishing and archiving
To share one of your own published agents or active workflows, submit a configuration snapshot of it. Give it a name, description and category; the snapshot copies only safe behavioural config and tool slugs. The submitted template starts visible to your workspace alone, awaiting review.
An owner then publishes the submitted template into the shared catalogue, making it installable by every tenant. A published template is immutable. To change it later, submit a fresh version that supersedes it. To withdraw a template, archive it; it can no longer be installed, but drafts already installed from it are unaffected.
Permissions and governance
Each action is gated by role, mirroring the equivalent agent action:
- Browse and view published templates: any member who can view agents.
- Install (creates a draft): members who can create agents (operators upwards), since an install is exactly that.
- Submit a snapshot for review: members who can publish agent versions (admin or owner).
- Publish into the shared catalogue: owner only, a deliberately higher bar than submit so the submit → review → publish gate is real.
- Archive: a published row needs the owner bar; your own draft or submitted row needs the publish bar.
A non-published template is visible only to its author tenant. Any cross-tenant or non-author attempt to reach one is refused as not found, so its existence is never disclosed.
Things to watch
- Suggested tools are never silently granted. If a template's key capability is in the suggested list, connect that tool in your workspace before relying on the draft.
- Publishing freezes the snapshot. Treat the name, description, category and configuration as final at publish time. Corrections mean a new submission.
- Archiving only removes a template from the catalogue going forward; it does not touch anything already installed.
- Built-in templates have no authoring tenant and exist to seed the catalogue — you cannot edit them, only install from them.