## Preflight checks for Workday Prism Analytics

URL: https://docs.atlan.com/apps/connectors/business-intelligence/workday-prism-analytics/references/preflight-checks-for-workday-prism-analytics

> Before running the Workday Prism Analytics crawler, Atlan checks that it can reach your tenant, that Prism Analytics is licensed, and that the configured account has permission to read tables and Data Change Tasks.

Before [running the Workday Prism Analytics crawler](https://docs.atlan.com/llms/connectors/workday-prism-analytics/crawl-workday-prism-analytics/llms.txt), you can run [preflight checks](https://docs.atlan.com/llms/catalog/connector-capabilities/what-are-preflight-checks/llms.txt) to perform the necessary technical validations. The following preflight checks are completed, in this order:

## Reachability

Atlan requests an access token from your Workday tenant's OAuth 2.0 token endpoint, using the Client ID, Client Secret, Refresh Token, and Base URL you provided.

✅ `Check successful` if Atlan obtains an access token.

❌ `Check failed` if the token endpoint can't be reached, or the credentials are rejected. Since this same token request also gates the _Tenant version_ check, a failure here fails that check too.

## Tenant version

Confirms that the token response resolves to a valid Workday tenant.

✅ `Check successful` if the access token request in the _Reachability_ check succeeds.

❌ `Check failed` if Atlan can't obtain an access token—see _Reachability_ earlier on this page.

## Prism licensed

Atlan calls `GET /tables?limit=1` against your tenant.

✅ `Check successful` if the call returns HTTP `200`.

❌ `Check failed for HTTP <code>` if the call fails—most commonly because Prism Analytics isn't licensed for this tenant, or because your API client's [scope](https://docs.atlan.com/llms/connectors/workday-prism-analytics/set-up-workday-prism-analytics/llms.txt) doesn't include Prism Analytics.

## Permission tables

Uses the result of the same `GET /tables?limit=1` call as _Prism licensed_: a `200` response confirms both that Prism is licensed **and** that the Integration System User has `Get` access to the Domain Security Policies gating Prism tables.

✅ `Check successful` if the call returns HTTP `200`.

❌ `Check failed for HTTP <code>` if the call fails—most commonly a missing grant on the [Prism Access Security Group](https://docs.atlan.com/llms/connectors/workday-prism-analytics/set-up-workday-prism-analytics/llms.txt).

## Permission data changes

Atlan calls `GET /dataChanges?limit=1` against your tenant.

✅ `Check successful` if the call returns HTTP `200`.

❌ `Check failed for HTTP <code>` if the call fails—most commonly a missing grant on the [Integration System Security Group](https://docs.atlan.com/llms/connectors/workday-prism-analytics/set-up-workday-prism-analytics/llms.txt) for Data Change Task-related Domain Security Policies.

---