> ## Documentation Index
> Fetch the complete documentation index at: https://docs.validio.io/llms.txt
> Use this file to discover all available pages before exploring further.

# About Credentials

> Credentials store the authentication details that connect Validio to your data warehouses, BI tools, and integrations.

Credentials store the authentication details that connect Validio to your data warehouses, business intelligence tools, and other integrations.

![The Credentials page listing existing credentials with their type and creation date](https://mintcdn.com/validio/h4NQPs1kJwlpB1Yj/images/docs/credentials/credentials-overview.png?fit=max\&auto=format\&n=h4NQPs1kJwlpB1Yj\&q=85\&s=99db5d5aaa0e95ae43ebbd26812fc202)

Credentials page with table of existing credentials

Credentials connect Validio to the data that you want to monitor. For data warehouses, the credentials store the authorizations details for the user or service accounts you will use to connect Validio to data sources and other integrations. For business intelligence tools, credentials are used to populate catalog assets and lineage graphs.

## How credentials work

Most credential configurations require a set of parameters, such as a username, password, and host name of a service account that you will use to access the data. For credentials that will connect to a warehouse, you might also need to specify the default database where the data is stored or the role used to access the data source.

After you create a credential, Validio will connect to the service account and automatically start to collect information, such as metadata and lineage. If the credential is used for catalog and schema checks, this information populates the catalog and lineage pages with assets. You can convert assets discovered from data source credentials to sources for Validio to monitor and validate.

For more information, see [Managing Credentials](https://docs.validio.io/v10.0/docs/credentials/managing-credentials.md).

> [!WARNING]
>
> **Credential Permission Requirements**
>
> Validio Credentials **require** `VIEWER` access rights when connecting to sources to read and access data. Admins must ensure that they do not provide `EDITOR` access rights to their credentials.

## Credential types

The following is a list of credential types. You can find instructions to configure each credential on their dedicated integration pages.

### BI tools credentials

Connect Validio to Business Intelligence Tools.

| Credential Type | Supported Integrations |
| :- | :- |
| Looker | [Looker](https://docs.validio.io/v10.0/docs/integrations/business-intelligence-tools/looker.md) |
| Omni | [Omni](https://docs.validio.io/v10.0/docs/integrations/business-intelligence-tools/omni.md) |
| Power BI | [Power BI](https://docs.validio.io/v10.0/docs/integrations/business-intelligence-tools/power-bi.md) |
| Sigma | [Sigma](https://docs.validio.io/v10.0/docs/integrations/business-intelligence-tools/sigma.md) |
| Tableau Connected App | [Tableau](https://docs.validio.io/v10.0/docs/integrations/business-intelligence-tools/tableau.md) |
| Tableau Personal Access Token | [Tableau](https://docs.validio.io/v10.0/docs/integrations/business-intelligence-tools/tableau.md) |

### Data catalog solutions

Connect Validio with data catalog solutions.

| Credential Type | Supported Integrations |
| :- | :- |
| Atlan | [Atlan](https://docs.validio.io/v10.0/docs/integrations/data-catalog-solutions/atlan.md) |

### Data source credentials

Connect Validio to data sources, such as warehouses, streams, transformation tools, and transactional databases.

| Credential Type | Supported Integrations |
| :- | :- |
| AWS | [Kinesis](https://docs.validio.io/v10.0/docs/integrations/data-streams/kinesis.md) |
| AWS Athena | [Athena](https://docs.validio.io/v10.0/docs/integrations/query-engine-sources/athena.md) |
| AWS Redshift | [AWS Redshift](https://docs.validio.io/v10.0/docs/integrations/data-warehouses/redshift.md) |
| Azure Synapse Entra ID | [Azure Synapse](https://docs.validio.io/v10.0/docs/integrations/data-warehouses/azure-synapse.md) |
| Azure Synapse SQL | [Azure Synapse](https://docs.validio.io/v10.0/docs/integrations/data-warehouses/azure-synapse.md) |
| ClickHouse | [ClickHouse](https://docs.validio.io/v10.0/docs/integrations/data-warehouses/clickhouse.md) |
| Databricks | [Databricks](https://docs.validio.io/v10.0/docs/integrations/data-warehouses/databricks.md) |
| dbt Cloud | [dbt Cloud](https://docs.validio.io/v10.0/docs/integrations/data-transformation/dbt-cloud.md) |
| dbt Core | [dbt Core](https://docs.validio.io/v10.0/docs/integrations/data-transformation/dbt-core.md) |
| Google Cloud Platform (GCP) | [Google BigQuery](https://docs.validio.io/v10.0/docs/integrations/data-warehouses/bigquery.md), [Pub/Sub](https://docs.validio.io/v10.0/docs/integrations/data-streams/pubsub.md) |
| Kafka SASL SSL Plain | [Kafka](https://docs.validio.io/v10.0/docs/integrations/data-streams/kafka.md) |
| Kafka SSL | [Kafka](https://docs.validio.io/v10.0/docs/integrations/data-streams/kafka.md) |
| Microsoft SQL Server | [SQL Server](https://docs.validio.io/v10.0/docs/integrations/transactional-databases/sql-server.md) |
| Oracle | [Oracle](https://docs.validio.io/v10.0/docs/integrations/transactional-databases/oracle.md) |
| PostgreSQL | [PostgreSQL](https://docs.validio.io/v10.0/docs/integrations/transactional-databases/postgresql.md) |
| Snowflake | [Snowflake](https://docs.validio.io/v10.0/docs/integrations/data-warehouses/snowflake.md) |
| Teradata | [Teradata](https://docs.validio.io/v10.0/docs/integrations/data-warehouses/teradata.md) |

### LLM credentials

Connect Validio to Large Language Model (LLM) providers to enable AI Features, such as [Generating SQL in Validators and Filters](https://docs.validio.io/v10.0/docs/ai-features/generating-sql-validators-and-filters.md).

| Credential Type | Supported Integrations |
| :- | :- |
| Amazon Bedrock | [Amazon Bedrock](https://docs.validio.io/v10.0/docs/integrations/llm-credentials/amazon-bedrock.md) |
| Anthropic | [Anthropic](https://docs.validio.io/v10.0/docs/integrations/llm-credentials/anthropic.md) |
| Gemini Enterprise | [Gemini Enterprise](https://docs.validio.io/v10.0/docs/integrations/llm-credentials/gemini-enterprise.md) |
| Microsoft Foundry | [Microsoft Foundry](https://docs.validio.io/v10.0/docs/integrations/llm-credentials/microsoft-foundry.md) |
| OpenAI | [OpenAI](https://docs.validio.io/v10.0/docs/integrations/llm-credentials/openai.md) |

## Best practices

When setting up credentials for your organization, you can use **Namespaces** to control access (view and edit privileges) to the credentials. The following are general guidelines and recommendations.

* **Visibility into global Catalog and Lineage views:** Configure a single credential with “Use for catalog and schema checks” enabled to populate your global catalog and lineage views so that it is visible for all of your organization’s users in Validio. This credential should be assigned to a namespace that only the admin has access to and it should not be used for creating new sources.
* **Dedicated Namespaces with limited visibility and permissions:** For individual teams and business units, create dedicated namespaces to ensure that the users and teams with Editor access to the namespace can only create sources and run debug queries off of the credentials in the namespace. You do not need to enable cataloging or schema checks on these credentials if you have enabled a global credential.
* **Distinguish between Editor and Viewer access:** Ensure that teams and users have access to what they need to see. Different teams can configure and manage their own resources separate from other teams.