fix all broken links

Author: renetapopova

modules/ROOT/pages/authentication-authorization/built-in-roles.adoc

@@ -830,7 +830,7 @@ These include the rights to perform the following classes of tasks:
 ** Manage link:{neo4j-docs-base-uri}/cypher-manual/current/indexes/[indexes] and link:{neo4j-docs-base-uri}/cypher-manual/current/constraints/[constraints].
 ** Allow the creation of labels, relationship types, or property names.
 ** Manage transactions.
-* Manage xref:authentication-authorization/dbms-administration.adoc[DBMS privileges] to control the rights to perform actions on the entire system:
+* Manage xref:authentication-authorization/dbms-administration/index.adoc[DBMS privileges] to control the rights to perform actions on the entire system:
 ** Manage xref:database-administration/index.adoc[multiple databases].
 ** Manage xref:authentication-authorization/manage-users.adoc[users] and xref:authentication-authorization/manage-roles.adoc[roles].
 ** Change configuration parameters.

modules/ROOT/pages/authentication-authorization/database-administration.adoc

@@ -182,7 +182,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.
 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.
+See link:https://neo4j.com/docs/status-codes/current/notifications/all-notifications/[Status Codes for Errors & Notifications -> List of notification codes] for details on notifications.
 
 The hierarchy between the different database privileges is shown in the image below.
 
@@ -679,7 +679,7 @@ Note that `START` and `STOP` privileges are not included in the xref:authenticat
 
 The `ALTER DATABASE`, `SET DATABASE ACCESS`, `SET DATABASE DEFAULT LANGUAGE`, and `ALTER COMPOSITE DATABASE` privileges can be granted both as database privileges and as DBMS privileges.
 The DBMS privilege is equivalent to granting the database privilege for all databases, `DATABASE *`.
-For more information on the DBMS privilege versions, see xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-database-management[The `DBMS DATABASE MANAGEMENT` privileges].
+For more information on the DBMS privilege versions, see xref:authentication-authorization/dbms-administration/dbms-database-management-privileges.adoc[The `DBMS DATABASE MANAGEMENT` privileges].
 
 
 The `ALTER DATABASE` privilege is used to enable the ability to modify a standard database:

modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-alias-management-privileges.adoc

@@ -113,7 +113,7 @@ TO role[, ...]
 
 |===
 
-=== Grant privilege to create aliases
+== Grant privilege to create aliases
 
 You can grant the privilege to create aliases using the `CREATE ALIAS` privilege. +
 For example:
@@ -139,7 +139,7 @@ SHOW ROLE aliasAdder PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to delete aliases
+== Grant privilege to delete aliases
 
 You can grant the privilege to delete aliases using the `DROP ALIAS` privilege. +
 For example:
@@ -165,7 +165,7 @@ SHOW ROLE aliasDropper PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to modify aliases
+== Grant privilege to modify aliases
 
 You can grant the privilege to modify aliases using the `ALTER ALIAS` privilege. +
 For example:
@@ -192,7 +192,7 @@ a|Rows: 1
 |===
 
 
-=== Grant privilege to list aliases
+== Grant privilege to list aliases
 
 You can grant the privilege to list aliases using the `SHOW ALIAS` privilege. +
 For example:
@@ -218,7 +218,7 @@ SHOW ROLE aliasViewer PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to manage aliases
+== Grant privilege to manage aliases
 
 You can grant the privilege to create, delete, modify, and list aliases using the `ALIAS MANAGEMENT` privilege. +
 For example:

modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-database-management-privileges.adoc

@@ -150,7 +150,7 @@ The DBMS privilege version is equivalent to granting the privilege for all datab
 For more information on the database privilege versions, see xref:authentication-authorization/database-administration.adoc#access-control-database-administration-alter-db[The alter database-related privileges].
 ====
 
-=== Grant privilege to create standard databases
+== Grant privilege to create standard databases
 
 You can grant the privilege to create standard databases using the `CREATE DATABASE` privilege. +
 For example:
@@ -176,7 +176,7 @@ SHOW ROLE databaseAdder PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to create composite databases
+== Grant privilege to create composite databases
 
 You can grant the privilege to create composite databases using the `CREATE COMPOSITE DATABASE` privilege. +
 For example:
@@ -202,7 +202,7 @@ SHOW ROLE compositeDatabaseAdder PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to delete standard databases
+== Grant privilege to delete standard databases
 
 You can grant the privilege to delete standard databases using the `DROP DATABASE` privilege. +
 For example:
