# Run Schema Monitoring and Column Detection Jobs

## Manually Run Schema Monitoring Jobs

### Manually Run Schema Monitoring Job for All Data Sources

**Requirement:** Immuta permission `USER_ADMIN`

You can manually run a schema monitoring job globally using the [`/dataSource/detectRemoteChanges` endpoint of the Immuta API](https://documentation.immuta.com/2024.2/developer-guides/api-intro/immuta-v1-api/data-sources#trigger-schema-monitoring-jobs) with an empty payload.

### Manually Run Schema Monitoring Job as a Data Owner

You can manually run a schema monitoring job for all data sources that you own using the [`/dataSource/detectRemoteChanges` endpoint of the Immuta API](https://documentation.immuta.com/2024.2/developer-guides/api-intro/immuta-v1-api/data-sources#trigger-schema-monitoring-jobs) with a payload containing the hostname for your data sources or their individual IDs.

### Manually Run Schema Monitoring Job as a Data User

You can manually run a schema monitoring job for data sources you are subscribed to using the [`/dataSource/detectRemoteChanges` endpoint of the Immuta API](https://documentation.immuta.com/2024.2/developer-guides/api-intro/immuta-v1-api/data-sources#trigger-schema-monitoring-jobs) with a payload containing the hostname for your data source and the table name or data source ID.

## Manually Run a Column Detection Job

1. Navigate to the data source overview page.
2. Click on the **health check icon**.
3. Scroll to Column Detection, and click **Trigger Detection**.