Security
functionalUsers, roles, membership, and access for the selected database.
Database-level security for the selected database: its users, their role membership, and the object and schema permissions that shape what each one can touch. Same master-list-plus-editor dialog as the server version, scoped one level down.
Why this is separate from server security
What you edit here
- Users - with a database picker at the top, a login dropdown when creating one, and a default-schema field.
- Database roles - membership as a checklist, including the fixed roles (
db_datareader,db_datawriter,db_owner, and the rest) alongside your own. - Permissions - what has been granted on schemas and objects within this database.
Nothing runs until you apply
Edits are diffed against the baseline that was loaded and rendered as an exact batch
under Statements to apply - CREATE USER, role grants,
permission changes - shown verbatim before the Apply (N) button,
which counts them. Read them, copy them into a change request, or close the dialog
and nothing has happened. A connection marked production read-only disables Apply
entirely.

Per-engine shape follows the engine: PostgreSQL's roles and schema grants, and MySQL's 'user'@'host' accounts with per-database privileges, are handled in the terms those engines actually use rather than being forced into a SQL Server mould. Oracle's users and roles come from the DBA_* views (falling back to USER_* / ALL_* with a note when those aren't granted), and the editor scripts CREATE USER, GRANT / REVOKE and ACCOUNT LOCK / UNLOCK. ClickHouse gets a read-only view over system.users and system.grants that scripts CREATE USER and GRANT statements for you to run. The editor is unavailable (with the reason) on SQLite, libSQL / Turso and DuckDB (no logins; access is the file's own permissions), on Redis (use ACL SETUSER / ACL LIST in a query tab), and on the wire-compatible PostgreSQL and MySQL labels whose catalogs differ (CockroachDB, YugabyteDB, TiDB, PlanetScale).