@@ -228,7 +228,7 @@ SHOW ROLE databaseDropper PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to delete composite databases
+== Grant privilege to delete composite databases
 
 You can grant the privilege to delete composite databases using the `DROP COMPOSITE DATABASE` privilege. +
 For example:
@@ -254,7 +254,7 @@ SHOW ROLE compositeDatabaseDropper PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to modify standard databases
+== Grant privilege to modify standard databases
 
 You can grant the privilege to modify standard databases using the `ALTER DATABASE` privilege. +
 For example:
@@ -287,7 +287,7 @@ The DBMS privilege version is equivalent to granting the privilege for all datab
 For more information on the database privilege versions, see xref:authentication-authorization/database-administration.adoc#access-control-database-administration-alter-db[The alter database-related privileges].
 ====
 
-=== Grant privilege to modify access to standard databases
+== Grant privilege to modify access to standard databases
 
 You can grant the privilege to modify access to standard databases using the `SET DATABASE ACCESS` privilege. +
 For example:
@@ -321,7 +321,7 @@ For more information on the database privilege versions, see xref:authentication
 ====
 
 [role=label--new-2025.06]
-=== Grant privilege to modify the default language of standard databases
+== Grant privilege to modify the default language of standard databases
 
 You can grant the privilege to modify the default language of standard databases using the `SET DATABASE DEFAULT LANGUAGE` privilege. +
 For example:
@@ -356,7 +356,7 @@ For more information on the database privilege versions, see xref:authentication
 
 [role=label--new-2025.06]
 [[grant-privilege-alter-composite-database]]
-=== Grant privilege to modify composite databases
+== Grant privilege to modify composite databases
 
 You can grant the privilege to modify composite databases using the `ALTER COMPOSITE DATABASE` privilege. +
 For example:
@@ -389,7 +389,7 @@ The DBMS privilege version is equivalent to granting the privilege for all datab
 For more information on the database privilege versions, see xref:authentication-authorization/database-administration.adoc#access-control-database-administration-alter-db[The alter database-related privileges].
 ====
 
-=== Grant privilege to manage composite databases
+== Grant privilege to manage composite databases
 
 You can grant the privilege to create, delete, and modify composite databases using the `COMPOSITE DATABASE MANAGEMENT` privilege. +
 For example:
@@ -415,7 +415,7 @@ SHOW ROLE compositeDatabaseManager PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to manage standard and composite databases
+== Grant privilege to manage standard and composite databases
 
 You can grant the privilege to create, delete, and modify standard and composite databases using the `DATABASE MANAGEMENT` privilege. +
 For example:

modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-execute-privileges.adoc

