fix(docs): repair 7 broken internal links in organizations and global volume docs

docs.json

@@ -2008,6 +2008,26 @@
       "source": "/sdk/whats-changed",
       "destination": "/sdk/migrate-from-flash",
       "permanent": true
+    },
+    {
+      "source": "/organizations/billing",
+      "destination": "/organizations/orgs-billing"
+    },
+    {
+      "source": "/organizations/roles",
+      "destination": "/organizations/org-roles"
+    },
+    {
+      "source": "/organizations/groups",
+      "destination": "/organizations/orgs-groups"
+    },
+    {
+      "source": "/organizations/migrate-from-teams",
+      "destination": "/organizations/orgs-access"
+    },
+    {
+      "source": "/storage/globalvolume-pods",
+      "destination": "/storage/globalvolume/globalvolume-pods"
     }
   ],
   "description": "Developer documentation for building, deploying, and scaling AI applications on Runpod.",

organizations/orgs-overview.mdx

@@ -7,7 +7,7 @@ description: "Manage enterprise GPU workloads with centralized resource ownershi
 Organizations are Runpod's enterprise account model, designed for teams that need centralized resource ownership, billing, and access control. Unlike Teams, an organization is a first-class entity that owns all resources independent of any individual member, including compute, storage, secrets, and templates.
 
 <Note>
-Organizations are currently in beta. Runpod provisions organization accounts and enables them for your account. If you're an existing Team account customer, see [Migrate from Teams](/organizations/migrate-from-teams).
+Organizations are currently in beta. Runpod provisions organization accounts and enables them for your account. If you're an existing Team account customer, see [Access](/organizations/orgs-access) for how Team members join an organization.
 </Note>
 
 ## How Organizations differ from Teams
@@ -30,10 +30,10 @@ Organizations and Teams are mutually exclusive. Accepting an organization invita
 
 **Membership:** A user can belong to at most one organization. Joining an organization is permanent and mutually exclusive with Team membership. There is no path back to a Team account once you join.
 
-**Roles:** Every member is assigned one of four built-in roles: admin, billing, dev, or basic. There is no owner role; admin is the highest level. Roles control what a member can create, manage, or view across compute, billing, and org settings. See [Roles](/organizations/roles) for the full permissions matrix.
+**Roles:** Every member is assigned one of four built-in roles: admin, billing, dev, or basic. There is no owner role; admin is the highest level. Roles control what a member can create, manage, or view across compute, billing, and org settings. See [Roles](/organizations/org-roles) for the full permissions matrix.
 
-**Groups:** Groups are the social unit within an organization. They are leaderless and additive: a member can belong to zero or many groups simultaneously. Only org admins can manage group membership. See [Groups](/organizations/groups).
+**Groups:** Groups are the social unit within an organization. They are leaderless and additive: a member can belong to zero or many groups simultaneously. Only org admins can manage group membership. See [Groups](/organizations/orgs-groups).
 
-**Billing:** Organizations are billed on a post-paid invoice model. Usage accrues throughout the month and is invoiced by Runpod's finance team. There is no credit balance, credit top-up, credit code redemption, or autopay. All members can view their own usage in Billing Explorer; org admins can view any member's usage. See [Billing](/organizations/billing).
+**Billing:** Organizations are billed on a post-paid invoice model. Usage accrues throughout the month and is invoiced by Runpod's finance team. There is no credit balance, credit top-up, credit code redemption, or autopay. All members can view their own usage in Billing Explorer; org admins can view any member's usage. See [Billing](/organizations/orgs-billing).
 
 **SSH keys:** Each org member manages their SSH keys on the [Credentials page](https://console.runpod.io/user/credentials?tab=ssh-key).

storage/globalvolume/overview.mdx

@@ -32,14 +32,14 @@ The volume appears in your Storage list with the type set to **Global**. Storage
 
 A global volume mounts automatically at startup. The mount path depends on where you're using it:
 
-- **Pods:** defaults to `/workspace`, or `/workspace-global` when a network volume is also attached. See [Global volumes for Pods](/storage/globalvolume-pods#mount-paths) for details.
+- **Pods:** defaults to `/workspace`, or `/workspace-global` when a network volume is also attached. See [Global volumes for Pods](/storage/globalvolume/globalvolume-pods#mount-paths) for details.
 - **Serverless:** always mounts at `/runpod-volume`. See [Global volumes for Serverless](/storage/globalvolume/globalvolume-serverless#mount-path) for details.
 
 ## Migrate data from a network volume
 
 If you have data on a network volume that you want to move to a global volume, you can use `rsync`. When both volumes are attached to a Pod without a custom mount path, the network volume is at `/workspace` and the global volume is at `/workspace-global`. Verify your paths in the Pod's **Console** tab before running the command.
 
-1. Deploy a Pod with both your network volume and global volume attached (see [Attach a global volume to a Pod](/storage/globalvolume-pods#attach-a-global-volume-to-a-pod)).
+1. Deploy a Pod with both your network volume and global volume attached (see [Attach a global volume to a Pod](/storage/globalvolume/globalvolume-pods#attach-a-global-volume-to-a-pod)).
 2. Run the following command from the Pod's **Console** tab:
 
 ```bash
@@ -88,7 +88,7 @@ Global volumes use object-backed storage, not a fully POSIX compliant file syste
 
 ## Next steps
 
-- [Global volumes for Pods](/storage/globalvolume-pods)
+- [Global volumes for Pods](/storage/globalvolume/globalvolume-pods)
 - [Global volumes for Serverless](/storage/globalvolume/globalvolume-serverless)
 - [Manage network volumes](/storage/network-volumes)
 - [Use the S3-compatible API](/storage/s3-api)