All posts

Granular Database Roles in Lnav

The cursor blinks. Access denied. You know the role isn’t right, but you need the query to run. Lnav granular database roles solve this. Instead of broad permissions that expose more than they should, granular roles split authority into precise capabilities. They define exactly what a user can view, edit, or execute inside Lnav’s query interface. No guessing, no overlap. Granular database roles in Lnav are built around the principle of least privilege. Each role is a controlled set of privileg

Free White Paper

Just-in-Time Access + Database Access Proxy: The Complete Guide

Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.

Free. No spam. Unsubscribe anytime.

The cursor blinks. Access denied. You know the role isn’t right, but you need the query to run.

Lnav granular database roles solve this. Instead of broad permissions that expose more than they should, granular roles split authority into precise capabilities. They define exactly what a user can view, edit, or execute inside Lnav’s query interface. No guessing, no overlap.

Granular database roles in Lnav are built around the principle of least privilege. Each role is a controlled set of privileges tied to specific databases, tables, or commands. You can grant read-only access to one dataset while allowing full write access to another, without risk of cross-contamination or unauthorized action.

In a production environment, this level of control matters. Misconfigured roles can leak sensitive data or allow destructive commands. Lnav’s role system gives you fine-tuned control over SQL execution, database browsing, and even log inspection. Admins can create roles for developers, auditors, or operators, each bound tightly to what they need—and nothing more.

Continue reading? Get the full guide.

Just-in-Time Access + Database Access Proxy: Architecture Patterns & Best Practices

Free. No spam. Unsubscribe anytime.

Setting up granular roles in Lnav is straightforward. Start by defining your databases in the config. Assign each role to a set of permissions:

  • READ for safe data access
  • WRITE for controlled updates
  • EXECUTE for approved query execution

Tie these permissions to role names, add users to those roles, and deploy. Lnav enforces these at runtime, ensuring no access outside defined boundaries.

Security policies demand traceability. Lnav’s granular roles integrate with audit logs, so every action carries a signature: who did it, when, and under which permission set. This makes compliance transparent and incident response faster.

If your team’s workflows depend on multiple databases or mixed environments, granular roles reduce friction. You no longer juggle high-level accounts with unpredictable access patterns. Instead, each engineer logs in knowing exactly what their role can—and cannot—do.

Test it yourself. Go to hoop.dev, spin up Lnav with granular database roles, and see secure precision in action in minutes.

Get started

See hoop.dev in action

One gateway for every database, container, and AI agent. Deploy in minutes.

Get a demoMore posts