Update links to new Cypher Manual Administration chapter

modules/ROOT/pages/authentication-authorization/access-control.adoc

@@ -82,7 +82,7 @@ This same database would be used by a number of different users, each with diffe
 
 Unlike applications which often require users to be modeled within the application itself, databases provide user management resources such as roles and privileges.
 This allows users to be created entirely within the database security model, a strategy that allows the separation of access to the data and the data itself.
-For more information, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/[Cypher Manual -> Access control].
+For more information, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/[Cypher Manual -> Access control].
 
 The following examples show two different approaches to using Neo4j security features to support the _healthcare_ database application.
 The first approach uses xref:authentication-authorization/built-in-roles/auth-built-in-roles[Built-in roles], whereas the second uses more advanced resources with fine-grained privileges for <<auth-access-control-using-privileges, sub-graph access control>>.
@@ -258,7 +258,7 @@ SHOW ROLE itadmin PRIVILEGES AS COMMANDS;
 
 [NOTE]
 ====
-Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
+Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
 ====
 
 To provide the IT administrator `tina` these privileges, they must be assigned the new role `itadmin`:
@@ -472,7 +472,7 @@ If the `researcherB` role is revoked to Charlie, but `researcherW` is granted, w
 
 [NOTE]
 ====
-Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
+Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
 ====
 
 === Privileges of `doctor`
@@ -749,7 +749,7 @@ GRANT DELETE ON GRAPH healthcare RELATIONSHIPS HAS, DIAGNOSIS TO receptionist;
 
 [NOTE]
 ====
-Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
+Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
 ====
 
 === Privileges of `nurse`
@@ -796,7 +796,7 @@ SHOW USER daniel PRIVILEGES AS COMMANDS;
 
 [NOTE]
 ====
-Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
+Privileges that were granted or denied earlier can be revoked using link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/manage-privileges/#access-control-revoke-privileges[the `REVOKE` command].
 ====
 
 Now the intention is that a nurse can perform the actions of a receptionist, which means they should be able to read and write the `address` field of the `Patient` nodes.
@@ -1051,7 +1051,7 @@ neo4j@system> SHOW USER tina PRIVILEGES AS COMMANDS;
 ====
 No other privilege management privileges were granted here.
 How much power this role should have would depend on the requirements of the system.
-Refer to the section link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/built-in-roles/[Cypher Manual -> The `admin` role] for a complete list of privileges to consider.
+Refer to the section link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/built-in-roles/[Cypher Manual -> The `admin` role] for a complete list of privileges to consider.
 ====
 
 Now Tina should be able to create new users and assign them to roles:

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

@@ -417,4 +417,4 @@ The subset of the functionality which is available with Community Edition is als
 |===
 
 More information about the built-in roles and their privileges can be found in
-link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/built-in-roles[Neo4j Cypher Manual].
+link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/built-in-roles[Neo4j Cypher Manual].

modules/ROOT/pages/authentication-authorization/introduction.adoc

