TykTechnologies · DavidRollins · Oct 30, 2024 · Oct 31, 2024 · Oct 31, 2024 · Oct 31, 2024
diff --git a/...ed-configuration/manage-multiple-environments/move-apis-between-environments.md b/...ed-configuration/manage-multiple-environments/move-apis-between-environments.md
@@ -61,4 +61,4 @@ The ID you use in with any Dashboard API integrations will change as the documen
 
 ## Use Tyk-Sync
 
-You can also use our new Tyk-Sync tool which allows you to sync your APIs (and Policies) with a Version Control System (VCS). You can then move your APIs between environments. See [Tyk-Sync]({{< ref "/product-stack/tyk-sync/overview" >}}) for more details.
+You can also use our new Tyk-Sync tool which allows you to sync your APIs (and Policies) with a Version Control System (VCS). You can then move your APIs between environments. See [Tyk-Sync]({{< ref "/api-management/automations#synchronize-tyk-environment-with-github-repository" >}}) for more details.
diff --git a/...onfiguration/manage-multiple-environments/move-policies-between-environments.md b/...onfiguration/manage-multiple-environments/move-policies-between-environments.md
@@ -145,4 +145,4 @@ As you can see, under the hood, the policy has been migrated correctly with targ
 
 ## Use Tyk-Sync
 
-You can also use our new Tyk-Sync tool which allows you to sync your Policies (and APIs) with a Version Control System (VCS). You can then move your Policies between environments. See [Tyk-Sync]({{< ref "/product-stack/tyk-sync/overview" >}}) for more details.
+You can also use our new Tyk-Sync tool which allows you to sync your Policies (and APIs) with a Version Control System (VCS). You can then move your Policies between environments. See [Tyk-Sync]({{< ref "/api-management/automations#synchronize-tyk-environment-with-github-repository" >}}) for more details.
diff --git a/tyk-docs/content/api-management/automations.md b/tyk-docs/content/api-management/automations.md
diff --git a/tyk-docs/content/api-management/manage-apis/deploy-apis/deploy-apis-overview.md b/tyk-docs/content/api-management/manage-apis/deploy-apis/deploy-apis-overview.md
@@ -42,7 +42,7 @@ Tyk Sync enables declarative API management and GitOps. With Tyk Sync, you can m
 Usage: Recommended for organizations looking to implement GitOps in API management and have portable API and Policy configurations.
 
 Learn more:
-- [Tyk Sync]({{<ref "/product-stack/tyk-sync/overview">}})
+- [Tyk Sync]({{<ref "/api-management/automations#synchronize-tyk-environment-with-github-repository">}})
 
 ## Tyk Operator
 
@@ -51,7 +51,7 @@ Building on the capabilities of Tyk Sync and GitOps, Tyk Operator provides a pow
 Usage: Recommended for organizations already running Kubernetes and seeking a Kubernetes-native, automated approach to API deployment and management.
 
 Learn more:
-- [Tyk Operator]({{<ref "tyk-operator">}})
+- [Tyk Operator]({{<ref "/api-management/automations#what-is-tyk-operator">}})
 - [Using Tyk Operator to enable GitOps with Tyk]({{<ref "getting-started/key-concepts/gitops-with-tyk">}})
 
 With these flexible deployment options, you can easily design, develop, and deploy APIs in Tyk according to your specific requirements and workflow. Choose the option that best aligns with your needs and integrates smoothly into your API development lifecycle.
