AI Guide inspector

The AI Guide is the database-understanding layer used by Speak To Your Database. The inspector inside AI Guide lets you review, edit, and control how that understanding maps to your database schema.

What the AI Guide Inspector is for

After you run the analyzer with Analyze data, the inspector shows the generated schema documentation for connections, tables, and columns.

AI Guide is not only automatic analysis. It is also a review interface where users can improve descriptions and control table visibility.

What STYD already understands

Selecting a connection shows a What STYD already understandscard, with What STYD discovered here: the tables and columns analyzed, the kinds of tables found and the kinds of information found. It is made automatically and shown for information only.

Left tree selection

The left panel contains the AI Guide tree. Selecting an item updates the inspector on the right.

Connection
Shows high-level information for the selected database connection.
Table
Shows the table's description, its review status, and its visibility.
Column
Shows the column's description, its type, sample values, and flags.
Empty selection
Shows a placeholder until a connection, table, or column is selected.

Table inspector

When you select a table, Speak To Your Database displays information about how that table is understood by AI Guide.

Table name
The database table currently selected.
Description
One box: the AI's explanation of what the table represents, which owners and admins can correct. Saving your own text marks it Confirmed, and STYD then follows it as a rule.
Review status
AI draft, Draft, or Confirmed, shown next to the table name.
Visibility
Owners and admins can hide the table from chosen members.

Column inspector

When you select a column, the inspector shows the metadata Speak To Your Database uses to understand that column.

Column name
The selected database column.
Description
AI-drafted or user-edited explanation of what the column means, first in the inspector, with the same review status as a table.
Column type
The detected database type, such as text, integer, date, or boolean.
Sample values
Example values found in the column when available.
PII
Indicates whether the column may contain personal information. Set by the analysis; owners and admins can change it.
URL
Indicates whether the column appears to contain URLs. Set by the analysis; owners and admins can change it.
Soft delete
Owners and admins can mark a column that flags deleted, archived, or inactive rows.

Table visibility

AI Guide can also show table visibility controls. These controls help decide which tables are available to specific users.

Visible tables
Tables that Speak To Your Database can use when answering questions.
Hidden tables
Tables excluded from AI query planning for selected users or workspace rules.
User-specific access
Some workspaces can hide sensitive tables from specific members.
For Odoo workspaces, prefer Odoo permissions and the Odoo Bridge security model. Manual table hiding should be used as an additional safety layer, not as the primary Odoo permission system.

Who can edit AI Guide?

AI Guide permissions depend on the user role inside the workspace.

Owner
Can view and edit AI Guide descriptions, flags, and visibility settings.
Admin
Can view and edit AI Guide descriptions, flags, and visibility settings.
Member
Can view AI Guide information but cannot edit AI Guide settings.
Viewer
Cannot open Settings, so cannot open the AI Guide.

Why editing descriptions matters

AI-drafted descriptions are useful, but users often know the business meaning better than the database schema alone.

Improving table and column descriptions helps Speak To Your Database choose better tables, understand business vocabulary, and generate more accurate SQL. Your texts are kept when the analysis runs again.

Best practices

Review important tables first
Start with the tables most often used for reporting and operations.
Clarify business terms
Add descriptions for columns with unclear names or internal abbreviations.
Run the AI Guide analysis again after schema changes
If new columns are added, run the AI Guide analysis again so Speak To Your Database can detect and document them. Running the analysis again costs prompts, about 1 for every 500 columns (at least 1), and the price is shown before you confirm.
Be careful with sensitive tables
Use visibility controls to reduce access to tables that should not be used by everyone.