Project AI Settings

All AI policies are stored and applied per Connection, not per Schema.

AI access, auto-apply, data transfer, and masking settings belong to each Connection.

Note: Database and Schema are Chat contexts, not policy boundaries.

Who can configure a Connection depends on its sharing scope and ownership.

Target	Manager	Notes
Public Connection	Project Owner	Shared policy for project members.
Private Connection	Connection owner	Applies only to the owner's private Connection.
Local project	User on this device	Managed locally with no sharing scope.

Configure these values for each Connection.

Setting	Behavior
AI access	Whether the Connection may be selected as an AI context.
Default Database and Schema	Initial Database and Schema for a new Chat.
Auto-apply schema changes	Whether DDL SQL cards run automatically.
Auto-apply data changes	Whether DML cards such as INSERT, UPDATE, and DELETE run automatically.
Allow data transfer	Stored policy allowing actual row results to be sent to an external provider.
Always mask sensitive data	Masks sensitive values before query results are sent to a provider.

The default target is only an initial selection for a new Chat.

It can be changed in the context picker before sending.
It is not a policy scope or permanent AI access boundary.
If any public Connection exists, changing the private Connection default target is disabled.
Without a default, the AI does not choose an arbitrary Connection.

NeoSQL evaluates the SQL type and target Connection policy together.

SQL type	Automatic execution	When auto-apply is off
SELECT	Runs after the response when a route exists	No separate auto-apply setting
DML	Runs when data auto-apply is on	Run button and confirmation
DDL	Runs when schema auto-apply is on	Run button and confirmation
UNKNOWN	Not executable	Not executable

Caution: Connection Read-only and Confirm protection and DDL permissions may require another confirmation or block execution.

Distinguish stored Connection policies from approval state in the current app runtime.

Allow data transfer is a stored project policy on the Connection.
Approve subsequent lookups persists across later requests and other Chats in the same project runtime.
It resets on project switch, app or page restart, or an automatic-approval failure.
Owners and local users can always choose it; regular members see it only when the Owner allows it.
Account projects can also apply the always-mask-sensitive-data policy.

Caution: Sensitive-data masking is unavailable in local projects. Review the actual values before approving transfer.