diff --git a/tyk-docs/content/apim.md b/tyk-docs/content/apim.md
@@ -16,8 +16,8 @@ Choosing the right one for your organization depends on your specific requiremen
 
 |                                                                                                                                                                                                                                    | [Open Source]({{< ref "apim/open-source" >}})  |   [Self-Managed]({{< ref "tyk-on-premises" >}})      |  [Cloud](https://account.cloud-ara.tyk.io/signup)
 |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-------------------|---------
-| API Gateway Capabilities <br> <ul><li>Rate Limiting</li><li>Authentication</li> <li>API Versioning</li><li>Granular Access Control</li><li>GraphQL</li>  <li>and [much more]({{< ref "apim/open-source" >}})</li></ul> | ✅             |✅	              |✅
-| [Version Control]({{< ref "/product-stack/tyk-sync/overview" >}}) Integration                                                                                                                                                      | -		      |✅	              |✅
+| API Gateway Capabilities <br> <ul><li>Rate Limiting</li><li>Authentication</li> <li>API Versioning</li><li>Granular Access Control</li><li>GraphQL</li>  <li>and [much more]({{< ref "apim/open-source#tyk-open-source" >}})</li></ul> | ✅             |✅	              |✅
+| [Version Control]({{< ref "/api-management/automations#synchronize-tyk-environment-with-github-repository" >}}) Integration                                                                                                                                                      | -		      |✅	              |✅
 | [API Analytics Exporter]({{< ref "tyk-pump" >}})                                                                                                                                                                                   | ✅		      |✅	              |✅	 
 | [Tyk Dashboard]({{< ref "tyk-dashboard" >}})                                                                                                                                                                                       | -	          |✅	              |✅	 
 | [Single Sign On (SSO)]({{< ref "advanced-configuration/integrate/sso" >}})                                                                                                                                                         | -	          |✅	              |✅	      

diff --git a/...t/basic-config-and-security/security/authentication-authorization/basic-auth.md b/...t/basic-config-and-security/security/authentication-authorization/basic-auth.md
@@ -73,7 +73,7 @@ As you can see in the above example, enabling Basic Authentication is as simple
 
 ### Enable basic authentication using Tyk Operator
 
-Please consult the Tyk Operator supporting documentation for an example of how to [enable basic authentication]({{< ref "product-stack/tyk-operator/advanced-configurations/client-authentication#basic-authentication" >}}) with Tyk Operator.
+Please consult the Tyk Operator supporting documentation for an example of how to [enable basic authentication]({{< ref "/api-management/automations#basic-authentication" >}}) with Tyk Operator.
 
 ## Create a Basic Authentication user
 

diff --git a/...asic-config-and-security/security/authentication-authorization/bearer-tokens.md b/...asic-config-and-security/security/authentication-authorization/bearer-tokens.md
@@ -102,4 +102,4 @@ It is possible to provide Tyk with your own custom tokens, this can be achieved
 
 ## Enabling bearer tokens with Tyk Operator
 
-Please consult the Tyk Operator supporting documentation for an example of how to [enable a bearer tokens]({{< ref "product-stack/tyk-operator/advanced-configurations/client-authentication#auth-token-bearer-token" >}}) with Tyk Operator.
+Please consult the Tyk Operator supporting documentation for an example of how to [enable a bearer tokens]({{< ref "/api-management/automations#auth-token-bearer-token" >}}) with Tyk Operator.
diff --git a/...ic-config-and-security/security/authentication-authorization/json-web-tokens.md b/...ic-config-and-security/security/authentication-authorization/json-web-tokens.md
@@ -240,4 +240,4 @@ Several scopes in JWT claim will lead to have several policies applied to a key.
 
 ### JWT authentication with Tyk Operator
 
-Please consult the Tyk Operator supporting documentation for an example of how to [configure JWT authentication]({{< ref "product-stack/tyk-operator/advanced-configurations/client-authentication#jwt" >}}) with Tyk Operator.
+Please consult the Tyk Operator supporting documentation for an example of how to [configure JWT authentication]({{< ref "/api-management/automations#jwt" >}}) with Tyk Operator.
diff --git a/...asic-config-and-security/security/authentication-authorization/multiple-auth.md b/...asic-config-and-security/security/authentication-authorization/multiple-auth.md
@@ -57,4 +57,4 @@ Tyk will chain the auth mechanisms as they appear in the code and will default t
 
 ## Enable Multi (Chained) Authentication with Tyk Operator
 
-Please consult the Tyk Operator supporting documentation for an example of how to enable [multi chained authentication]({{< ref "product-stack/tyk-operator/advanced-configurations/client-authentication#multiple-chained-auth" >}}) with Tyk Operator.
+Please consult the Tyk Operator supporting documentation for an example of how to enable [multi chained authentication]({{< ref "/api-management/automations#multiple-chained-auth" >}}) with Tyk Operator.
diff --git a/...basic-config-and-security/security/authentication-authorization/open-keyless.md b/...basic-config-and-security/security/authentication-authorization/open-keyless.md
@@ -41,4 +41,4 @@ Keyless APIs cannot be selected for [Access Rights]({{< ref "getting-started/cre
 
 ## Tyk Operator Example
 
-Please consult the Tyk Operator supporting documentation for an example of how to configure an API within Tyk Operator for [Open Access]({{< ref "product-stack/tyk-operator/advanced-configurations/client-authentication#keyless-open" >}}).
+Please consult the Tyk Operator supporting documentation for an example of how to configure an API within Tyk Operator for [Open Access]({{< ref "/api-management/automations#keyless-open" >}}).
diff --git a/tyk-docs/content/developer-support/backups/backup-apis-and-policies.md b/tyk-docs/content/developer-support/backups/backup-apis-and-policies.md
@@ -6,7 +6,7 @@ description: "How to backup APIs and Policies with Tyk Dashboard"
 ---
 
 Backing up Tyk APIs and Policies is crucial for ensuring business continuity and data integrity. It safeguards against accidental data loss, system failures or corruption. This provides the opportunity to rollback to a stable state during upgrades or migrations, allowing you to restore configurations to a previous state to prevent disruptions with your API infrastructure.
-If you are using Self Managed deployment then we recommend that you use [Tyk Sync]({{< ref "/product-stack/tyk-sync/overview" >}}) to backup your Tyk APIs and policies. 
+If you are using Self Managed deployment then we recommend that you use [Tyk Sync]({{< ref "/api-management/automations#synchronize-tyk-environment-with-github-repository" >}}) to backup your Tyk APIs and policies. 
 
 ## Export And Restore APIs and Policies
 

diff --git a/tyk-docs/content/frequently-asked-questions/how-to-backup-tyk-cloud-deployment.md b/tyk-docs/content/frequently-asked-questions/how-to-backup-tyk-cloud-deployment.md
@@ -13,4 +13,4 @@ To track changes in Dashboard configurations, please submit a [support ticket](h
 
 #### If there's a configuration error or an unwanted change, can I easily revert to a previous API or Policy configuration? What are the options or best practices for effective rollbacks?
 
-You can configure [Tyk-Sync]({{< ref "/product-stack/tyk-sync/overview" >}}) to synchronise APIs and Policies with any version control system, like GitHub or GitLab and use it to perform roll back. Keys are not synchronised with Tyk Sync.
+You can configure [Tyk-Sync]({{< ref "/api-management/automations#synchronize-tyk-environment-with-github-repository" >}}) to synchronise APIs and Policies with any version control system, like GitHub or GitLab and use it to perform roll back. Keys are not synchronised with Tyk Sync.
diff --git a/tyk-docs/content/getting-started/using-oas-definitions/create-an-oas-api.md b/tyk-docs/content/getting-started/using-oas-definitions/create-an-oas-api.md
@@ -332,4 +332,4 @@ Note that the Gateway will respond with the following error message:
 
 You can make use of Tyk Operator custom resources to configure [Tyk OAS API]({{<ref "getting-started/using-oas-definitions/oas-glossary#tyk-oas-api-definition">}}) in a Kubernetes environment.
 
-In this [tutorial]({{<ref "product-stack/tyk-operator/getting-started/create-an-oas-api">}}) we guide you through the steps to create a new Tyk OAS API using Tyk Operator.
+In this [tutorial]({{<ref "/api-management/automations#set-up-oas-api">}}) we guide you through the steps to create a new Tyk OAS API using Tyk Operator.
diff --git a/tyk-docs/content/plugins/plugin-types/auth-plugins/auth-plugins.md b/tyk-docs/content/plugins/plugin-types/auth-plugins/auth-plugins.md
@@ -66,6 +66,6 @@ See the [supported languages]({{< ref "plugins/supported-languages" >}}) section
 
 Please consult the Tyk Operator supporting documentation for examples of how to configure a Tyk Operator API to use:
 
-- [Go custom authentication plugin]({{< ref "product-stack/tyk-operator/advanced-configurations/client-authentication#custom-plugin-auth-go" >}})
-- [gRPC custom authentication plugin]({{< ref "product-stack/tyk-operator/advanced-configurations/client-authentication#custom-plugin-auth-grpc" >}})
+- [Go custom authentication plugin]({{< ref "/api-management/automations#custom-plugin-auth-go" >}})
+- [gRPC custom authentication plugin]({{< ref "/api-management/automations#custom-plugin-auth-grpc" >}})
 
diff --git a/tyk-docs/content/product-stack/tyk-charts/release-notes/version-1.4.md b/tyk-docs/content/product-stack/tyk-charts/release-notes/version-1.4.md
@@ -150,7 +150,7 @@ Each change log item should be expandable. The first line summarises the changel
 <details>
 <summary>OSS: Simplify Tyk Operator setup with Kubernetes Secret creation</summary>
 
-When you set `operatorSecret.enabled` to `true` in the `tyk-oss` chart, a Kubernetes Secret named `tyk-operator-conf` will be automatically created in the same namespace. This secret is essential for connecting Tyk Operator to the Gateway, enabling seamless management of Tyk API resources. To learn more about setting up Tyk Operator, check out [Tyk Operator installation]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}}).
+When you set `operatorSecret.enabled` to `true` in the `tyk-oss` chart, a Kubernetes Secret named `tyk-operator-conf` will be automatically created in the same namespace. This secret is essential for connecting Tyk Operator to the Gateway, enabling seamless management of Tyk API resources. To learn more about setting up Tyk Operator, check out [Tyk Operator installation]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}}).
 </details>
 </li>
 

