> ## Documentation Index
> Fetch the complete documentation index at: https://docs.joystream.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Visibility and discovery

> How a good agent spreads across an organization — visibility levels, the registry, and installations.

An agent built by one team is often useful to another. Visibility is how it becomes findable, and installation is how another team takes it up without taking it over.

## Visibility levels

```bash theme={null}
jstm agent visibility failed-payment-digest ORG_VISIBLE
```

| Level         | Who can find it                   |
| ------------- | --------------------------------- |
| `PRIVATE`     | The owning workspace only         |
| `ORG_VISIBLE` | Any workspace in the organization |
| `PUBLIC`      | Beyond the organization           |

Visibility controls discovery. It does not transfer ownership — the agent stays owned where it was built, and only its owning workspace can change it.

## The registry

Org-visible agents from sibling workspaces appear in the registry:

```bash theme={null}
jstm agent search invoice
jstm agent search --org acme-corp --json
```

## Installation

Installing gives you your own installation in your active workspace:

```bash theme={null}
jstm agent install acme-corp/finance/failed-payment-digest
jstm agent installations
```

An installation runs with **your** workspace's credentials, and carries its own schedule.

```mermaid theme={null}
flowchart LR
    A["Agent<br/>owned by Finance<br/>ORG_VISIBLE"] --> B["Installation<br/>in RevOps<br/>RevOps credentials"]
    A --> C["Installation<br/>in Support<br/>Support credentials"]
```

This separation is the point. One team owns and improves the capability. Other teams operate their own instance of it, against their own systems, without forking the definition or acquiring write access to it.

To remove your installation:

```bash theme={null}
jstm agent uninstall 8c41f2b9-… --yes
```

The original is untouched.

## Moving and copying

Visibility and installation are for reuse across teams. Two other operations change ownership:

| Command                            | Effect                                                       |
| ---------------------------------- | ------------------------------------------------------------ |
| `jstm agent move --to <workspace>` | Transfers ownership. The original workspace no longer has it |
| `jstm agent copy --to <workspace>` | Creates an independent copy the destination owns             |
| `jstm agent duplicate`             | Creates a variant in the same workspace                      |

Use `move` when an agent is in the wrong place — most often, when it was drafted in a personal workspace and should belong to the team that owns the work.

Use `copy` when two teams want to evolve the same starting point in different directions. Use install when they want the same capability, kept current by its owner.

## When to publish

Make an agent org-visible once it has earned production, not while it's still a draft. A discoverable agent that doesn't work costs the next team more time than it saves.

## Sharing with one person

Visibility is organization-wide discovery. To give one person access to one agent or one run, share it by email instead. See [Sharing](/features/sharing).

## See also

* [Organize and publish agents](/guides/organize-and-publish-agents) — walkthrough.
* [Manage agents](/cli/agent-manage) — full reference.