> For the complete documentation index, see [llms.txt](https://docs.pipekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pipekit.io/using-pipekit/targets.md).

# Targets

See the clusters and namespaces your workspace holds, and open the runs in one of them.

{% hint style="warning" %}
Targets are part of [Access Control](https://docs.pipekit.io/concepts/access-control.md), which is in alpha. The `TARGETS` page appears only when your organization has an active RBAC policy.
{% endhint %}

A target is one cluster and one namespace that a [workspace](https://docs.pipekit.io/concepts/access-control.md#workspaces) holds. Your Org Admin gives targets to workspaces in the RBAC policy.

## Viewing your targets

1. Select a workspace in the workspace switcher.
2. Click `TARGETS` in the navigation bar.

The page lists every target your workspace holds, grouped by cluster. It shows no cluster or namespace that belongs to another workspace.

Each cluster shows its Pipekit Agent version and the same status chips as the [Clusters view](https://docs.pipekit.io/using-pipekit/clusters.md#clusters-view): `Agent` and `Metrics collector`. The chips show the current state and refresh every few seconds.

The page is read-only. To add or remove a target, ask your Org Admin to change the RBAC policy. If your workspace holds no target, the page shows `No targets in this workspace`.

## Opening the runs of a target

Click `View runs` next to a namespace. The Runs list opens, filtered to that cluster and that namespace.

`View runs` replaces the filters you last set on the Runs list, so an earlier filter does not hide runs from the result. Your [saved filters](https://docs.pipekit.io/using-pipekit/runs/filters.md#saving-a-filter) stay as they are.

An Org Admin with no role in the workspace sees its targets but no `View runs`, because the Runs list shows them none of the workspace's runs.

Pipekit matches each target to a cluster by name. If no cluster has that name, for example after the cluster was deleted or renamed, its namespaces show `Cluster not found` instead of `View runs`. Ask your Org Admin to update the cluster name in the RBAC policy.