diff --git a/tyk-docs/content/product-stack/tyk-charts/release-notes/version-1.5.md b/tyk-docs/content/product-stack/tyk-charts/release-notes/version-1.5.md
@@ -271,14 +271,14 @@ mdcb:
 
 `global.components.operator` added to determine whether the Tyk Operator component should be installed.
 
-This feature adds a dependency on the Tyk Operator to the umbrella charts, facilitating the installation of the Tyk Operator component. Users can now easily install the Tyk Operator component by setting the `global.components.operator` parameter. Note that the Tyk Operator requires `cert-manager` to be installed beforehand. It also expects secret `tyk-operator-conf` is present in the installation namespace. You can enable bootstrapping at `global.components.bootstrap` if you are working on a new installation to have this secret created for you. Refer to the Tyk Operator [installation guide]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}}) for detailed information on pre-requisites.
+This feature adds a dependency on the Tyk Operator to the umbrella charts, facilitating the installation of the Tyk Operator component. Users can now easily install the Tyk Operator component by setting the `global.components.operator` parameter. Note that the Tyk Operator requires `cert-manager` to be installed beforehand. It also expects secret `tyk-operator-conf` is present in the installation namespace. You can enable bootstrapping at `global.components.bootstrap` if you are working on a new installation to have this secret created for you. Refer to the Tyk Operator [installation guide]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}}) for detailed information on pre-requisites.
 
 ```yaml
 global:
   components:
     # operator determines whether Tyk Operator component should be installed or not.
     # Tyk Operator needs cert-manager to be installed beforehand. Make sure that cert-manager is installed.
-    # For further details, please refer to https://tyk.io/docs/tyk-stack/tyk-operator/installing-tyk-operator/
+    # For further details, please refer to https://tyk.io/docs//api-management/automations#install-and-configure-tyk-operator/
     operator: false
 ```
 

