DataGrip data editor: submitted grid edits invisible to other sessions in manual commit mode

I use DataGrip's data editor to make small corrections directly in the result grid, and I need to settle one behavior before trusting it on shared tables. My understanding is that submitting an edit in the grid only stages it in my open session, and it becomes permanent and visible to other clients only when the transaction commits.

The uncertainty is around the per-console transaction mode (auto-commit vs. manual commit) exposed in the transaction widget. I want to pick one mode as a team default for interactive editing, but the trade-offs are unclear to me: auto-commit makes each submitted change durable immediately, while manual mode lets me review a batch of edits before committing but may hold locks on some DBMSs while the transaction stays open.

I also gather that the IDE toggle is enforced client-side and may interact with server-side session settings depending on the driver, so effective behavior could differ per data source.

Assuming a recent DataGrip release (2024.x or later):

1. In manual commit mode, is it expected that a submitted grid edit is invisible to a second client session until I explicitly commit, and is that the usual explanation for edits that look 'stuck'?
2. Can the IDE's auto-commit setting be silently overridden or contradicted by server-side session configuration for certain drivers, and how do I confirm which side wins?
3. For a team default, which failure modes should decide between auto-commit and manual mode?