premium tags appended to enterprise

stirby · stirby · commit 4e5a0959696a · 2024-10-04T23:05:45.000Z
diff --git a/docs/admin/monitoring/notifications/index.md b/docs/admin/monitoring/notifications/index.md
@@ -230,7 +230,7 @@ notification is indicated on the right hand side of this table.
 
 ![User Notification Preferences](../../../images/admin/monitoring/notifications/user-notification-preferences.png)
 
-## Delivery Preferences (enterprise)
+## Delivery Preferences (enterprise) (premium)
 
 Administrators can configure which delivery methods are used for each different
 [event type](#event-types).
diff --git a/docs/admin/networking/port-forwarding.md b/docs/admin/networking/port-forwarding.md
@@ -129,7 +129,7 @@ resource uses a different method of authentication and **is not impacted by the
 template's maximum sharing level**, nor the level of a shared port that points
 to the app.
 
-### Configure maximum port sharing level (enterprise)
+### Configure maximum port sharing level (enterprise) (premium)
 
 Enterprise-licensed template admins can control the maximum port sharing level
 for workspaces under a given template in the template settings. By default, the
diff --git a/docs/admin/users/groups-roles.md b/docs/admin/users/groups-roles.md
@@ -19,7 +19,7 @@ Roles determine which actions users can take within the platform.
 |                                                                 | Auditor | User Admin | Template Admin | Owner |
 | --------------------------------------------------------------- | ------- | ---------- | -------------- | ----- |
 | Add and remove Users                                            |         | ✅         |                | ✅    |
-| Manage groups (enterprise)                                      |         | ✅         |                | ✅    |
+| Manage groups (enterprise) (premium)                            |         | ✅         |                | ✅    |
 | Change User roles                                               |         |            |                | ✅    |
 | Manage **ALL** Templates                                        |         |            | ✅             | ✅    |
 | View **ALL** Workspaces                                         |         |            | ✅             | ✅    |
diff --git a/docs/user-guides/workspace-management.md b/docs/user-guides/workspace-management.md
@@ -88,7 +88,7 @@ manually updated the workspace.
 
 ![Automatic Updates](../images/workspace-automatic-updates.png)
 
-## Bulk operations (enterprise)
+## Bulk operations (enterprise) (premium)
 
 Enterprise admins may apply bulk operations (update, delete, start, stop) in the
 **Workspaces** tab. Select the workspaces you'd like to modify with the
diff --git a/docs/user-guides/workspace-scheduling.md b/docs/user-guides/workspace-scheduling.md
@@ -49,7 +49,7 @@ Workspaces will automatically shut down after a period of inactivity. This can
 be configured at the template level, but is visible in the autostop description
 for your workspace.
 
-## Autostop requirement (enterprise)
+## Autostop requirement (enterprise) (premium)
 
 Enterprise template admins may enforce a required stop for workspaces to apply
 updates or undergo maintenance. These stops ignore any active connections or
@@ -61,7 +61,7 @@ and specified quiet hours (see below).
 > Admins: See the template schedule settings for more information on configuring
 > Autostop Requirement.
 
-### User quiet hours (enterprise)
+### User quiet hours (enterprise) (premium)
 
 User quiet hours can be configured in the user's schedule settings page.
 Workspaces on templates with an autostop requirement will only be forcibly
@@ -99,7 +99,7 @@ Let's say that both are set to 5 hours. When either your workspace autostarts or
 you sign in, you will have confidence that the only condition for shutdown is 5
 hours of inactivity.
 
-## Dormancy (enterprise)
+## Dormancy (enterprise) (premium)
 
 Dormancy automatically deletes workspaces which remain unused for long
 durations. Template admins configure an inactivity period after which your