diff --git a/tyk-docs/content/product-stack/tyk-charts/release-notes/version-2.1.md b/tyk-docs/content/product-stack/tyk-charts/release-notes/version-2.1.md
@@ -30,7 +30,7 @@ For a comprehensive list of changes, please refer to the detailed [changelog](#C
 <!-- Required. Use the following statement if there are no breaking changes, or explain if there are -->
 This release has no breaking changes.
 
-However, if you are upgrading to [Tyk Operator v1.0]({{<ref "product-stack/tyk-operator/release-notes/operator-1.0.md">}}) using the Helm Chart, please read the [license requirement]({{<ref "product-stack/tyk-operator/release-notes/operator-1.0.md#breaking-changes">}}) and Tyk Operator [installation and upgrade instructions]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}}) carefully.
+However, if you are upgrading to [Tyk Operator v1.0]({{<ref "product-stack/tyk-operator/release-notes/operator-1.0.md">}}) using the Helm Chart, please read the [license requirement]({{<ref "product-stack/tyk-operator/release-notes/operator-1.0.md#breaking-changes">}}) and Tyk Operator [installation and upgrade instructions]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}}) carefully.
 
 <!-- The following "Changed error log messages" section is Optional!
 Instructions: We should mention in the changelog section ALL changes in our application log messages. In case we made such changes, this section should also be added, to make sure the users don't miss this notice among other changelog lines. -->

