Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ Use `REVOKE` if you want to remove a privilege.
====

Common errors, such as misspellings or attempts to revoke privileges that have not been granted or denied, will lead to notifications.
Some of these notifications may be replaced with errors in a future major version of Neo4j.
In Cypher 25, notifications for impossible `REVOKE` commands, where a user, a role, or a database does not exist, have been replaced with errors.
See link:{neo4j-docs-base-uri}/status-codes/{page-version}/notifications/all-notifications[Status Codes for Errors & Notifications -> Server notifications] for details on notifications.

The hierarchy between the different database privileges is shown in the image below.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ Use `REVOKE` if you want to remove a privilege.
====

Common errors, such as misspellings or attempts to revoke privileges that have not been granted or denied, will result in notifications.
Some of these notifications may be replaced with errors in a future major version of Neo4j.
In Cypher 25, notifications for impossible `REVOKE` commands, where a user, a role, or a database does not exist, have been replaced with errors.
See link:{neo4j-docs-base-uri}/status-codes/{page-version}/notifications/all-notifications[Status Codes -> Notification codes] for details on notifications.

The general `GRANT` and `DENY` syntaxes are illustrated in the following image:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -814,7 +814,7 @@ REVOKE ROLES role1, role2 FROM user1, user2, user3
----

Common errors, such as misspellings or attempts to revoke roles from users who have not been granted those roles, will lead to notifications.
Some of these notifications may be replaced with errors in a future major version of Neo4j.
In Cypher 25, notifications for impossible `REVOKE` commands, where a user, a role, or a database does not exist, have been replaced with errors.
See link:{neo4j-docs-base-uri}/status-codes/{page-version}/notifications/all-notifications[Status Codes -> Notification codes] for details on notifications.

[[access-control-drop-roles]]
Expand Down