@@ -25,7 +25,7 @@ For more information, see xref:configuration/password-and-user-recovery.adoc[Pas
 When triggered, Neo4j logs an error containing a timestamp and the message `failed to log in: too many failed attempts` in the _security.log_.
 ====
 +
-The Cypher commands to manage users, roles, and permissions are described in detail in link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/[Cypher Manual -> Administration].
+The Cypher commands to manage users, roles, and permissions are described in detail in link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/[Cypher Manual -> Access control].
 Various scenarios that illustrate the use of the native auth provider are available in xref:authentication-authorization/access-control.adoc[Fine-grained access control].
 
 *LDAP auth provider*::

modules/ROOT/pages/authentication-authorization/ldap-integration.adoc

@@ -123,7 +123,7 @@ dbms.security.ldap.authorization.group_to_role_mapping=\
 <3> Mapping of two LDAP groups to a Neo4j built-in role.
 <4> Mapping of an LDAP group to a custom-defined role.
 Custom-defined roles, such as `rolename`, must be explicitly created using the `CREATE ROLE rolename` command before they can be used to grant privileges.
-See link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/manage-users[the Cypher Manual -> Creating roles].
+See link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/manage-roles[the Cypher Manual -> Creating roles].
 ====
 
 [[auth-ldap-configure-provider-ad]]

modules/ROOT/pages/authentication-authorization/manage-execute-permissions.adoc

@@ -22,12 +22,12 @@ Please refer to link:{neo4j-docs-base-uri}/java-reference/{page-version}/extendi
 [[auth-manage-procedure-permissions]]
 == Manage procedure permissions
 
-Procedure permissions can be managed using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/dbms-administration#access-control-dbms-administration-execute[native execute privileges].
+Procedure permissions can be managed using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/dbms-administration#access-control-dbms-administration-execute[native execute privileges].
 These control whether the user is allowed to both execute a procedure, and which set of privileges apply during the execution.
 
-A procedure may be run using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/dbms-administration#access-control-execute-procedure[`EXECUTE PROCEDURE` privilege].
+A procedure may be run using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/dbms-administration#access-control-execute-procedure[`EXECUTE PROCEDURE` privilege].
 
-This allows the user to execute procedures that match the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/dbms-administration#access-control-name-globbing[globbed procedures].
+This allows the user to execute procedures that match the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/dbms-administration#access-control-name-globbing[globbed procedures].
 
 .Grant privilege to execute procedure
 ====
@@ -48,7 +48,7 @@ GRANT TRAVERSE ON GRAPH * RELATIONSHIP R1 TO role
 When calling the `db.schema.visualization` procedure that user will only see the `A` and `B` nodes and `R1` relationships, even though there might exist other nodes and relationships.
 ====
 
-A procedure may also be executed with elevated privileges using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/dbms-administration#access-control-execute-boosted-procedure[`EXECUTE BOOSTED PROCEDURE` privilege].
+A procedure may also be executed with elevated privileges using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/dbms-administration#access-control-execute-boosted-procedure[`EXECUTE BOOSTED PROCEDURE` privilege].
 
 [NOTE]
 --
@@ -74,12 +74,12 @@ When calling the `db.schema.visualization` procedure that user will see all node
 [[auth-manage-function-permissions]]
 == Manage user-defined function permissions
 
-User-defined function permissions can be managed using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/dbms-administration#access-control-dbms-administration-execute[native execute privileges].
+User-defined function permissions can be managed using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/dbms-administration#access-control-dbms-administration-execute[native execute privileges].
 These control if the user is both allowed to execute a user-defined function, and which set of privileges apply during the execution.
 
-A user-defined function may be executed using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/dbms-administration#access-control-execute-user-defined-function[`EXECUTE USER DEFINED FUNCTION` privilege].
+A user-defined function may be executed using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/dbms-administration#access-control-execute-user-defined-function[`EXECUTE USER DEFINED FUNCTION` privilege].
 
-This allows the user to execute user-defined functions that match the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/dbms-administration#access-control-name-globbing[globbed user-defined function].
+This allows the user to execute user-defined functions that match the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/dbms-administration#access-control-name-globbing[globbed user-defined function].
 
 .Grant privilege to execute user-defined function
 ====
@@ -100,7 +100,7 @@ When calling the user-defined function `MATCH (a:A) RETURN apoc.any.properties(a
 ====
 
 A user-defined function may also be executed with elevated privileges using the
-link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/dbms-administration#access-control-execute-boosted-user-defined-function[`EXECUTE BOOSTED USER DEFINED FUNCTION` privilege].
+link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/dbms-administration#access-control-execute-boosted-user-defined-function[`EXECUTE BOOSTED USER DEFINED FUNCTION` privilege].
 
 [NOTE]
 --

modules/ROOT/pages/authentication-authorization/sso-integration.adoc

@@ -181,7 +181,7 @@ dbms.security.oidc.mysso.authorization.group_to_role_mapping=\
 <3> Mapping of two identity provider groups to a Neo4j built-in role.
 <4> Mapping of an identity provider group to a custom-defined role.
 Custom-defined roles, such as `rolename`, must be explicitly created using the `CREATE ROLE rolename` command before they can be used to grant privileges.
-See link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/manage-users[the Cypher Manual -> Creating roles].
+See link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control/manage-roles[the Cypher Manual -> Creating roles].
 ====
 
 [[auth-sso-configure-provider]]

modules/ROOT/pages/clustering/databases.adoc

@@ -9,7 +9,7 @@ If a database is no longer needed, the command `DROP DATABASE` deletes the datab
 
 == `CREATE DATABASE`
 
-The command to create a database in a cluster is not significantly different from the command to create a database in a non-clustered environment (see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/databases[Cypher Manual -> Database management] for more information on database management on single servers).
+The command to create a database in a cluster is not significantly different from the command to create a database in a non-clustered environment (see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/databases[Cypher Manual -> Database management] for more information on database management on single servers).
 The difference in a clustered environment is that the topology can be specified, i.e. how many primaries and secondaries are desired for the database.
 To create a database `foo` with 3 servers hosting the database in primary mode and 2 servers in secondary mode, the command looks like this:
 

modules/ROOT/pages/clustering/servers.adoc

@@ -251,7 +251,7 @@ neo4j@neo4j> ALTER SERVER '25a7efc7-d063-44b8-bdee-f23357f89f01' SET OPTIONS {mo
 Altering servers may cause databases to be moved, and should be performed with care.
 For example, if the server `25a7efc7-d063-44b8-bdee-f23357f89f01` hosts database `foo` in primary mode when the above command is executed, then another server must begin hosting `foo` in primary mode.
 Likewise, if `ALTER SERVER '25a7efc7-d063-44b8-bdee-f23357f89f01' SET OPTIONS {allowedDatabases:['bar','baz']};` is executed, then `foo` is forced to move.
-For a description of all the server options (e.g., server tags) that can be altered via the `ALTER SERVER` command, see the xref:link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control/server-management/#server-management-alter-server[Cypher Manual -> Modifying servers].
+For a description of all the server options (e.g., server tags) that can be altered via the `ALTER SERVER` command, see the xref:link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/servers/#server-management-alter-server[Cypher Manual -> Modifying servers].
 
 [NOTE]
 ====

modules/ROOT/pages/composite-databases/introduction.adoc

@@ -24,7 +24,7 @@ These graphs are added to the composite database by means of database aliases.
 A Neo4j DBMS can have multiple composite databases, and they can be created both in single-instance deployments, and in cluster deployments.
 
 Composite databases are managed using administrative commands.
-They are created with the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/databases#administration-databases-create-composite-database[`CREATE COMPOSITE DATABASE`] command.
+They are created with the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/databases#administration-databases-create-composite-database[`CREATE COMPOSITE DATABASE`] command.
 
 .Creating a composite database
 ====
@@ -34,7 +34,7 @@ CREATE COMPOSITE DATABASE cineasts
 ----
 ====
 
-Constituent graphs are added with the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/aliases#alias-management-create-database-alias[`CREATE ALIAS`] administrative command, for example:
+Constituent graphs are added with the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/aliases#alias-management-create-database-alias[`CREATE ALIAS`] administrative command, for example:
 
 .Creating an alias on a composite database
 ====
@@ -59,7 +59,7 @@ CREATE ALIAS cineasts.upcoming
 ----
 ====
 
-The link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/databases#administration-databases-show-databases[`SHOW DATABASE`] administrative command includes composite databases.
+The link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/databases#administration-databases-show-databases[`SHOW DATABASE`] administrative command includes composite databases.
 
 Their `type` is reported as `"composite"`, and the `constituents` column lists the names of the aliases contained.
 
@@ -80,7 +80,7 @@ SHOW DATABASE cineasts YIELD name, type, constituents
 ====
 
 
-The link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/aliases#alias-management-show-alias[`SHOW ALIASES FOR DATABASE`] administrative command can be used to inspect aliases on composite databases in further detail.
+The link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/aliases#alias-management-show-alias[`SHOW ALIASES FOR DATABASE`] administrative command can be used to inspect aliases on composite databases in further detail.
 
 .Showing composite database aliases
 ====
@@ -98,4 +98,4 @@ SHOW ALIASES FOR DATABASE
 ----
 ====
 
-For a full description of the administrative commands for managing composite databases, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/databases[Cypher Manual -> Database management].
+For a full description of the administrative commands for managing composite databases, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/databases[Cypher Manual -> Database management].

modules/ROOT/pages/manage-databases/configuration.adoc

@@ -11,7 +11,7 @@
 Administrative commands should not be used during a rolling upgrade.
 For more information, see link:{neo4j-docs-base-uri}/upgrade-migration-guide/upgrade/upgrade-4.4/causal-cluster/[Upgrade and Migration Guide -> Upgrade a cluster].
 
-For detailed information on Cypher administrative commands, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/databases[Cypher Manual -> Database management].
+For detailed information on Cypher administrative commands, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/databases[Cypher Manual -> Database management].
 ====
 
 Before using administrative commands, it is important to understand the difference between stopped databases, and dropped databases:
@@ -75,9 +75,9 @@ For example, `main.db` is a valid database name.
 ====
 
 It is possible to create an alias to refer to an existing database to avoid these restrictions.
-For more information, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/aliases#alias-management-create-database-alias[Cypher Manual -> Creating database aliases].
+For more information, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/aliases#alias-management-create-database-alias[Cypher Manual -> Creating database aliases].
 
-For detailed information on Cypher administrative commands, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/access-control[Cypher Manual -> Access Control].
+For detailed information on Cypher administrative commands, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/access-control[Cypher Manual -> Access Control].
 
 For examples of using the Cypher administrative commands to manage multiple active databases, see xref:manage-databases/queries.adoc[Queries].
 
@@ -147,7 +147,7 @@ Regardless of settings of `server.databases.default_to_read_only`, `server.datab
 
 [NOTE]
 ====
-Another way of preventing writes is to set the database access to read-only using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/databases#administration-databases-alter-database[ALTER DATABASE] command.
+Another way of preventing writes is to set the database access to read-only using the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/databases#administration-databases-alter-database[ALTER DATABASE] command.
 ====
 
 

modules/ROOT/pages/manage-databases/errors.adoc

@@ -173,7 +173,7 @@ neo4j@system> SHOW DATABASE foo;
 ----
 ====
 
-If repeated retries of a command have no effect, or if a database is in a `dirty` state, you may drop and recreate the database, as detailed in link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/databases[Cypher manual -> Database management].
+If repeated retries of a command have no effect, or if a database is in a `dirty` state, you may drop and recreate the database, as detailed in link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/administration/databases[Cypher manual -> Database management].
 
 [NOTE]
 ====