Restructuring Phase 3 (#492)

src/pages/manage/access-control/endpoint-detection-and-response/crowdstrike-edr.mdx

@@ -59,7 +59,7 @@ Before you start creating and configuring a CrowdStrike integration, ensure that
     The EDR check will apply only to machines in the selected groups and will require a running CrowdStrike agent.
 </Note>
 <Note>
-    You can also use groups [synchronized from your Identity Provider (IdP)](/how-to/idp-sync).
+    You can also use groups [synchronized from your Identity Provider (IdP)](/manage/team/idp-sync).
 </Note>
 
 - Peers that have the CrowdStrike agent installed will be granted access to the network. Peers without the agent will appear

src/pages/manage/access-control/endpoint-detection-and-response/intune-mdm.mdx

@@ -148,7 +148,7 @@ At this stage, specify one or more NetBird groups to which the check should appl
     The MDM check will apply only to machines in the selected groups and will require a running Intune agent.
 </Note>
 <Note>
-    You can also use groups [synchronized from your Identity Provider (IdP)](/how-to/idp-sync).
+    You can also use groups [synchronized from your Identity Provider (IdP)](/manage/team/idp-sync).
 </Note>
 
 Peers that have the Intune agent installed and are compliant will be granted access to the network. Peers without the agent will appear

src/pages/manage/access-control/endpoint-detection-and-response/sentinelone-edr.mdx

@@ -74,7 +74,7 @@ Treat the API token securely and store it safely. You will need both the console
 
 <Note>
     The EDR check will apply only to peers in the selected groups and will require a running SentinelOne agent.
-    You can also use groups [synchronized from your Identity Provider (IdP)](/how-to/idp-sync).
+    You can also use groups [synchronized from your Identity Provider (IdP)](/manage/team/idp-sync).
 </Note>
 
 - Configure the compliance criteria that devices must meet to access your network. These security requirements ensure only healthy, properly configured devices can connect. Select the criteria that align with your organization's security policies:

src/pages/manage/access-control/index.mdx

@@ -6,7 +6,7 @@ NetBird's access control system is built on Zero Trust security principles, ensu
 </p>
 
 <Note>
-    **NEW:** For a visual overview of your access policies and how peers, groups, and their relationships connect, check out the [**Control Center**](https://docs.netbird.io/how-to/control-center) feature in NetBird. The Control Center provides an interactive graph view that makes it easy to understand your network's access structure at a glance.
+    **NEW:** For a visual overview of your access policies and how peers, groups, and their relationships connect, check out the [**Control Center**](https://docs.netbird.io/manage/control-center) feature in NetBird. The Control Center provides an interactive graph view that makes it easy to understand your network's access structure at a glance.
 </Note>
 
 ## Zero-Trust Principles and NetBird
@@ -88,7 +88,7 @@ When a user signs into NetBird on a device (such as a Windows computer using the
 **How peer groups work:**
 
 1. **Manual Creation:** Groups are created explicitly in the NetBird interface
-2. **Setup Key Assignment:** The most common method - when creating a setup key, you specify which groups should be [auto-assigned](https://docs.netbird.io/how-to/register-machines-using-setup-keys#peer-auto-grouping) to any peer that registers with that key
+2. **Setup Key Assignment:** The most common method - when creating a setup key, you specify which groups should be [auto-assigned](https://docs.netbird.io/manage/peers/register-machines-using-setup-keys#peer-auto-grouping) to any peer that registers with that key
 3. **Manual Assignment:** Administrators can also manually assign groups to specific infrastructure peers after they're connected
 
 **What are Setup Keys?**

src/pages/manage/access-control/manage-network-access.mdx

@@ -13,7 +13,7 @@ Watch our Access Control video on YouTube:
 </div>
 
 <Note>
-    For a visual overview of your access policies and network topology, check out the [Control Center](/how-to/control-center), which provides an interactive graph view of peers, groups, and their access relationships.
+    For a visual overview of your access policies and network topology, check out the [Control Center](/manage/control-center), which provides an interactive graph view of peers, groups, and their access relationships.
 </Note>
 
 ## Introduction
@@ -36,7 +36,7 @@ Here are some key attributes of groups:
 - There exists a default group called `All` which cannot be deleted or renamed.
 
 <Note>
-    You can assign groups automatically with the [peer auto-grouping feature](/how-to/register-machines-using-setup-keys#peer-auto-grouping).
+    You can assign groups automatically with the [peer auto-grouping feature](/manage/peers/register-machines-using-setup-keys#peer-auto-grouping).
 </Note>
 
 ### The All Group
@@ -75,7 +75,7 @@ After accessing the `Access Control` > `Policies` tab, click on the `Add policy`
 In the popup, specify connection `Source` and `Destination` groups. You can select existing groups or create new ones by entering a name in the input box.
 
 <Note>
-    We recommend using [identity provider (IdP) integrations](/how-to/idp-sync) to provision your user groups from the IdP.
+    We recommend using [identity provider (IdP) integrations](/manage/team/idp-sync) to provision your user groups from the IdP.
 </Note>
 
 You can limit access to specific protocol and ports by selecting the `Protocol` and providing the port numbers in the `Ports` field.
@@ -109,7 +109,7 @@ You can assign a peer to a group by accessing the `Peers` section. Then, choose
 </p>
 
 <Note>
-    You can assign groups automatically with the [peer auto-grouping feature](/how-to/register-machines-using-setup-keys#peer-auto-grouping).
+    You can assign groups automatically with the [peer auto-grouping feature](/manage/peers/register-machines-using-setup-keys#peer-auto-grouping).
 </Note>
 
 ### Updating Policies

src/pages/manage/access-control/posture-checks/connecting-from-the-office.mdx

@@ -1,5 +1,5 @@
 # Connecting from the office
-A typical scenario administrators have is accessing their office networks remotely. With [Network routes](https://docs.netbird.io/how-to/routing-traffic-to-private-networks), NetBird makes this easy. Still, administrators often want to avoid routing their users’ traffic via NetBird when they are in the office.
+A typical scenario administrators have is accessing their office networks remotely. With [Network routes](https://docs.netbird.io/manage/network-routes/routing-traffic-to-private-networks), NetBird makes this easy. Still, administrators often want to avoid routing their users’ traffic via NetBird when they are in the office.
 To solve this, administrators can leverage the power of [Posture Checks](https://docs.netbird.io/manage/access-control/posture-checks) and create policies that allow connection to the routing peers only if they are outside the office by using
 a [Peer Network Range](/manage/access-control/posture-checks#peer-network-range) posture check with a block action.
 
@@ -51,7 +51,7 @@ We are now ready for the final step of creating the office route.
 
 ### Create a Network Route
 
-Now, let's create a [Network Route](https://docs.netbird.io/how-to/routing-traffic-to-private-networks) that will expose the local office subnet `192.168.1.0/24`,
+Now, let's create a [Network Route](https://docs.netbird.io/manage/network-routes/routing-traffic-to-private-networks) that will expose the local office subnet `192.168.1.0/24`,
 which will be distributed to all peers members of the group `route-users`. In this example, we will be using a routing peer named `router-01`,
 which is a member of the group `route-nodes`, this way, the policy we just created goes into effect, and all peers from the group `route-users` will be able to reach
 `router-01` only if they are not in the office network, due to our posture check.