Why your SQL client needs policies

Catch the obvious mistake first

An accidental write without WHERE is easy to spot after the damage and easy to miss while moving fast. Studio includes default blocks for UPDATE and DELETE without an effective WHERE clause, plus DROP and TRUNCATE.

DELETE FROM orders;
-- Blocked by the default DELETE-without-WHERE policy

Add limits that match your work

Personal policies can block a table or schema, cap returned rows, stop long queries, and restrict writes to a time window. Safe mode on a connection can block all writes. These controls are useful alongside least-privilege database credentials and backups.

SELECT id, customer_id, total
FROM orders
WHERE created_at >= '2026-09-01'
LIMIT 100;

SELECT id, total, status
FROM orders
WHERE customer_id = 1001
LIMIT 100;

When the rules must apply to everyone

Rowset Teams adds role-based connection access, shared policies, approvals, masking, row filters and a centralized activity trail. The team path is for organizations that need a consistent decision about who can access a database and what they can see.

Studio's personal policies remain local to one person's workspace. Teams is commercial and self-hosted; shared row backups and Restore are planned and are not available on the Teams server yet.