correct broken links due to enteprise feature move

raphael-istari · raphael-istari · commit b24b99caa74d · 2025-12-02T15:49:45.000-08:00
diff --git a/docusaurus-docs/docs-graphql/admin/admin-api.md b/docusaurus-docs/docs-graphql/admin/admin-api.md
@@ -806,7 +806,7 @@ Here are the important types, queries, and mutations from the `admin` schema.
 You'll notice that the `/admin` schema is very much the same as the schemas generated by Dgraph GraphQL.
 
 * The `health` query lets you know if everything is connected and if there's a schema currently being served at `/graphql`.
-* The `state`  query returns the current state of the cluster and group membership information. For more information about `state` see [here](/admin/dgraph-zero#more-about-the-state-endpoint).
+* The `state`  query returns the current state of the cluster and group membership information. 
 * The `config` query returns the configuration options of the cluster set at the time of starting it.
 * The `getGQLSchema` query gets the current GraphQL schema served at `/graphql`, or returns null if there's no such schema.
 * The `updateGQLSchema` mutation allows you to change the schema currently served at `/graphql`.
diff --git a/docusaurus-docs/docs-graphql/admin/index.md b/docusaurus-docs/docs-graphql/admin/index.md
@@ -28,25 +28,6 @@ When you start Dgraph, two GraphQL endpoints are served.
 
 At `/graphql` you'll find the GraphQL API for the types you've added.  That's what your app would access and is the GraphQL entry point to Dgraph.  If you need to know more about this, see the [quick start](https://dgraph.io/docs/graphql/quick-start/) and [schema docs](https://dgraph.io/docs/graphql/schema/).
 
-### /admin
-
-At `/admin` you'll find an admin API for administering your GraphQL instance.  The admin API is a GraphQL API that serves POST and GET as well as compressed data, much like the `/graphql` endpoint.
-
-
-* The `health` query lets you know if everything is connected and if there's a schema currently being served at `/graphql`.
-* The `state`  query returns the current state of the cluster and group membership information. For more information about `state` see [here](/admin/dgraph-zero#more-about-the-state-endpoint).
-* The `config` query returns the configuration options of the cluster set at the time of starting it.
-* The `getGQLSchema` query gets the current GraphQL schema served at `/graphql`, or returns null if there's no such schema.
-* The `updateGQLSchema` mutation allows you to change the schema currently served at `/graphql`.
-
-## Enterprise features
-
-Enterprise Features like ACL, Backups and Restore are also available using the GraphQL API at `/admin` endpoint.
-
-* [ACL](/admin/enterprise-features/access-control-lists#accessing-secured-dgraph)
-* [Backups](/admin/admin-tasks/binary-backups#create-a-backup)
-* [Restore](/admin/admin-tasks/binary-backups#online-restore)
-
 ## First start
 
 On first starting with a blank database:
diff --git a/docusaurus-docs/docs-graphql/graphql-dql/graphql-dql-schema.md b/docusaurus-docs/docs-graphql/graphql-dql/graphql-dql-schema.md
@@ -157,7 +157,7 @@ In particular, you can
 - use Dgraph DQL mutations but also Dgraph's [import tools](/migration/import-data) to populate the graph after you have deployed a GraphQL Schema. See [GraphQL data loading](/graphql/graphql-dql/graphql-data-loading)
 - use DQL to query the graph in the context of authorization rules and custom resolvers.
 - add knowledge to your graph such as meta-data, score, annotations, ...,  but also relationships or relationships attributes (facets) that could be the result of similarity computation, threat detection a.s.o. The added data could be hidden from your GraphQL API clients but be available to logic written with DQL clients.
-- break things using DQL: DQL is powerful and is bypassing constraints expressed in the GraphQL schema. You can for example delete a node predicate that is mandatory in the GraphQL API! Hopefully there are ways to secure who can read/write/delete predicates. ( see the [ACL](/admin/enterprise-features/access-control-lists/)) section.
+- break things using DQL: DQL is powerful and is bypassing constraints expressed in the GraphQL schema. You can for example delete a node predicate that is mandatory in the GraphQL API! Hopefully there are ways to secure who can read/write/delete predicates. ( see the [ACL](/admin/admin-tasks/user-management-access-control)) section.
 - fix things using DQL: this is especially useful when doing GraphQL Schema updates which require some [data migrations](/graphql/graphql-dql/graphql-data-migration). 
 
 
diff --git a/docusaurus-docs/docs-graphql/security/index.md b/docusaurus-docs/docs-graphql/security/index.md
@@ -47,7 +47,7 @@ You can use any authentication method that is capable of generating such JWT tok
 
 
 ### ACL
-Note that another token may be needed to access the system if ACL security is also enabled. See the [ACLs](/admin/enterprise-features/access-control-lists/) section for details. The ACLs are a separate security mechanism.
+Note that another token may be needed to access the system if ACL security is also enabled. See the [ACLs](/installation/configuration/enable-acl) section for details. The ACLs are a separate security mechanism.
 
 ### JWT Claims
 
diff --git a/docusaurus-docs/docs-ratel/connection.md b/docusaurus-docs/docs-ratel/connection.md
@@ -27,7 +27,7 @@ Under the input box you have tree icons which gives you the status of the connec
 - Logging in: a "lock" icon.
 
 :::tip
-To connect to a standard Dgraph instance, you only need to click on `Connect`. There's a specific section to [login using ACL](#acl-account) ([Enterprise feature](/admin/enterprise-features/access-control-lists/)).
+To connect to a standard Dgraph instance, you only need to click on `Connect`. There's a specific section to [login using ACL](#acl-account).
 :::
 
 ## Cluster Settings
diff --git a/docusaurus-docs/docs/clients/javascript/grpc.md b/docusaurus-docs/docs/clients/javascript/grpc.md
@@ -62,7 +62,7 @@ To facilitate debugging, [debug mode](#debug-mode) can be enabled for a client.
 
 ### Multi-tenancy
 
-In [multi-tenancy](../../../admin/enterprise-features/multitenancy) environments, `dgraph-js` provides a new method `loginIntoNamespace()`,
+In [multi-tenancy](../../../admin/admin-tasks/multitenancy) environments, `dgraph-js` provides a new method `loginIntoNamespace()`,
 which will allow the users to login to a specific namespace.
 
 In order to create a JavaScript client, and make the client login into namespace `123`:
diff --git a/docusaurus-docs/docs/migration/live-loader.md b/docusaurus-docs/docs/migration/live-loader.md
@@ -195,13 +195,13 @@ dgraph live \
 
 ## Enterprise Features
 
-### Multi-tenancy (Enterprise Feature)
+### Multi-tenancy
 
-Since [multi-tenancy](/admin/enterprise-features/multitenancy) requires ACL,
+Since multi-tenancy requires ACL,
 when using the Live loader you must provide the login credentials using the `--creds` flag.
 By default, Live loader loads the data into the user's namespace.
 
-[Guardians of the Galaxy](/admin/enterprise-features/multitenancy#guardians-of-the-galaxy) can load the data into multiple namespaces.
+[Guardians of the Galaxy](/admin/admin-tasks/multitenancy#guardians-of-the-galaxy) can load the data into multiple namespaces.
 Using `--force-namespace`, a _Guardian_ can load the data into the namespace specified in the data and schema files.
 
 :::note
diff --git a/docusaurus-docs/docs/migration/loading-csv-data.md b/docusaurus-docs/docs/migration/loading-csv-data.md
@@ -172,7 +172,7 @@ This JSON file can be loaded into Dgraph using the programmatic clients.
     }
     ```
 :::note
-To reuse existing integer IDs from a CSV file as UIDs in Dgraph, use Dgraph Zero's [assign endpoint](/admin/dgraph-zero) before loading data to allocate a range of UIDs that can be safely assigned.
+To reuse existing integer IDs from a CSV file as UIDs in Dgraph, use Dgraph Zero's [assign endpoint](/admin/admin-endpoints) before loading data to allocate a range of UIDs that can be safely assigned.
 :::
 
 4. Paste the output in the **Mutate** tab of **Console** in Ratel, and click **Run** to import data.
diff --git a/docusaurus-docs/docs_versioned_docs/version-v24.1/clients/javascript/grpc.md b/docusaurus-docs/docs_versioned_docs/version-v24.1/clients/javascript/grpc.md
@@ -62,7 +62,7 @@ To facilitate debugging, [debug mode](#debug-mode) can be enabled for a client.
 
 ### Multi-tenancy
 
-In [multi-tenancy](../../../admin/enterprise-features/multitenancy) environments, `dgraph-js` provides a new method `loginIntoNamespace()`,
+In [multi-tenancy](../../../admin/admin-tasks/multitenancy) environments, `dgraph-js` provides a new method `loginIntoNamespace()`,
 which will allow the users to login to a specific namespace.
 
 In order to create a JavaScript client, and make the client login into namespace `123`:
diff --git a/docusaurus-docs/docs_versioned_docs/version-v24.1/migration/live-loader.md b/docusaurus-docs/docs_versioned_docs/version-v24.1/migration/live-loader.md
@@ -195,13 +195,13 @@ dgraph live \
 
 ## Enterprise Features
 
-### Multi-tenancy (Enterprise Feature)
+### Multi-tenancy
 
-Since [multi-tenancy](/admin/enterprise-features/multitenancy) requires ACL,
+Since multi-tenancy requires ACL,
 when using the Live loader you must provide the login credentials using the `--creds` flag.
 By default, Live loader loads the data into the user's namespace.
 
-[Guardians of the Galaxy](/admin/enterprise-features/multitenancy#guardians-of-the-galaxy) can load the data into multiple namespaces.
+[Guardians of the Galaxy](/admin/admin-tasks/multitenancy#guardians-of-the-galaxy) can load the data into multiple namespaces.
 Using `--force-namespace`, a _Guardian_ can load the data into the namespace specified in the data and schema files.
 
 :::note
diff --git a/docusaurus-docs/docs_versioned_docs/version-v24.1/migration/loading-csv-data.md b/docusaurus-docs/docs_versioned_docs/version-v24.1/migration/loading-csv-data.md
@@ -172,7 +172,7 @@ This JSON file can be loaded into Dgraph using the programmatic clients.
     }
     ```
 :::note
-To reuse existing integer IDs from a CSV file as UIDs in Dgraph, use Dgraph Zero's [assign endpoint](/admin/dgraph-zero) before loading data to allocate a range of UIDs that can be safely assigned.
+To reuse existing integer IDs from a CSV file as UIDs in Dgraph, use Dgraph Zero's [assign endpoint](/admin/admin-endpoints)) before loading data to allocate a range of UIDs that can be safely assigned.
 :::
 
 4. Paste the output in the **Mutate** tab of **Console** in Ratel, and click **Run** to import data.
diff --git a/docusaurus-docs/docusaurus.config.ts b/docusaurus-docs/docusaurus.config.ts
@@ -222,6 +222,12 @@ const config: Config = {
       darkTheme: prismThemes.dracula,
     },
   } satisfies Preset.ThemeConfig,
+  scripts: [
+    {
+      src: 'https://www.googletagmanager.com/gtag/js?id=GTM-TZTPBZBZ',
+      async: true,
+    },
+  ],
 };
 
 export default config;
diff --git a/docusaurus-docs/graphql_versioned_docs/version-v24.1/admin/admin-api.md b/docusaurus-docs/graphql_versioned_docs/version-v24.1/admin/admin-api.md
@@ -806,7 +806,7 @@ Here are the important types, queries, and mutations from the `admin` schema.
 You'll notice that the `/admin` schema is very much the same as the schemas generated by Dgraph GraphQL.
 
 * The `health` query lets you know if everything is connected and if there's a schema currently being served at `/graphql`.
-* The `state`  query returns the current state of the cluster and group membership information. For more information about `state` see [here](/admin/dgraph-zero#more-about-the-state-endpoint).
+* The `state`  query returns the current state of the cluster and group membership information. 
 * The `config` query returns the configuration options of the cluster set at the time of starting it.
 * The `getGQLSchema` query gets the current GraphQL schema served at `/graphql`, or returns null if there's no such schema.
 * The `updateGQLSchema` mutation allows you to change the schema currently served at `/graphql`.
diff --git a/docusaurus-docs/graphql_versioned_docs/version-v24.1/admin/index.md b/docusaurus-docs/graphql_versioned_docs/version-v24.1/admin/index.md
@@ -28,25 +28,6 @@ When you start Dgraph, two GraphQL endpoints are served.
 
 At `/graphql` you'll find the GraphQL API for the types you've added.  That's what your app would access and is the GraphQL entry point to Dgraph.  If you need to know more about this, see the [quick start](https://dgraph.io/docs/graphql/quick-start/) and [schema docs](https://dgraph.io/docs/graphql/schema/).
 
-### /admin
-
-At `/admin` you'll find an admin API for administering your GraphQL instance.  The admin API is a GraphQL API that serves POST and GET as well as compressed data, much like the `/graphql` endpoint.
-
-
-* The `health` query lets you know if everything is connected and if there's a schema currently being served at `/graphql`.
-* The `state`  query returns the current state of the cluster and group membership information. For more information about `state` see [here](/admin/dgraph-zero#more-about-the-state-endpoint).
-* The `config` query returns the configuration options of the cluster set at the time of starting it.
-* The `getGQLSchema` query gets the current GraphQL schema served at `/graphql`, or returns null if there's no such schema.
-* The `updateGQLSchema` mutation allows you to change the schema currently served at `/graphql`.
-
-## Enterprise features
-
-Enterprise Features like ACL, Backups and Restore are also available using the GraphQL API at `/admin` endpoint.
-
-* [ACL](/admin/enterprise-features/access-control-lists#accessing-secured-dgraph)
-* [Backups](/admin/admin-tasks/binary-backups#create-a-backup)
-* [Restore](/admin/admin-tasks/binary-backups#online-restore)
-
 ## First start
 
 On first starting with a blank database:
diff --git a/docusaurus-docs/graphql_versioned_docs/version-v24.1/graphql-dql/graphql-dql-schema.md b/docusaurus-docs/graphql_versioned_docs/version-v24.1/graphql-dql/graphql-dql-schema.md
@@ -157,7 +157,7 @@ In particular, you can
 - use Dgraph DQL mutations but also Dgraph's [import tools](/migration/import-data) to populate the graph after you have deployed a GraphQL Schema. See [GraphQL data loading](/graphql/graphql-dql/graphql-data-loading)
 - use DQL to query the graph in the context of authorization rules and custom resolvers.
 - add knowledge to your graph such as meta-data, score, annotations, ...,  but also relationships or relationships attributes (facets) that could be the result of similarity computation, threat detection a.s.o. The added data could be hidden from your GraphQL API clients but be available to logic written with DQL clients.
-- break things using DQL: DQL is powerful and is bypassing constraints expressed in the GraphQL schema. You can for example delete a node predicate that is mandatory in the GraphQL API! Hopefully there are ways to secure who can read/write/delete predicates. ( see the [ACL](/admin/enterprise-features/access-control-lists/)) section.
+- break things using DQL: DQL is powerful and is bypassing constraints expressed in the GraphQL schema. You can for example delete a node predicate that is mandatory in the GraphQL API! Hopefully there are ways to secure who can read/write/delete predicates. ( see the [ACL](/admin/admin-tasks/user-management-access-control)) section.
 - fix things using DQL: this is especially useful when doing GraphQL Schema updates which require some [data migrations](/graphql/graphql-dql/graphql-data-migration). 
 
 
diff --git a/docusaurus-docs/graphql_versioned_docs/version-v24.1/security/index.md b/docusaurus-docs/graphql_versioned_docs/version-v24.1/security/index.md
@@ -47,7 +47,7 @@ You can use any authentication method that is capable of generating such JWT tok
 
 
 ### ACL
-Note that another token may be needed to access the system if ACL security is also enabled. See the [ACLs](/admin/enterprise-features/access-control-lists/) section for details. The ACLs are a separate security mechanism.
+Note that another token may be needed to access the system if ACL security is also enabled. See the [ACLs](/installation/configuration/enable-acl) section for details. The ACLs are a separate security mechanism.
 
 ### JWT Claims
 

Original file line number	Diff line number	Diff line change
`@@ -172,7 +172,7 @@ This JSON file can be loaded into Dgraph using the programmatic clients.`
`172`	`172`	`}`
`173`	`173`	```
`174`	`174`	`:::note`
`175`		`-To reuse existing integer IDs from a CSV file as UIDs in Dgraph, use Dgraph Zero's [assign endpoint](/admin/dgraph-zero) before loading data to allocate a range of UIDs that can be safely assigned.`
	`175`	`+To reuse existing integer IDs from a CSV file as UIDs in Dgraph, use Dgraph Zero's [assign endpoint](/admin/admin-endpoints) before loading data to allocate a range of UIDs that can be safely assigned.`
`176`	`176`	`:::`
`177`	`177`
`178`	`178`	`4. Paste the output in the Mutate tab of Console in Ratel, and click Run to import data.`