How to Configure Neo4j Create User

Published
Length
3 min read

Luis Felipe Dias

All posts

You run a neo4j create user statement in the system database to add accounts. The database stores these credentials and assigns a base role to the new account. Teams often set up shared accounts so engineers can debug graph queries fast. Still, broad permissions let a single bad query alter or wipe production nodes. How the neo4j create user workflow operates Neo4j manages user accounts inside a dedicated internal system database. You must switch to this system context before you add any new

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 run a neo4j create user statement in the system database to add accounts. The database stores these credentials and assigns a base role to the new account. Teams often set up shared accounts so engineers can debug graph queries fast. Still, broad permissions let a single bad query alter or wipe production nodes.

How the neo4j create user workflow operates

Neo4j manages user accounts inside a dedicated internal system database. You must switch to this system context before you add any new accounts. An admin sends a creation statement with a username and an initial password. You can force the user to change this password at first login.

In community editions, the database supports basic account management without custom roles. Every valid user gets full read and write access to the graph. Enterprise editions add role-based access control for finer permission splits. Admins create custom roles and attach specific graph privileges to those roles.

Privileges control who can traverse nodes, read properties, or write new edges. After you create the account, you grant one or more roles to it. The database checks these assigned roles whenever the user starts a new session. You can also suspend an account to block logins without deleting the user.

Why static graph roles leave operational gaps

Native roles work well when you separate apps from human admins. You can give a reporting app read-only rights on a single graph. This setup stops the app from dropping indexes or deleting core nodes. It also blocks unauthorized people from logging into the database cluster.

Still, static roles only decide who can log in and which labels exist. They do not inspect what individual queries do in flight during a session. A support engineer with read rights can still pull every node property. Those properties often hold sensitive emails, phone numbers, card numbers, or national IDs.

User Provisioning (SCIM) + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

You also have to manage password rotation across every person on the team. When someone leaves the team, admins must find and revoke their static accounts. Shared accounts make audit logs hard to read during a security review. You see the shared account name in the log, not the actual person.

Managing graph permissions across growing engineering teams

As teams grow, managing individual graph accounts by hand takes too much time. Admins often map external directory groups to internal database roles to save time. This link lets central identity teams control who can log in to Neo4j. Yet directory groups still grant broad session rights once the login succeeds.

Teams need a way to check queries before the database runs them. They also need data masking that rewrites matched fields in results for sensitive properties. Controlling queries at the statement level keeps production graphs safe during live debugging. It also removes the need to share static database passwords with engineers.

Govern statements and responses across databases and APIs

Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev sits inline in the protocol beside each supported service as an open-source proxy, a sidecar for your database or API. For every query or command an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human approval.

First, hoop.dev guardrails block banned queries before they run or hold risky ones for review, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.

Frequently asked questions

Where does Neo4j store user accounts and roles?

Neo4j stores all user accounts and role assignments inside its built-in system database. Admins must run account statements against this system database, not the user graph.

Can I assign roles during the neo4j create user step in Community Edition?

No, the Community Edition only supports basic user creation and password updates. Role-based access control and custom graph privileges require the Enterprise Edition.

How do I stop a user from logging in without deleting their account?

An admin can run an alter user command to set the account status to suspended. This action blocks new logins right away while keeping the user record intact.

The query runs. The emails stay hidden.