Modified following initial PO review

Author: Donna-Marie Smith

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

@@ -9,7 +9,7 @@ weight: 50
 
 ## Summary
 
-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.
+The Studio Authorisation page is used to configure access to flows within {{% ctx %}} Gateway. Each flow can be set to have [`View`][View] or [`Edit`][Edit] permissions assigned to LDAP Groups that exist in the Active Directory server configured in LDAP Connection for {{% ctx %}} Gateway, or no access permissions at all.
 
 |                              |                                                                 |
 |------------------------------|-----------------------------------------------------------------|
@@ -25,7 +25,7 @@ Permissions are set either explicitly or implicitly. Explicitly set permissions
 
 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.
+If an item is explicitly set with [`Edit`][Edit] permissions, then that item will also be implicitly set with [`View`][View] permissions. Explicitly setting an item with [`View`][View] permissions does not implicitly set it with Edit permissions.
 
 ## Actions
 

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

@@ -15,7 +15,7 @@ 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 with `Edit` permissions for the current user are displayed in the Studio Hierarchy grid.
+Only flows with [`Edit`][Edit] permissions for the current user are displayed in the Studio Hierarchy grid.
 
 ## Actions
 
@@ -33,7 +33,7 @@ See the [Manage Flow Hierarchy][Manage Flow Hierarchy tutorial] tutorial for a s
 
 ### Known Limitations
 
-* Parent groups must also have edit permissions, in addition to the flows, otherwise the group and flows contained within it will not be displayed.
+* Parent groups must also have [`Edit`][Edit] permissions, in addition to the flows, otherwise the group and flows contained within it will not be displayed.
 
 ## See Also
 
@@ -45,4 +45,5 @@ None
 
 * [Manage Flow Hierarchy][Manage Flow Hierarchy tutorial]
 
+[Edit]: {{< url path="Cortex.Guides.UserGuides.UserInterfaces.Gateway.Admin.StudioAuthorisation.Edit" >}}
 [Manage Flow Hierarchy tutorial]: {{< url path="Cortex.Tutorials.Administration.StudioHierarchy.ManageFlowHierarchy" >}}

content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/Admin/version-control.md

@@ -15,7 +15,7 @@ The Version Control page displays the flow hierarchy for the current user, indic
 
 {{< figure src="/images/Version Control.png" title="Version Control" >}}
 
-Only flows with Edit permissions for the current user are displayed in the Version Control grid.
+Only flows with [`Edit`][Edit] permissions for the current user are displayed in the Version Control grid.
 
 ## Actions
 
@@ -35,7 +35,7 @@ See the [Use Version Control][Use Version Control tutorial] tutorial for a step-
 
 ### Known Limitations
 
-* Parent groups must also have edit permissions, in addition to the flows, otherwise the group and flows contained within it will not be displayed.
+* Parent groups must also have [`Edit`][Edit] permissions, in addition to the flows, otherwise the group and flows contained within it will not be displayed.
 
 ## See Also
 
@@ -47,4 +47,5 @@ None
 
 * [Use Version Control][Use Version Control tutorial]
 
+[Edit]: {{< url path="Cortex.Guides.UserGuides.UserInterfaces.Gateway.Admin.StudioAuthorisation.Edit" >}}
 [Use Version Control tutorial]: {{< url path="Cortex.Tutorials.Administration.VersionControl.UseVersionControl" >}}

content/en/docs/2025.3/Tutorials/Administration/license-consumption.md

@@ -2,7 +2,7 @@
 title: "License Consumption"
 linkTitle: "License Consumption"
 description: "This section includes tutorials about checking the license consumption for {{% ctx %}}."
-weight: 70
+weight: 80
 ---
 
 # {{% param title %}}

data/urls.toml

@@ -924,6 +924,9 @@
                                 SetDefaultVersion = "/docs/guides/user-guides/user-interfaces/gateway/admin/packages/package-version-editor/#set-as-default-version"
                                 Triggers = "/docs/guides/user-guides/user-interfaces/gateway/admin/packages/package-version-editor/#triggers"
                                 Unpublish = "/docs/guides/user-guides/user-interfaces/gateway/admin/packages/package-version-editor/#unpublish-a-package-version"
+                        [Cortex.Guides.UserGuides.UserInterfaces.Gateway.Admin.StudioAuthorisation]
+                            MainDoc = "/docs/guides/user-guides/user-interfaces/gateway/admin/studio-authorisation/"
+                            Edit = "/docs/guides/user-guides/user-interfaces/gateway/admin/studio-authorisation/#edit"
                         [Cortex.Guides.UserGuides.UserInterfaces.Gateway.Admin.StudioImport]
                             MainDoc = "/docs/guides/user-guides/user-interfaces/gateway/admin/studio-import/"
     [Cortex.Reference]