Academy
7. Sharing with Your Team and Managing Instances
Share a Live Artifact with team members so each gets their own instance, inputs, history and billing, while you retain the reference workflow.
When you share a Live Artifact with your team, you are not handing over your workflow file — you are publishing a reference recipe. Each team member who receives it gets their own independent instance: their own input form, their own run history, their own deliverables folder, and their own billing. Your original artifact stays untouched as the canonical version. This means you can iterate on the reference without breaking anyone's running copy, and each colleague's runs are charged to their own credit balance, not yours.
The sharing mechanism lives in the marketplace, which serves two purposes: (1) organization-level publishing, where artifacts you or your colleagues create are listed for anyone in the org to install, and (2) OUPI-published artifacts — pre-built workflows maintained by the platform. When a team member installs an artifact from the marketplace, they can also derive it — creating a variant they customize (different inputs, adjusted logic) while the lineage back to your original is preserved. This install-and-derive model lets teams standardize processes without locking anyone into a rigid template.
Every instance keeps a full, isolated history: inputs supplied, deliverables produced, cost in credits, and the verification verdict for each run. This is critical for accountability in a team setting — you can audit who ran what, when, with which data, and at what cost, without any cross-contamination between members' records. Deliverables are stored in each member's own file space under the artifact's folder, accessible from the run page.
Before sharing, review your artifact's declared inputs carefully. Clear input names, types, required/optional flags, and allowed choices act as built-in documentation for your team. A well-declared input form means fewer clarification questions and fewer failed runs from bad data.
If a colleague needs a slightly different version — say, an extra input field or a different output format — encourage them to derive the artifact rather than building from scratch. Derivation preserves the link to your reference workflow, making it easier to propagate improvements later.
Sharing a Live Artifact is fundamentally different from sharing a Studio scheduled task. A scheduled task repeats one specific project with fixed parameters. A Live Artifact is parameterized and multi-tenant by design: each team member fills their own inputs, attaches their own schedules or triggers (a webhook, a watcher, a recurring schedule), and operates independently. This is why Live Artifacts are the right vehicle for team-wide process standardization — they scale across people without multiplying your maintenance burden.
Go to the marketplace (dashboard.user.live-artifacts.marketplace). Find one of your own Live Artifacts or install an organization artifact. Share it with a colleague, then ask them to open their instance and confirm they see an empty input form, no run history, and that a test run is billed to their account — not yours.
Sharing a Live Artifact gives each team member an independent instance with their own inputs, history, deliverables, and billing — your reference workflow stays intact. The marketplace is the hub for publishing, installing, and deriving artifacts across your organization. Well-declared inputs reduce friction; derivation lets colleagues customize without breaking lineage. Unlike a repeated Studio task, a Live Artifact is built for multi-user, parameterized operation at scale.