For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 AI 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 AI Accuracy: Limit the AI's scope to tables that are analyzed and confirmed (with solid metadata) so query generation stays relevant.

Core Functionality

When a table's visibility boolean is toggled:

  • AI Chat: The table and its metadata are excluded from the AI'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 AI 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 after analysis: Tables included in an AI analysis run are set to Available for chat and charts when the analysis processes them. You can still turn visibility off afterward for tables that should stay hidden.

  • Schema refresh: Refreshing the schema discovers structure; it does not by itself decide which tables should stay available — use analysis and this toggle together.

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

Last updated

Was this helpful?