@@ -114,12 +114,12 @@ GRANT [IMMUTABLE] EXECUTE BOOSTED [USER [DEFINED]] FUNCTION[S] name-globbing[, .
 |===
 
 [[access-control-execute-procedure]]
-=== Grant privilege to execute procedures
+== Grant privilege to execute procedures
 
 You can grant the privilege to execute procedures using the `EXECUTE PROCEDURE` privilege. +
-A role with this privilege is allowed to execute the procedures matched by the <<access-control-name-globbing, name-globbing>>.
+A role with this privilege is allowed to execute the procedures matched by the xref:authentication-authorization/dbms-administration/index.adoc#access-control-name-globbing[name-globbing].
 
-==== Grant privilege to execute some procedures
+=== Grant privilege to execute some procedures
 
 The following query allow the execution of procedures starting with `db.schema`:
 
@@ -146,7 +146,7 @@ SHOW ROLE procedureExecutor PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-==== Grant privilege to execute all but some procedures
+=== Grant privilege to execute all but some procedures
 
 You can grant the privilege to execute all except a few procedures using `EXECUTE PROCEDURES *` and deny the unwanted procedures.
 For example, the following queries allow the execution of all procedures, except those starting with `dbms.cluster`:
@@ -185,15 +185,15 @@ The `dbms.cluster.checkConnectivity`, `dbms.cluster.cordonServer`, `dbms.cluster
 
 
 [[access-control-execute-boosted-procedure]]
-=== Grant privilege to execute procedures with elevated privileges
+== Grant privilege to execute procedures with elevated privileges
 
 You can grant the privilege to execute procedures with elevated privileges using the `EXECUTE BOOSTED PROCEDURE` privilege. +
-A user with this privilege will not be restricted to their other privileges when executing the procedures matched by the <<access-control-name-globbing, name-globbing>>.
+A user with this privilege will not be restricted to their other privileges when executing the procedures matched by the xref:authentication-authorization/dbms-administration/index.adoc#access-control-name-globbing[name-globbing].
 The `EXECUTE BOOSTED PROCEDURE` privilege only affects the elevation, and not the execution of the procedure.
 Therefore, it is needed to grant `EXECUTE PROCEDURE` privilege for the procedures as well.
 Both `EXECUTE PROCEDURE` and `EXECUTE BOOSTED PROCEDURE` are needed to execute a procedure with elevated privileges.
 
-==== Grant privilege to execute some procedures with elevated privileges
+=== Grant privilege to execute some procedures with elevated privileges
 
 You can grant the privilege to execute some procedures with elevated privileges using `EXECUTE BOOSTED PROCEDURE *`.
 
@@ -226,7 +226,7 @@ a|Rows: 3
 |===
 
 [[grant-execute-procedure-deny-elevation]]
-==== Combination of granting execution and denying privilege elevation
+=== Combination of granting execution and denying privilege elevation
 
 As with grant, denying `EXECUTE BOOSTED PROCEDURE` on its own only affects the elevation and not the execution of the procedure.
 
@@ -259,7 +259,7 @@ a|Rows: 2
 |===
 
 [[grant-privilege-elevation-deny-execution]]
-==== Combination of granting privilege elevation and denying execution
+=== Combination of granting privilege elevation and denying execution
 
 You can also grant the privilege to execute procedures with elevated privileges and deny the execution of specific procedures.
 
@@ -294,7 +294,7 @@ a|Rows: 2
 |===
 
 [[grant-deny-privilege-elevation]]
-==== Combination of granting and denying privilege elevation
+=== Combination of granting and denying privilege elevation
 
 You can also grant the privilege to execute procedures with elevated privileges and deny the elevation for specific procedures.
 
@@ -330,7 +330,7 @@ SHOW ROLE deniedBoostedProcedureExecutor3 PRIVILEGES AS COMMANDS;
 a|Rows: 2
 |===
 
-==== Control procedure output with privileges
+=== Control procedure output with privileges
 
 You can control the output of procedures based on the privileges granted or denied to a role using the `EXECUTE PROCEDURE` and `EXECUTE BOOSTED PROCEDURE` privileges.
 For example, assume there is a procedure called `myProc`.
@@ -353,7 +353,7 @@ For comparison, when granted:
 
 
 [[access-control-admin-procedure]]
-=== Grant privilege to execute admin procedures
+== Grant privilege to execute admin procedures
 
 Admin procedures (annotated with `@Admin`) are special in that they require elevated privileges to be executed at all.
 This means that to execute an admin procedure you need both the <<access-control-execute-procedure, `EXECUTE PROCEDURE`>> and <<access-control-execute-boosted-procedure, `EXECUTE BOOSTED PROCEDURE`>> privileges for that procedure.
@@ -396,18 +396,18 @@ Any denied `EXECUTE` privilege results in the procedure not being allowed to be
 In this case, it does not matter whether `EXECUTE PROCEDURE`, `EXECUTE BOOSTED PROCEDURE` or `EXECUTE ADMIN PROCEDURES` is being denied.
 
 [[access-control-execute-user-defined-function]]
-=== Grant privilege to execute user-defined functions
+== Grant privilege to execute user-defined functions
 
 //EXECUTE [USER [DEFINED]] FUNCTION[S]
 You can grant the privilege to execute user-defined functions (UDFs) using the `EXECUTE USER DEFINED FUNCTION` privilege.
-A role with this privilege is allowed to execute the UDFs matched by the <<access-control-name-globbing, name-globbing>>.
+A role with this privilege is allowed to execute the UDFs matched by the xref:authentication-authorization/dbms-administration/index.adoc#access-control-name-globbing[name-globbing].
 
 [IMPORTANT]
 ====
 The `EXECUTE USER DEFINED FUNCTION` privilege does not apply to built-in functions, which are always executable.
 ====
 
-==== Grant privilege to execute some user-defined functions
+=== Grant privilege to execute some user-defined functions
 
 The following query shows an example of how to grant the `EXECUTE USER DEFINED FUNCTION` privilege:
 
@@ -442,7 +442,7 @@ SHOW ROLE functionExecutor PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-==== Grant privilege to execute all but some user-defined functions
+=== Grant privilege to execute all but some user-defined functions
 
 To allow the execution of all but a few UDFs, you can grant `+EXECUTE USER DEFINED FUNCTIONS *+` and deny the unwanted UDFs.
 For example, the following queries allow the execution of all UDFs except those starting with `apoc.any.prop`:
@@ -490,11 +490,11 @@ a|Rows: 2
 The `apoc.any.property` and `apoc.any.properties` are blocked, as well as any other UDFs starting with `apoc.any.prop`.
 
 [[access-control-execute-boosted-user-defined-function]]
-=== Grant privilege to execute user-defined functions with elevated privileges
+== Grant privilege to execute user-defined functions with elevated privileges
 
 //EXECUTE BOOSTED [USER [DEFINED]] FUNCTION[S]
 You can grant the privilege to execute user-defined functions (UDFs) with elevated privileges using the `EXECUTE BOOSTED USER DEFINED FUNCTION` privilege. +
-A user with this privilege will not be restricted to their other privileges when executing the UDFs matched by the <<access-control-name-globbing, name-globbing>>.
+A user with this privilege will not be restricted to their other privileges when executing the UDFs matched by the xref:authentication-authorization/dbms-administration/index.adoc#access-control-name-globbing[name-globbing].
 The `EXECUTE BOOSTED USER DEFINED FUNCTION` privilege only affects the elevation and not the execution of the function.
 Therefore, it is needed to grant `EXECUTE USER DEFINED FUNCTION` privilege for the UDFs as well.
 Both `EXECUTE USER DEFINED FUNCTION` and `EXECUTE BOOSTED USER DEFINED FUNCTION` are needed to execute a function with elevated privileges.
@@ -504,7 +504,7 @@ Both `EXECUTE USER DEFINED FUNCTION` and `EXECUTE BOOSTED USER DEFINED FUNCTION`
 The `EXECUTE BOOSTED USER DEFINED FUNCTION` privilege does not apply to built-in functions, as they have no concept of elevated privileges.
 ====
 
-==== Grant privilege to execute some user-defined functions with elevated privileges
+=== Grant privilege to execute some user-defined functions with elevated privileges
 
 The following query shows an example of how to grant the `EXECUTE BOOSTED USER DEFINED FUNCTION` privilege:
 

modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-impersonate-privileges.adoc

@@ -99,7 +99,7 @@ GRANT [IMMUTABLE] IMPERSONATE (user[, ...])
 
 |===
 
-=== Grant privilege to impersonate all users
+== Grant privilege to impersonate all users
 
 You can grant the privilege to impersonate all users using the `IMPERSONATE (*)` privilege. +
 For example:
@@ -126,7 +126,7 @@ SHOW ROLE allUserImpersonator PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to impersonate specific users
+== Grant privilege to impersonate specific users
 
 You can also grant the privilege to impersonate specific users or a subset of users. +
 For example:

modules/ROOT/pages/authentication-authorization/dbms-administration/dbms-privilege-management-privileges.adoc

@@ -106,7 +106,7 @@ GRANT [IMMUTABLE] PRIVILEGE MANAGEMENT
 | Enables the specified roles to list, assign, and remove privileges.
 |===
 
-=== Grant privilege to list privileges
+== Grant privilege to list privileges
 
 You can grant the `SHOW PRIVILEGE` privilege to allow a user to list privileges using the `SHOW PRIVILEGE`, `SHOW ROLE roleName PRIVILEGES`, and `SHOW USER username PRIVILEGES` administration commands.
 The `SHOW USER username PRIVILEGES` command also requires the `SHOW USER` privilege.
@@ -142,7 +142,7 @@ If a non-native auth provider like LDAP is in use, `SHOW USER PRIVILEGES` will o
 Other users' privileges cannot be listed when using a non-native auth provider.
 ====
 
-=== Grant privilege to assign privileges
+== Grant privilege to assign privileges
 
 You can grant the privilege to assign privileges using the `ASSIGN PRIVILEGE` privilege. +
 A user with this privilege is allowed to execute `GRANT` and `DENY` administration commands. +
@@ -169,7 +169,7 @@ SHOW ROLE privilegeAssigner PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to remove privileges
+== Grant privilege to remove privileges
 
 You can grant the privilege to remove privileges from roles using the `REMOVE PRIVILEGE` privilege. +
 A user with this privilege is allowed to execute `REVOKE` administration commands. +
@@ -196,7 +196,7 @@ SHOW ROLE privilegeRemover PRIVILEGES AS COMMANDS;
 a|Rows: 1
 |===
 
-=== Grant privilege to manage privileges
+== Grant privilege to manage privileges
 
 You can grant the privilege to list, assign, and remove privileges using the `PRIVILEGE MANAGEMENT` privilege. +
 For example: