Environment permissions to GA (#5826)

## What are you changing in this pull request and why?

Making environment permissions GA
Moves from `secure` to `managed access`
Added redirects
Added to sidebar

## Checklist
<!--
Uncomment when publishing docs for a prerelease version of dbt:
- [ ] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
-->
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
- [ ] For [docs
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning),
review how to [version a whole
page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
and [version a block of
content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):
- [ ] Add/remove page in `website/sidebars.js`
- [ ] Provide a unique filename for new pages
- [ ] Add an entry for deleted pages in `website/vercel.json`
- [ ] Run link testing locally with `npm run build` to update the links
that point to deleted pages

website/docs/docs/cloud/secure/environment-permissions-setup.md → website/docs/docs/cloud/manage-access/environment-permissions-setup.md

@@ -7,14 +7,6 @@ pagination_next: null
 pagination_prev: null
 ---
 
-# Set up environment-level permissions <Lifecycle status='beta' />
-
-:::note
-
-This is a beta feature available to select dbt Cloud Enterprise customers. If you are interested in beta testing this feature, please contact your account manager.
-
-:::
-
 To set up and configure environment-level permissions, you must have write permissions to the **Groups & Licenses** settings of your dbt Cloud account. For more information about roles and permissions, check out [User permissions and licenses](/docs/cloud/manage-access/seats-and-users).
 
 Environment-level permissions are not the same as account-level [role-based access control (RBAC)](/docs/cloud/manage-access/about-user-access#role-based-access-control) and are configured separately from those workflows.
@@ -53,7 +45,7 @@ If you select a permission set that is not supported, the environment permission
 
 ## User experience
 
-Users with permissions to the environment will see all capabilities assigned to their role. The environment-level permissions are `write` or `read-only` access. This feature does not currently support determining which features in the environment are accessible. For more details on what can and can not be done with environment-level permissions, refer to [About environment-permissions](/docs/cloud/secure/environment-permissions).
+Users with permissions to the environment will see all capabilities assigned to their role. The environment-level permissions are `write` or `read-only` access. This feature does not currently support determining which features in the environment are accessible. For more details on what can and can not be done with environment-level permissions, refer to [About environment-permissions](/docs/cloud/manage-access/environment-permissions).
 
 For example, here is an overview of the **Jobs** section of the environment page if a user has been granted access:
 

website/docs/docs/cloud/secure/environment-permissions.md → website/docs/docs/cloud/manage-access/environment-permissions.md

@@ -7,17 +7,9 @@ pagination_next: null
 pagination_prev: null
 ---
 
-# About environment-level permissions <Lifecycle status='beta' />
-
-:::note
-
-This is a beta feature available to select dbt Cloud Enterprise customers. If you are interested in beta testing this feature, please contact your account manager.
-
-:::
-
 Environment-level permissions give dbt Cloud admins the ability to grant write permission to groups and service tokens for specific [environment types](/docs/dbt-cloud-environments) within a project. Granting access to an environment give users access to all environment-level write actions and resources associated with their assigned roles. For example, users with a Developer role can create and run jobs within the environment(s) they have access to. For all other environments, those same users will have read-only access. 
 
-For configuration instructions, check out the [setup page](/docs/cloud/secure/environment-permissions-setup).
+For configuration instructions, check out the [setup page](/docs/cloud/manage-access/environment-permissions-setup).
 
 ## Current limitations
 
@@ -85,4 +77,4 @@ If the user has the same roles across projects, you can apply environment access
 
 
 ## Related docs
--[Environment-level permissions setup](/docs/cloud/secure/environment-permissions-setup)
+-[Environment-level permissions setup](/docs/cloud/manage-access/environment-permissions-setup)

website/sidebars.js

@@ -92,7 +92,18 @@ const sidebarSettings = {
                     "docs/cloud/manage-access/enterprise-permissions",
                   ],
                 },
-
+                {
+                  type: "category",
+                  label: "Environment permissions",
+                  link: {
+                    type: "doc",
+                    id: "docs/cloud/manage-access/environment-permissions",
+                  },
+                  items: [
+                    "docs/cloud/manage-access/environment-permissions",
+                    "docs/cloud/manage-access/environment-permissions-setup",
+                  ],
+                },
                 {
                   type: "category",
                   label: "Single sign-on and Oauth",

website/vercel.json

@@ -2,6 +2,16 @@
   "cleanUrls": true,
   "trailingSlash": false,
   "redirects": [
+    {
+      "source":  "docs/cloud/secure/environment-permissions",
+      "destination":  "docs/cloud/manage-access/environment-permissions",
+      "permanent": true
+    },
+    {
+      "source":  "docs/cloud/secure/environment-permissions-setup",
+      "destination": "docs/cloud/manage-access/environment-permissions-setup",
+      "permanent": true
+    },
     {
       "source": "/docs/dbt-versions/core-upgrade/upgrading-to-dbt-utils-v1.0.md",
       "destination": "/docs/dbt-versions/core-upgrade/Older%20versions/upgrading-to-dbt-utils-v1.0.md",