Clients
functionalUse clients as the top-level home for the connections that belong to the same customer or owner.
A Client is the top-level owner for a connection: a customer, team, or organization. It is more than a label, carrying its own color, icon, and query protections wherever it appears.
Creating and assigning
- In the connection editor, type a client name in the Client field. As you type, a list suggests the clients you already have whose names contain what you have typed; click one to use it exactly as it is spelled.
- A name that doesn't exist yet is registered as a client automatically when you save, so you can immediately give it a color or a safety rule.
- Refine it in Tools › Manage Clients, Projects & Environments...: name, color (hex + picker), icon (browse for an image), and a Query Protections section. Tools › Connection Management... has a Clients pane with the same fields (its protections are headed Safety Features), where you can also drag an image file onto the Icon box.
Client matching is by name and case-insensitive, so every connection tagged with a client inherits that client's color and safety policy.


Where a client shows up
| Place | What you see |
|---|---|
| Explorer, By client view | One folder per client, its header tinted with the client's color and showing its icon. Connections with no client gather in “Unassigned” at the bottom. See Grouping views. |
| Status bar | The active connection's client as a badge in the client's color and icon, next to its project and environment badges. |
| Connection Management | Each client in the Clients list with its icon (or a color dot when it has no icon). On a connection's form, any protection the client switches on is listed as “… from ‘Acme’” and marked enforced. |
Client-wide safety
The client's Query Protections are the same toggles every client, project, and environment has - see the table on Connection Organization. Production marking, rollback-wrap, SELECT-only, confirmation, and AI review set on a client are added to every connection tagged with it. They can only switch a guard on: a connection never inherits a looser setting from its client.
Renaming, removing, and spelling
- Renaming a client does not retag its connections. Connections store the client's name, not a link to it. Rename “Acme” to “Acme Corp” and connections still tagged “Acme” lose the color and protections until you edit them to the new name. Rename the connections too, or keep the old name.
- Removing a client deletes its color, icon, and protections. Connections keep the client name as text, so they still group together in By client, just without the color or the safety policy.
- Same name, different case. Color and protections match case-insensitively, but the explorer's folders use the text exactly as typed, so “Acme” and “acme” give you two folders. Picking from the suggestion list avoids it.
- Icons are referenced, not copied. SQLly stores the path to the image you chose (PNG, JPEG, GIF, SVG, ICO, BMP, or WebP). Move or delete that file and the icon stops showing; keep logos somewhere stable.
Clients, with their colors and icons, live in your connections file alongside your connections - never any passwords - and travel in a credential file when you export one.