# Hide the Immuta Database in Databricks

{% hint style="info" %}
**Hiding the database does not disable access to it**

Queries can still be performed against tables in the `immuta` database using the Immuta-qualified table name (e.g., `immuta.my_schema_my_table`) regardless of whether or not this feature is enabled.
{% endhint %}

The `immuta` database on Immuta-enabled clusters allows Immuta to track Immuta-managed data sources separately from remote Databricks tables so that policies and other security features can be applied. However, Immuta supports raw tables in Databricks, so table-backed queries do not need to reference this database. When configuring a Databricks cluster, you can hide `immuta` from any calls to `SHOW DATABASES` so that users are not confused or misled by that database.

## Hide the `immuta` Database

When configuring a Databricks cluster, hide `immuta` by using the following environment variable in the [Spark cluster configuration](/2024.3/integrations/databricks-spark/reference-guides/configuration-settings/configuration.md):

```conf
IMMUTA_SPARK_SHOW_IMMUTA_DATABASE=false
```

Then, Immuta will not show this database when a `SHOW DATABASES` query is performed.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.immuta.com/2024.3/integrations/databricks-spark/how-to-guides/hide-immuta-database.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.