Modified following PO Review

Author: Donna-Marie Smith

assets/scss/_content.scss

@@ -185,7 +185,6 @@
     }
 
     >.scribe-video {
-        max-width: 640px;
         width: 100%;
         animation: fadeIn 2s;
 

content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/Admin/studio-authorisation.md

@@ -1,15 +1,15 @@
 ---
 title: "Studio Authorisation"
 linkTitle: "Studio Authorisation"
-description: "Manage the authorisation for access to flows in {{% ctx %}} Gateway."
+description: "Configure access to flows in {{% ctx %}} Gateway."
 weight: 50
 ---
 
 # {{% param title %}}
 
 ## Summary
 
-The Studio Authorisation page is used to manage the authorisation for access to flows within {{% ctx %}} Gateway. Each flow can be set to have [View][] or [Edit][] permissions assigned to LDAP Groups, or no access permissions at all.
+The Studio Authorisation page is used to configure access to flows within {{% ctx %}} Gateway. Each flow can be set to have [View][] or [Edit][] permissions assigned to LDAP Groups that exist in the Active Directory server configured in LDAP Connection for CORTEX Gateway, or no access permissions at all.
 
 |                              |                                                                 |
 |------------------------------|-----------------------------------------------------------------|
@@ -19,11 +19,11 @@ The Studio Authorisation page is used to manage the authorisation for access to
 
 {{< figure src="/images/Studio Authorisation.png" title="Studio Authorisation" >}}
 
-The LDAP Groups that may be granted access are limited to those assigned the Studio role in LDAP Authorisation.
+The LDAP Groups that may be granted access are limited to those assigned the `Studio` role in LDAP Authorisation.
 
 Permissions are set either explicitly or implicitly. Explicitly set permissions are assigned by the user performing an explicit action to set that item’s permissions, whereas implicitly set permissions are assigned automatically by the user explicitly setting the permissions on a parent group.
 
-Permissions are explicitly set by setting the checkbox in either the [View][] or [Edit][] columns of the appropriate LDAP Group where it intersects with the flow or flow Group to which the permissions are to be assigned.  Permissions are explicitly removed by clearing the checkbox.
+Permissions are explicitly set by setting the checkbox in either the [View][] or [Edit][] columns of the appropriate LDAP Group for the flow or group to which the permissions are to be assigned.  Permissions are explicitly removed by clearing the checkbox.
 
 If an item is explicitly set with [Edit][] permissions, then that item will also be implicitly set with [View][] permissions. Explicitly setting an item with [View][] permissions does not implicitly set it with Edit permissions.
 
@@ -34,13 +34,16 @@ If an item is explicitly set with [Edit][] permissions, then that item will also
 If an LDAP group is given `View` permissions on a flow, the members of the LDAP group can:
 
 * View the flow
-* Execute the flow
+* Debug the flow
 
-If an LDAP Group is given `View` only permissions on a flow group, the members of that LDAP group can only access existing flows and flow groups within that flow group.
+If an LDAP Group is given `View` permissions on a group, the members of that LDAP group can:
 
-If a flow group has `View` permissions either explicitly set or implicitly set, then its child flow groups or flows will have their `View` permissions be implicitly set.
+* View all descendent groups and flows
+* Debug all descendent flows
 
-If a flow group has its `View` permissions removed, then all its child flow groups or flows will have their `View` permissions removed, regardless of whether they were set explicitly or implicitly.
+If a group has `View` permissions either explicitly set or implicitly set, then its child groups and flows will have their `View` permissions implicitly set.
+
+If a group has its `View` permissions removed, then all its child groups and flows will have their `View` permissions removed, regardless of whether they were set explicitly or implicitly.
 
 See the [Manage Flow Access][Manage Flow Access tutorial] tutorial for a step-by-step guide.
 
@@ -49,27 +52,39 @@ See the [Manage Flow Access][Manage Flow Access tutorial] tutorial for a step-by
 If an LDAP group is given `Edit` permissions on a flow, the members of the LDAP group can:
 
 * View the flow
-* Execute the flow
+* Debug the flow
 * Edit the flow
+* Move the flow
+* Rename the flow
 * Delete the flow
 * Commit changes to the flow
 * Get the master version of the flow
 
-If an LDAP Group is given `Edit` permissions on a flow group, the members of that LDAP group can create new flows and groups within that flow group.
+If an LDAP Group is given `Edit` permissions on a group, the members of that LDAP group can:
+
+* Create new flows and groups within the group
+* View all descendent flows and groups
+* Debug all descendent flows
+* Edit all descendent flows
+* Move all descendent flows
+* Rename all descendent flows
+* Delete all descendent flows
+* Commit changes to all descendent flows
+* Get the master version of all descendent flows
 
-If a flow group has `Edit` permissions explicitly set, then its child flow groups or flows will be implicitly set with both `Edit` and [`View`][View] permissions.
+If a group has `Edit` permissions explicitly set, then its child groups and flows will be implicitly set with both `Edit` and [`View`][View] permissions.
 
-If a flow group has its `Edit` permissions removed, then all its child flow groups or flows will have their `Edit` permissions removed, regardless of whether they were set explicitly or implicitly.
+If a group has its `Edit` permissions removed, then all its child groups and flows will have their `Edit` permissions removed, regardless of whether they were set explicitly or implicitly.
 
-If a flow is explicitly set with `Edit` permissions, then any parent Groups, which have not been explicitly set with [`View`][View] permissions, will be also implicitly set with [`View`][View] permissions.
+If a flow is explicitly set with `Edit` permissions, then any parent groups, which have not been explicitly set with [`View`][View] permissions, will be implicitly set with [`View`][View] permissions.
 
 See the [Manage Flow Access][Manage Flow Access tutorial] tutorial for a step-by-step guide.
 
 ## Remarks
 
 ### Known Limitations
 
-* If a flow group is explicitly set Edit permissions, then the Groups View permissions will be implicitly set. However, if the explicitly set Edit permissions are removed from the Group, the implicitly set View permissions are not removed.
+* The state of whether a permission is granted explicitly or implicitly is not persisted between the page being closed and reopened.
 
 ## See Also
 

content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/Admin/studio-hierarchy.md

@@ -1,7 +1,7 @@
 ---
 title: "Studio Hierarchy"
 linkTitle: "Studio Hierarchy"
-description: "Manage the flow hierarchy in {{% ctx %}} Gateway."
+description: "Move flows in {{% ctx %}} Gateway."
 weight: 70
 ---
 
@@ -15,29 +15,25 @@ The Studio Hierarchy page is used to move one or more flows from one group to an
 
 {{< figure src="/images/Studio Hierarchy.png" title="Studio Hierarchy" >}}
 
-Only flows that the user has Edit permissions for are displayed.
+Only flows with `Edit` permissions for the current user are displayed in the Studio Hierarchy grid.
 
 ## Actions
 
 ### Move Flows
 
-After selecting the flows that are to be moved to a unique location in Group hierarchy, Right-Click on the target Group to where the selected flows will be moved to, and select the `Move selected items to this Group` from the context menu. The display will be updated to show the resultant hierarchy, with the flows to be moved but not yet committed identified with an asterisk (*) in the Results column of the display.
+After selecting the flows that are to be moved, right-click on the group where the selected flows will be moved to, and select the `Move selected items to this Group` from the context menu. The display will be updated to show the resultant hierarchy, with the flows to be moved but not yet committed identified with an asterisk (*) in the `Results` column of the grid.
 
-If a Group is selected, then only the flows contained in that selected group are moved to another group; not the group itself.
+If a group is selected, then only the flows contained in that group are moved to another group; not the group itself.
 
-See the [Manage Flow Hierarchy][Manage Flow Hierarchy tutorial] tutorial for a step-by-step guide.
-
-### Commit Changes
-
-Once all the necessary flows have been moved in the hierarchy, all the changes can be committed using the Commit button.
+Once all the necessary flows have been moved, the changes can be committed using the `Commit` button.
 
 See the [Manage Flow Hierarchy][Manage Flow Hierarchy tutorial] tutorial for a step-by-step guide.
 
 ## Remarks
 
 ### Known Limitations
 
-* It is necessary for the parent Groups to have Edit permissions in addition to the flows to be moved, to enable the display of the flows in Studio Hierarchy.
+* Parent groups must also have edit permissions, in addition to the flows, otherwise the group and flows contained within it will not be displayed.
 
 ## See Also