Approval and Audit

1. Operation Approval

1.1 Why Approval Is Sometimes Required

Reading and changing data have different effects. The system distinguishes four categories:

Category	Examples	Typical handling
READ	Query data or inspect table structures	Runs automatically by default
WRITE	Create tables, insert data, or change schemas	Runs after approval; conversation policies may allow automatic approval
DANGER	Delete data or drop tables	Requires approval and a confirmation word every time
FORBIDDEN	Grant permissions, shut down the database, or concatenate multiple statements	Rejected; approval cannot override the restriction

The actual category depends on the system's assessment of the complete operation. SQL is the database command language, usually generated by the assistant and displayed on the approval card.

1.2 Handle an Approval Card

1. Read the target database, objects, and operation carefully.
2. Ask a database administrator if you do not understand the effect.
3. Click Approve Execution only when the operation is authorized. Otherwise, select Reject Execution and optionally give a reason.
4. Check the final execution result. Successful approval does not mean the database operation succeeded.

Who approves:

Situation	Requirement
Ordinary writes	Regular users can approve operations in their own conversations
Dangerous operations	An authorized database or platform administrator must approve
Writes subject to four-eyes approval	An authorized person other than the requester must approve; the requester can only withdraw the request

Automatic approval:

• Automatically approve similar operations in this conversation reduces approval prompts for similar writes. Check the scope before enabling it. It does not permit dangerous operations automatically.
• If the platform prohibits automatic approval of writes within a conversation, the switch is hidden and every ordinary write requires approval.
• Writes subject to four-eyes approval cannot have approval remembered or granted automatically. Follow the rules shown on the card.

Note: Do not switch conversations or rewrite instructions to bypass a rejection. Follow any additional change-approval requirements of your organization.

1.3 Approvals for Forecasting and External Tools

• Data sent: Forecasting sends the time and target columns from query results; external tools send invocation arguments. These operations usually require approval even if read-only queries are allowed to run automatically.
• Before approving: Check the data, destination service, and business authorization.
• Automatic approval within a conversation: Selecting Automatically approve similar operations in this conversation can avoid repeated cards for later forecasts or calls to the same external tool. Dangerous database operations always require individual approval.
• After execution: Data Egress records help review calls outside the platform. Check the actual result after approval; authorization is not proof of successful execution. See Common Messages for error handling.

2. Database Administrators: Approval and Audit

2.1 Handle Pending Operations

After signing in, open Pending Approvals (All Conversations) on the right side of Conversation Workbench.

1. Check the original question, SQL, target connection, and time remaining.
2. Confirm the target objects, scope of impact, and any required backup or change authorization.
3. For dangerous operations, enter the confirmation word shown on the card, such as DROP, then approve.
4. Reject operations you do not accept and explain why.
5. Check execution status and, if necessary, verify the result with read-only queries.

• Validity: The default waiting period is 10 minutes. An approval cannot continue after timeout, user cancellation, conversation deletion, or a service restart.
• Information scope: Global approvals show the necessary details without granting access to another user's full conversation.
• Four-eyes approval: Operations you request must be handled by another authorized approver.
• Notifications: Email and instant messaging notifications are currently unavailable. Monitor the pending approvals panel and agree on a handling time with the requester.

2.2 Query and Export Audits

1. Open Audit Center and select Execution Audit or Approval Records.
2. Filter by time, user, risk level, status, database connection, or SQL keyword.
3. Check who requested and approved the operation, which connection was used, and whether execution succeeded.
4. Export the current filtered results as CSV when needed. The file can be opened in Excel.

Time range: Queries cover the last seven days by default. A single query can span at most 366 days. The default audit retention is 180 days.

Storage: Exported files contain user and operation information and must be stored with appropriate access controls.