Resources

Team Server organizes activity into two trees:

Pipeline → Build → Violation
Deployment → Workload → Violation

Provider integrations discover pipelines/builds. Successfully reporting a manually started workload creates its host deployment and workload; Sensor startup alone does not. Recognized CI runs attach to their pipeline/build.

Browse and Export

Use resource-specific filters, search, sorting, columns, pagination, and CSV export. Table filters, search, ordering, and pagination persist in the URL. Page-level time windows, including Violations, are local; reselect them after opening a shared link.

CSV fields are quoted. Values beginning with optional whitespace then =, +, -, or @ receive a protective apostrophe to prevent spreadsheet formulas.

Open a row for metadata and relationships: builds/workloads show violations and runtime context; pipelines show policy assignment/history; deployments show Sensor/workloads.

Created is provider creation/start time used for ordering and freshness. Discovered is first storage time. Heartbeat-created builds temporarily use heartbeat receipt as Created until provider synchronization corrects it.

Operators and Administrators can use <create> in an unassigned pipeline’s Policy column to create and assign atomically. Creating from Policies alone does not assign. Policy Assignment filters Assigned/Unassigned independently of protection coverage. See Policy Management.

Resource Status

status_reconcile maintains activity:

Pipeline states use this precedence:

The stale window defaults to 14 days, configurable by Administrators under Pipeline Settings. See settings and recency.

Delete Resources

Deletion is permanent. Pipelines cascade to builds/violations; deployments to workloads/violations; Sensors to deployments, workloads, workload violations, and Sensor logs. Sensor deletion retains pipeline builds. Verify identity and export required records first.