diff --git a/tyk-docs/content/product-stack/tyk-charts/tyk-control-plane-chart.md b/tyk-docs/content/product-stack/tyk-charts/tyk-control-plane-chart.md
@@ -865,7 +865,7 @@ tyk-dev-portal:
 ### Tyk Operator Configurations
 
 Tyk Operator is a licensed component that requires a valid key for operation. 
-Please refer to the [Tyk Operator Installation Guide]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}})
+Please refer to the [Tyk Operator Installation Guide]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}})
 for detailed information on the installation and upgrade processes. 
 
 Prior to installing Tyk Operator, ensure that a valid license key is provided by setting `global.license.operator` field in values.yaml file. You can set license key via a Kubernetes secret using `global.secrets.useSecretName` field. The secret should contain a key called `OperatorLicense`.
@@ -876,4 +876,4 @@ to `true`.
 All other configurations related to Tyk Operator are available under `tyk-operator` section of `values.yaml` file.
 
 > Tyk Operator needs a cert-manager to be installed. Ensure that cert-manager is installed as described in the
-> official documentation: [Installing Tyk Operator]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}}).
+> official documentation: [Installing Tyk Operator]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}}).
diff --git a/tyk-docs/content/product-stack/tyk-charts/tyk-oss-chart.md b/tyk-docs/content/product-stack/tyk-charts/tyk-oss-chart.md
@@ -496,7 +496,7 @@ To setup other backends for pump, refer to this [document](https://github.com/Ty
 ### Tyk Operator Configurations
 
 Tyk Operator is a licensed component that requires a valid key for operation. 
-Please refer to the [Tyk Operator Installation Guide]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}})
+Please refer to the [Tyk Operator Installation Guide]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}})
 for detailed information on the installation and upgrade processes. 
 
 Prior to installing Tyk Operator, ensure that a valid license key is provided by setting `global.license.operator` field in values.yaml file. You can set license key via a Kubernetes secret using `global.secrets.useSecretName` field. The secret should contain a key called `OperatorLicense`.
@@ -505,4 +505,4 @@ In order to enable installing Tyk Operator along-side Tyk OSS installation, plea
 
 All other configurations related to Tyk Operator are available under `tyk-operator` section of `values.yaml` file.
 
-> Tyk Operator needs a cert-manager to be installed. Ensure that cert-manager is installed as described in the official documentation: [Installing Tyk Operator]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}}).
+> Tyk Operator needs a cert-manager to be installed. Ensure that cert-manager is installed as described in the official documentation: [Installing Tyk Operator]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}}).
diff --git a/tyk-docs/content/product-stack/tyk-charts/tyk-stack-chart.md b/tyk-docs/content/product-stack/tyk-charts/tyk-stack-chart.md
@@ -888,7 +888,7 @@ tyk-dev-portal:
 ### Tyk Operator Configurations
 
 Tyk Operator is a licensed component that requires a valid key for operation. 
-Please refer to the [Tyk Operator Installation Guide]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}})
+Please refer to the [Tyk Operator Installation Guide]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}})
 for detailed information on the installation and upgrade processes. 
 
 Prior to installing Tyk Operator, ensure that a valid license key is provided by setting `global.license.operator` field in values.yaml file. You can set license key via a Kubernetes secret using `global.secrets.useSecretName` field. The secret should contain a key called `OperatorLicense`.
@@ -899,4 +899,4 @@ to `true`.
 All other configurations related to Tyk Operator are available under `tyk-operator` section of `values.yaml` file.
 
 > Tyk Operator needs a cert-manager to be installed. Ensure that cert-manager is installed as described in the
-> official documentation: [Installing Tyk Operator]({{<ref "tyk-stack/tyk-operator/installing-tyk-operator">}}).
+> official documentation: [Installing Tyk Operator]({{<ref "/api-management/automations#install-and-configure-tyk-operator">}}).