Merge pull request #416 from hashicorp/RK/HCP-EU

[WIP] Getting the HCP EU documentation ready to go

Author: rkoron007

content/terraform-docs-agents/v1.24.x/docs/cloud-docs/agents/agent-pools.mdx

@@ -18,7 +18,7 @@ Terraform Enterprise does not support Stacks. You can only scope agent pools to
 
 Managing agent pools requires the following permissions:
 
-- You must have the [**Manage Agent Pools**](/terraform/cloud-docs/users-teams-organizations/permissions#manage-agent-pools) permission in your organization to manage an organization's agents.
+- You must have the [**Manage Agent Pools**](/terraform/cloud-docs/users-teams-organizations/permissions/organization#manage-agent-pools) permission in your organization to manage an organization's agents.
 - You must have **Admin** access to a workspace or Stack before you can change its execution mode to use an agent pool.
 
 Refer to [Permissions](/terraform/cloud-docs/users-teams-organizations/permissions) in the HCP Terraform documentation for details.

content/terraform-docs-common/data/cloud-docs-nav-data.json

@@ -29,6 +29,10 @@
     "title": "Migrate to HCP Terraform",
     "path": "migrate"
   },
+  {
+    "title": "Use HCP Terraform in Europe",
+    "path": "europe"
+  },
   {
     "title": "Manage access and organizations",
     "routes": [
@@ -73,16 +77,21 @@
         ]
       },
       {
-  "title": "Permissions",
-        "path": "users-teams-organizations/permissions"
+        "title": "Set permissions",
+        "routes": [
+          {"title": "Overview","path": "users-teams-organizations/permissions"},
+          {"title": "Set permissions","path": "users-teams-organizations/permissions/set-permissions"},
+          { "title": "Organization permissions", "path": "users-teams-organizations/permissions/organization" },
+          { "title": "Project permissions", "path": "users-teams-organizations/permissions/project" },
+          { "title": "Workspace permissions", "path": "users-teams-organizations/permissions/workspace" }
+        ]
       },
-
       {
-  "title": "Two-factor authentication",
+        "title": "Two-factor authentication",
         "path": "users-teams-organizations/2fa"
       },
       {
-  "title": "API tokens",
+        "title": "API tokens",
         "path": "users-teams-organizations/api-tokens"
       },
       {

content/terraform-docs-common/docs/cloud-docs/api-docs/configuration-versions.mdx

@@ -44,7 +44,7 @@ description: >-
 
 A configuration version (`configuration-version`) is a resource used to reference the uploaded configuration files on a workspace. It is associated with the run to use the uploaded configuration files for performing the plan and apply.
 
-You need read runs permission to list and view configuration versions for a workspace, and you need queue plans permission to create new configuration versions. Refer to the [permissions](/terraform/cloud-docs/users-teams-organizations/permissions#general-workspace-permissions) documentation for more details.
+You need read runs permission to list and view configuration versions for a workspace, and you need queue plans permission to create new configuration versions. Refer to the [permissions](/terraform/cloud-docs/users-teams-organizations/permissions/workspace) documentation for more details.
 
 [permissions-citation]: #intentionally-unused---keep-for-maintainers
 

content/terraform-docs-common/docs/cloud-docs/api-docs/hold-your-own-key/configurations.mdx

@@ -41,7 +41,7 @@ tfc_only: true
 
 @include 'tfc-package-callouts/hyok.mdx'
 
-Hold your own key (HYOK) lets you authenticate a key management system with HCP Terraform to encrypt HCP Terraform state and plan data with a key that you provide and control.
+Hold your own key (HYOK) lets you authenticate a key management system with HCP Terraform to encrypt workspace state and plan data with a key that you provide and control.
 
 HCP Terraform lets you configure multiple HYOK configurations for an
 organization. Each HYOK configuration corresponds to a single key in a

content/terraform-docs-common/docs/cloud-docs/api-docs/organization-memberships.mdx

@@ -52,7 +52,7 @@ You can invite users who already have an account, as well as new users. If the u
 | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
 | `:organization_name` | The name of the organization the user will be invited to join. The inviting user must have permission to manage organization memberships. |
 
--> **Note:** Organization membership management is restricted to members of the owners team, the owners [team API token](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens), the [organization API token](/terraform/cloud-docs/users-teams-organizations/api-tokens#organization-api-tokens), and users or teams with one of the [Team Management](/terraform/cloud-docs/users-teams-organizations/permissions#team-management-permissions) permissions.
+-> **Note:** Organization membership management is restricted to members of the owners team, the owners [team API token](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens), the [organization API token](/terraform/cloud-docs/users-teams-organizations/api-tokens#organization-api-tokens), and users or teams with one of the [Team Management](/terraform/cloud-docs/users-teams-organizations/permissions/organization#team-permissions) permissions.
 
 [permissions-citation]: #intentionally-unused---keep-for-maintainers
 
@@ -194,7 +194,7 @@ This endpoint supports pagination [with standard URL query parameters](/terrafor
 | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `q`              | **Optional.** A search query string. Organization memberships are searchable by user name and email.                                                                                          |
 | `filter[status]` | **Optional.** If specified, restricts results to those with the matching status value. Valid values are `invited` and `active`.                                                               |
-| `filter[email]`  | **Optional.** If specified, restricts results to those with a matching user email address. If multiple comma separated values are specified, results matching any of the values are returned. | 
+| `filter[email]`  | **Optional.** If specified, restricts results to those with a matching user email address. If multiple comma separated values are specified, results matching any of the values are returned. |
 | `page[number]`   | **Optional.** If omitted, the endpoint will return the first page.                                                                                                                            |
 | `page[size]`     | **Optional.** If omitted, the endpoint will return 20 users per page.                                                                                                                         |
 

content/terraform-docs-common/docs/cloud-docs/api-docs/private-registry/gpg-keys.mdx

@@ -40,7 +40,7 @@ description: >-
 
 These endpoints are only relevant to private providers. When you [publish a private provider](/terraform/cloud-docs/registry/publish-providers) to the HCP Terraform private registry, you must upload the public key of the GPG key-pair that you used to sign the release. The HCP Terraform registry supports RSA or DSA formatted GPG keys. Refer to [Preparing and adding a signing key](/terraform/registry/providers/publishing#preparing-and-adding-a-signing-key) for more details.
 
-You need [owners team](/terraform/cloud-docs/users-teams-organizations/permissions#organization-owners) or [Manage Private Registry](/terraform/cloud-docs/users-teams-organizations/permissions#manage-private-registry) permissions to add, update, or delete GPG keys in a private registry.
+You need [owners team](/terraform/cloud-docs/users-teams-organizations/permissions/organization#organization-owners) or [Manage Private Registry](/terraform/cloud-docs/users-teams-organizations/permissions/organization#manage-private-registry) permissions to add, update, or delete GPG keys in a private registry.
 
 ## List GPG Keys
 

content/terraform-docs-common/docs/cloud-docs/api-docs/private-registry/provider-versions-platforms.mdx

@@ -41,7 +41,7 @@ description: >-
 These endpoints are only relevant to private providers. When you [publish a private provider](/terraform/cloud-docs/registry/publish-providers) to the HCP Terraform private registry, you must also create at least one version and at least one platform for that version before consumers can use the provider in configurations. Unlike the public Terraform Registry, the private registry does not automatically upload new releases. You must manually add new provider versions and the associated release files.
 
 
-All members of an organization can view and use both public and private providers, but you need [owners team](/terraform/cloud-docs/users-teams-organizations/permissions#organization-owners) or [Manage Private Registry](/terraform/cloud-docs/users-teams-organizations/permissions#manage-private-registry) permissions to add, update, or delete provider versions and platforms in private registry.
+All members of an organization can view and use both public and private providers, but you need [owners team](/terraform/cloud-docs/users-teams-organizations/permissions/organization#organization-owners) or [Manage Private Registry](/terraform/cloud-docs/users-teams-organizations/permissions/organization#manage-private-registry) permissions to add, update, or delete provider versions and platforms in private registry.
 
 ## Create a Provider Version
 

content/terraform-docs-common/docs/cloud-docs/api-docs/private-registry/providers.mdx

@@ -41,7 +41,7 @@ description: >-
 You can add publicly curated providers from the [Terraform Registry](https://registry.terraform.io/) and custom, private providers to your HCP Terraform private registry. The private registry stores a pointer to public providers so that you can view their data from within HCP Terraform. This lets you clearly designate all of the providers that are recommended for the organization and makes them centrally accessible.
 
 
-All members of an organization can view and use both public and private providers, but you need [owners team](/terraform/cloud-docs/users-teams-organizations/permissions#organization-owners) or [Manage Private Registry](/terraform/cloud-docs/users-teams-organizations/permissions#manage-private-registry) permissions to add, update, or delete them them in private registry.
+All members of an organization can view and use both public and private providers, but you need [owners team](/terraform/cloud-docs/users-teams-organizations/permissions/organization#organization-owners) or [Manage Private Registry](/terraform/cloud-docs/users-teams-organizations/permissions/organization#manage-private-registry) permissions to add, update, or delete them them in private registry.
 
 ## HCP Terraform Registry Implementation
 

content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks.mdx

@@ -50,7 +50,7 @@ Refer to [run tasks Integration](/terraform/cloud-docs/api-docs/run-tasks/run-ta
 
 ## Required Permissions
 
-To interact with run tasks on an organization, you need the [Manage Run Tasks permission](/terraform/cloud-docs/users-teams-organizations/permissions#manage-run-tasks). To associate or dissociate run tasks in a workspace, you need the [Manage Workspace Run Tasks permission](/terraform/cloud-docs/users-teams-organizations/permissions#general-workspace-permissions) on that particular workspace.
+To interact with run tasks on an organization, you need the [Manage Run Tasks permission](/terraform/cloud-docs/users-teams-organizations/permissions/organization#manage-run-tasks). To associate or dissociate run tasks in a workspace, you need the [Manage Workspace Run Tasks permission](/terraform/cloud-docs/users-teams-organizations/permissions/workspace#manage-workspace-run-tasks) on that particular workspace.
 
 [permissions-citation]: #intentionally-unused---keep-for-maintainers
 
@@ -60,7 +60,7 @@ To interact with run tasks on an organization, you need the [Manage Run Tasks pe
 
 | Parameter            | Description                                                                                                                                                                                                                     |
 | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `:organization_name` | The organization to create a run task in. The organization must already exist in HCP Terraform, and the token authenticating the API request must have [owner permission](/terraform/cloud-docs/users-teams-organizations/permissions). |
+| `:organization_name` | The organization to create a run task in. The organization must already exist in HCP Terraform, and the token authenticating the API request must have [owner permission](/terraform/cloud-docs/users-teams-organizations/permissions/organization#organization-owners). |
 
 [permissions-citation]: #intentionally-unused---keep-for-maintainers
 

content/terraform-docs-common/docs/cloud-docs/api-docs/variable-sets.mdx

@@ -41,7 +41,7 @@ A [variable set](/terraform/cloud-docs/variables#scope) is a resource that allow
 
 Projects and organizations can both own variable sets. The owner of a variable set can determine the precedence of that set. Refer to [**Manage variable sets**](/terraform/cloud-docs/variables/managing-variables#permissions) for more details on variable set permissions.
 
-To view the variables applied from a variable set on a particular workspace, you must have [**Read** variables permission](/terraform/cloud-docs/users-teams-organizations/permissions#general-workspace-permissions) on that workspace.
+To view the variables applied from a variable set on a particular workspace, you must have [**Read** variables permission](/terraform/cloud-docs/users-teams-organizations/permissions/workspace) on that workspace.
 
 ## Create a Variable Set