feat: add permissions docs page (#611)

* feat: add permissions docs page

* fix: update organization roles table

* fix: increase clarity of differences between the different roles

* chore: update yarn lock with new updates

* chore: update role capabilities for production active scenario

docs/essentials/organizations.md

@@ -66,15 +66,12 @@ There are three main roles in DevCycle:
 
 The table below displays the built-in roles and their associated permissions:
 
-| Permission                    | Owner | Publisher | Member | Granular Owner<sup>1</sup> |
-| ----------------------------- | :---: | :-------: | :----: | :------------------------: |
-| Add Team Members              |  ✅   |    ✅     |   ✅   |             ✅             |
-| Edit Team Member Roles        |  ✅   |           |        |             ✅             |
-| Modify Features in Production |  ✅   |    ✅     |        |                            |
-
-> _<sup>1</sup> Granular (by environment) Roles & Permissions are for Business/Enterprise Customers only. Contact our team for details._
-
-
+| Permission                    | Owner | Publisher | Member |
+| ----------------------------- | :---: | :-------: | :----: |
+| Add Team Members              |  ✅   |    ✅     |   ✅   |
+| Remove Team Members           |  ✅   |           |        |
+| Edit Team Member Roles        |  ✅   |           |        |
+| Modify Features in Production |  ✅   |    ✅     |        |
 
 **Assigning Roles**
 

docs/extras/permissions/_category_.yml

@@ -0,0 +1,2 @@
+label: 'Permissions'
+position: 12

docs/extras/permissions/permissions.md

@@ -0,0 +1,60 @@
+---
+title: Permissions
+sidebar_position: 1
+---
+
+# Permissions
+
+At DevCycle, our primary goal for permissions is to protect production. We've designed our permissions to be lightweight, straightforward and simple while ensuring production is protected.
+
+Specifically, we offer Permissions Gating to protect Environments which are marked as "production" from unauthorized changes. This allows Organizations to manage which users can modify the Targeting Status, Rules and served Variations in a production Environment that may impact their end users.
+
+Permissions can be enabled for Organizations on our Business or Enterprise plans. Please contact our [support](mailto:support@devcycle.com) team to get started.
+
+:::info
+Permissions enforcement will apply to all Projects and Production-type Environments within your Organization.
+:::
+
+## What Can Users Do?
+
+To ensure usability, all users are able to make any edits to a Feature when production targeting isn't enabled. Permissions Gating and its protections come into play when production targeting is either enabled or a user is attempting to enable production.
+
+See below for the full details on what each user role can do when permissions are enabled.
+
+### Members
+
+#### Can ✅
+
+- Configure Development and Staging Environments
+- Configure **Inactive** Production Environments
+
+#### Cannot ❌
+
+- Enable or Disable Production Environments Targeting
+- Configure **Active** Production Environments
+- When Production is **Active**, Configure Variables and Variations
+- Manage Roles of all Users in the Organization
+
+### Publishers
+
+Everything **Members** can do, plus
+
+#### Can ✅
+
+- Enable or Disable Production Environments Targeting
+- Configure **Active** Production Environments
+- When Production is **Active**, Configure Variables and Variations
+
+#### Cannot ❌
+
+- Manage Roles of all Users in the Organization
+
+### Owners
+
+Everything **Publishers** can do, plus
+
+#### Can ✅
+
+- Manage Roles of all Users in the Organization
+
+For more information, check out the [Organization Roles](/essentials/organizations#organization-roles) documentation.