How to Configure Neo4j Read Only User
You set up a neo4j read only user by assigning a reader role to an account. This built-in role lets the user run read queries while blocking all graph changes. Most teams create one shared reader account for developers and support staff. Broad shared roles often expose sensitive node properties and make audit tracking hard. How a neo4j read only user works in practice Neo4j manages user rights through its built-in system database. Admins create new accounts inside this central system store. N
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You set up a neo4j read only user by assigning a reader role to an account. This built-in role lets the user run read queries while blocking all graph changes. Most teams create one shared reader account for developers and support staff. Broad shared roles often expose sensitive node properties and make audit tracking hard.
How a neo4j read only user works in practice
Neo4j manages user rights through its built-in system database. Admins create new accounts inside this central system store. Next, the admin links the account to a built-in reader role. This role grants the right to traverse the graph and read data. It blocks commands that add, edit, or delete nodes and relationships. It also stops the user from changing indexes or database constraints.
For finer control, admins can build custom roles in the enterprise edition. A custom role can allow traversal on specific node labels only. It can also deny read rights on chosen relationship types or properties. When a user logs in, the database checks these role rules first. Every query goes through this check before the engine reads any graph data. If a query tries to write data, the database stops it right away.
What native roles solve and what they miss
Native reader roles solve the problem of accidental data changes in production. A developer with a reader role cannot drop a node by mistake. They also cannot wipe out links between records during a debug session. This setup protects graph integrity during daily fixing work.
Still, static roles leave several daily security gaps open for your team. First, teams often share one reader password across many people and tools. When a bad query runs, the database log only shows that shared account. You cannot tell which person on the team actually ran the query. Second, a reader role still returns raw text from allowed properties. If nodes hold emails, phone numbers, or card numbers, those values appear in results. Masking is needed to rewrite matched fields in results before they reach the screen. Third, a read query can still traverse millions of nodes and lock up memory. Native login checks decide who gets in, not how safe each query is.
Read-Only Root Filesystem + User Provisioning (SCIM): architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Managing graph access across growing teams
As your team grows, keeping track of local database accounts gets hard. Admins have to add, update, and remove users across every database instance. When someone leaves the team, an admin must remember to delete their account. Old accounts often stay active for months without anyone noticing the risk.
Linking your graph database to a single sign-on provider helps fix user sprawl. Even then, group mappings often grant permanent read rights to entire teams. Engineers keep read rights all day even when they only debug once a month. A strong setup ties each query to an individual user identity. It also checks query safety and rewrites sensitive fields in the output.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
Can a neo4j read only user exists in the community edition?
No, the community edition does not support role-based access control or reader roles. It only allows basic admin accounts that have full read and write rights.
Does a read only role stop heavy queries from slowing the database?
No, a reader role only blocks data changes and schema updates. A user can still run an unbounded graph traversal that uses up server memory.
Can native roles hide sensitive fields like emails or phone numbers?
Custom roles can block access to a whole property key across the graph. Still, they cannot mask part of a value while leaving the rest visible.
Related guides
In this post