# Use list and bulk actions

> Source: https://docs.clonepartner.com/ui/bulk-and-list-actions/

Envoy resource lists use server-side search, filtering, sorting, and cursor pagination. Row actions affect one resource. Bulk actions apply the same operation to an explicitly selected scope.

## Refine the list first

Before selecting rows:

1. clear stale filters;
2. enter a specific search;
3. choose status or type filters;
4. sort by a useful field;
5. verify the result count.

Changing the filter changes the meaning of **all matching** selection.

## Understand selection scope

Selecting the header checkbox selects the visible page. When supported, Envoy then offers to select all rows matching the current server-side query.

These are different scopes:

- **selected rows** — explicit resource IDs;
- **current page** — rows loaded on screen;
- **all matching** — every server result for the captured search and filters, including unloaded pages.

The action dialog should state which scope will be affected and show the count. Stop if the count is unexpected.

## Common actions

Depending on resource type and permission, actions can include:

- export;
- archive or restore;
- enable or disable;
- delete;
- retry or stop;
- duplicate.

Archive is preferable when a definition or record may still be referenced or needs later recovery. Delete is appropriate only when the product confirms dependency handling and retention requirements permit it.

## Export selected definitions

Task exports create portable NDJSON definition bundles without connector secrets or run history. For cross-environment promotion, see [Move tasks and job templates between environments](/guides/task-and-job-bundles).

## Review destructive actions

For archive or delete:

1. read the confirmation text;
2. verify the resource type and total count;
3. confirm whether dependencies will block the action;
4. export definitions when rollback may require recreation;
5. apply the action;
6. refresh the list and record the result.

A bulk request can partially succeed. Review the result summary and retry only failed IDs after understanding the cause.

## Permissions and concurrency

Actions are role-gated on the server. Hiding a button is not the security boundary.

Another operator can edit or delete a resource between list selection and confirmation. Treat conflict or not-found responses as a signal to refresh and re-evaluate the selection rather than blindly resubmitting.