Merge pull request #375 from hashicorp/RK/Module-management-change-requests

Author: rkoron007

website/data/cloud-docs-nav-data.json

@@ -196,8 +196,18 @@
         "title": "Create tags",
         "path": "workspaces/tags"
       },
-      { "title": "Explorer", "path": "workspaces/explorer" },
       { "title":  "Browse workspaces", "path":  "workspaces/browse"},
+      { "title": "Explorer", "path": "workspaces/explorer" },
+      {
+        "title": "Change requests",
+        "routes": [
+          { "title": "Overview", "path": "workspaces/change-requests" },
+          {
+            "title": "Manage change requests",
+            "path": "workspaces/change-requests/manage"
+          }
+        ]
+      },
       {
         "title": "Terraform Configurations",
         "path": "workspaces/configurations"
@@ -297,7 +307,14 @@
     "title": "Users, Teams, Organizations",
     "routes": [
       { "title": "Users", "path": "users-teams-organizations/users" },
-      { "title": "Teams", "path": "users-teams-organizations/teams" },
+    {
+        "title": "Teams",
+        "routes": [
+          {"title": "Overview","path": "users-teams-organizations/teams"},
+          { "title": "Manage teams", "path": "users-teams-organizations/teams/manage" },
+          { "title": "Notifications", "path": "users-teams-organizations/teams/notifications" }
+        ]
+      },
       {
         "title": "Organizations",
         "routes": [

website/docs/cloud-docs/api-docs/project-team-access.mdx

@@ -44,9 +44,11 @@ description: >-
 
 The team access APIs are used to associate a team to permissions on a project. A single `team-project` resource contains the relationship between the Team and Project, including the privileges the team has on the project.
 
--> **Note**: A `team-project` resource represents a team's _local_ permissions on a specific project. Teams can also have _organization-level_ permissions that grant access to projects, and HCP Terraform uses whichever access level is higher. (For example: a team with the "manage projects" permission has admin access on all projects, even if their `team-project` on a particular project only grants read access.) For more information, see [Managing Project Access](/terraform/cloud-docs/users-teams-organizations/teams#managing-project-access).
+## Resource permissions
 
-Any member of an organization can view team access relative to their own team memberships, including secret teams of which they are a member. Organization owners and project admins can modify team access or view the full set of secret team accesses. The organization token and the owners team token can act as an owner on these endpoints. ([More about permissions.](/terraform/cloud-docs/users-teams-organizations/permissions))
+A `team-project` resource represents a team's local permissions on a specific project. Teams can also have organization-level permissions that grant access to projects. HCP Terraform uses the more restrictive access level. For example, a team with the **Manage projects** permission enabled has admin access on all projects, even if their `team-project` on a particular project only grants read access. For more information, refer to [Managing Project Access](/terraform/cloud-docs/users-teams-organizations/teams/manage#managing-project-access).
+
+Any member of an organization can view team access relative to their own team memberships, including secret teams of which they are a member. Organization owners and project admins can modify team access or view the full set of secret team accesses. The organization token and the owners team token can act as an owner on these endpoints. Refer to [Permissions](/terraform/cloud-docs/users-teams-organizations/permissions) for additional information.
 
 ## Project Team Access Levels
 | Access Level    | Description                                                                                                                                                      |

website/docs/cloud-docs/api-docs/team-access.mdx

@@ -44,9 +44,11 @@ description: >-
 
 The team access APIs are used to associate a team to permissions on a workspace. A single `team-workspace` resource contains the relationship between the Team and Workspace, including the privileges the team has on the workspace.
 
--> **Note**: A `team-workspace` resource represents a team's _local_ permissions on a specific workspace. Teams can also have _organization-level_ permissions that grant access to workspaces, and HCP Terraform uses whichever access level is higher. (For example: a team with the "manage workspaces" permission has admin access on all workspaces, even if their `team-workspace` on a particular workspace only grants read access.) For more information, see [Managing Workspace Access](/terraform/cloud-docs/users-teams-organizations/teams#managing-workspace-access).
+## Resource permissions
 
-Any member of an organization can view team access relative to their own team memberships, including secret teams of which they are a member. Organization owners and workspace admins can modify team access or view the full set of secret team accesses. The organization token and the owners team token can act as an owner on these endpoints. ([More about permissions.](/terraform/cloud-docs/users-teams-organizations/permissions))
+A `team-workspace` resource represents a team's local permissions on a specific workspace. Teams can also have organization-level permissions that grant access to workspaces. HCP Terraform uses the more restrictive access level. For example, a team with the "**Manage workspaces** permission enabled has admin access on all workspaces, even if their `team-workspace` on a particular workspace only grants read access. For more information, refer to [Managing Workspace Access](/terraform/cloud-docs/users-teams-organizations/teams/manage#managing-workspace-access).
+
+Any member of an organization can view team access relative to their own team memberships, including secret teams of which they are a member. Organization owners and workspace admins can modify team access or view the full set of secret team accesses. The organization token and the owners team token can act as an owner on these endpoints. Refer to [Permissions](/terraform/cloud-docs/users-teams-organizations/permissions) for additional information.
 
 ## List Team Access to a Workspace
 

website/docs/cloud-docs/api-docs/variable-sets.mdx

@@ -8,7 +8,7 @@ description: >-
 
 A [variable set](/terraform/cloud-docs/workspaces/variables#scope) is a resource that allows you to reuse the same variables across multiple workspaces and projects. For example, you could define a variable set of provider credentials and automatically apply it to a selection of workspaces, all workspaces in a project, or all workspaces in an organization.
 
-You need [`read variables` permission](/terraform/cloud-docs/users-teams-organizations/permissions#general-workspace-permissions) to view the variables for a particular workspace and to view the variable sets in the owning organization. To create or edit variable sets, your team must have [`Manage Workspace` organization access](/terraform/cloud-docs/users-teams-organizations/teams#managing-organization-access).
+You need [**Read** variables permission](/terraform/cloud-docs/users-teams-organizations/permissions#general-workspace-permissions) to view the variables for a particular workspace and to view the variable sets in the owning organization. To create or edit variable sets, your team must have [**Manage all workspaces** organization access](/terraform/cloud-docs/users-teams-organizations/teams/manage#managing-organization-access).
 
 ## Create a Variable Set
 

website/docs/cloud-docs/projects/manage.mdx

@@ -14,7 +14,7 @@ This topic describes how to create and manage projects in HCP Terraform and Terr
 You must have the following permissions to manage projects:
 
 - You must be a member of a team with the **Manage all Projects**  permissions enabled to create a project. Refer to [Organization Permissions](/terraform/cloud-docs/users-teams-organizations/permissions#organization-permissions) for additional information.
-- You must be a member of a team with the **Visible** option enabled under **Visibility** in the organization settings to configure a new team's access to the project. Refer to [Team Visibility](/terraform/cloud-docs/users-teams-organizations/teams#team-visibility) for additional information.
+- You must be a member of a team with the **Visible** option enabled under **Visibility** in the organization settings to configure a new team's access to the project. Refer to [Team Visibility](/terraform/cloud-docs/users-teams-organizations/teams/manage#team-visibility) for additional information.
 - You must be a member of a team with update and delete permissions to be able to update and delete teams respectively.
 
 To delete tags on a project, you must be member of a team with the **Admin** permission group enabled for the project.

website/docs/cloud-docs/users-teams-organizations/organizations/index.mdx

@@ -148,7 +148,7 @@ You can perform the following actions in the **Tags** tab:
 All users in an organization can access the **Teams** page, which displays a list of [teams][] within the organization. 
 
 Organization owners and users with the [include secret teams permission](/terraform/cloud-docs/users-teams-organizations/permissions#include-secret-teams) can:
-  * view all [secret teams](/terraform/cloud-docs/users-teams-organizations/teams#team-visibility)
+  * view all [secret teams](/terraform/cloud-docs/users-teams-organizations/teams/manage#team-visibility)
   * view each team's membership
   * manage team API tokens
 

website/docs/cloud-docs/users-teams-organizations/permissions.mdx

@@ -104,7 +104,7 @@ Admin permissions include the highest level of general permissions for the works
 Workspace admins have all [General Workspace Permissions](#general-workspace-permissions), as well as the ability to do the following tasks:
 
 - Read and write workspace settings. This includes general settings, notification configurations, run triggers, and more.
-- Set or remove workspace permissions for visible teams. Workspace admins cannot view or manage teams that are are [Secret](/terraform/cloud-docs/users-teams-organizations/teams#team-visibility), unless they are also organization owners.
+- Set or remove workspace permissions for visible teams. Workspace admins cannot view or manage teams with the [**Secret**](/terraform/cloud-docs/users-teams-organizations/teams/manage#team-visibility) visibility option enabled unless they are also organization owners.
 - Delete the workspace
   - Depending on the [organization's settings](/terraform/cloud-docs/users-teams-organizations/organizations#general), workspace admins may only be able to delete the workspace if it is not actively managing infrastructure. Refer to [Deleting a Workspace With Resources Under Management](/terraform/cloud-docs/workspaces/settings#deleting-a-workspace-with-resources-under-management) for details.
 
@@ -179,7 +179,7 @@ You can grant the following project permissions to teams on a per-project basis.
 - **Team management:**
   - **None:** — No access to view teams assigned to the project.
   - **Read:** — Allows users to see teams assigned to the project for visible teams.
-  - **Manage:** — _Implies permission to read._ Allows users to set or remove project permissions for visible teams. Project admins can not view or manage [secret teams](/terraform/cloud-docs/users-teams-organizations/teams#team-visibility) unless they are also organization owners.
+  - **Manage:** — _Implies permission to read._ Allows users to set or remove project permissions for visible teams. Project admins can not view or manage [secret teams](/terraform/cloud-docs/users-teams-organizations/teams/manage#team-visibility) unless they are also organization owners.
 
 See [General Workspace Permissions](#general-workspace-permissions)for the complete list of available permissions for a project's workspaces.
 
@@ -197,7 +197,7 @@ Members of teams with "admin" permissions for a project have [General Workspace
 - Delete the project.
 - Create workspaces in the project.
 - Move workspaces into or out of the project. This also requires project admin permissions for the source or destination project.
-- Grant or revoke project permissions for visible teams. Project admins **cannot** view or manage access for teams that are are [Secret](/terraform/cloud-docs/users-teams-organizations/teams#team-visibility), unless those admins are also organization owners.
+- Grant or revoke project permissions for visible teams. Project admins **cannot** view or manage access for teams that are are [Secret](/terraform/cloud-docs/users-teams-organizations/teams/manage#team-visibility), unless those admins are also organization owners.
 
 #### Maintain
 
@@ -321,7 +321,7 @@ Allows members to invite users to the organization, remove users from the organi
 
 This permission grants the ability to view the list of users within the organization, and to view the organization access of other visible teams. It does not permit the creation of teams, the ability to modify the settings of existing teams, or the ability to view secret teams.
 
-In order to modify the membership of a team, a user with Manage Membership permissions must have visibility into the team (i.e. the team must be ["Visible"](/terraform/cloud-docs/users-teams-organizations/teams#team-visibility), or the user must be on the team).
+In order to modify the membership of a team, a user with Manage Membership permissions must have visibility into the team (i.e. the team must be ["Visible"](/terraform/cloud-docs/users-teams-organizations/teams/manage#team-visibility), or the user must be on the team).
 In order to remove a user from the organization, the holder of this permission must have visibility into all of the teams which the user is a member of.
 
 ~> This permission is intended to allow owners of large organizations to delegate membership management to another trusted team, and should be granted to only teams of trusted users. **Assign with caution:** Users with this permission are able to add themselves to any visible team, and inherit the permissions of any visible team.