Table Visibility Governance

TL;DR

The Available for chat and charts / Unavailable for chat and charts boolean allows you to explicitly include or exclude specific tables from being accessed by the Al assistants or appearing in manual visualization workflows.

When to use it

Use this toggle to:

• Reduce Noise: Hide internal staging tables, lookup tables, or raw data that should not be used for reporting.

• Enhance Security: Prevent sensitive tables from being queried via Natural Language prompts in the Chat interface.

• Improve Al Accuracy: Limit the Al's scope to only relevant, "Enriched" tables to ensure higher quality query generation.

Core Functionality

When a table's visibility boolean is toggled:

• Al Chat: The table and its metadata are excluded from the Al's reasoning engine; it will not "see" the table when responding to user prompts.

• Manual Configuration: The table is hidden from the selection list when builders are manually creating charts or dashboards in the Library.

Prerequisites

• A connected and active database (PostgreSQL or Google BigQuery).

• Part of the database schema must have been previously analyzed to populate the table list.

Types and Properties

The visibility setting is managed within the Databases > [Selected Database] view.

Property	Type	Description
Available in Chat/Charts	Boolean	True (Enabled): Table is available for Al and manual use. False (Disabled): Table is hidden from all end-user interfaces.

Where to use it

• Database Management: Located in the table list view under the Databases section.

• Governance Phase: Use this during the final preparation of data before moving a project to production.

Constraints

• Default State: Newly analyzed tables are set to "Visible" by default following a schema refresh.

• Single Table Scope: Visibility must be toggled on a per-table basis.