Add studio import/export documentation (#204)

Author: Cortex-DMS

content/en/docs/2025.3/Guides/cortex-gateway/settings/studio-export.md

@@ -2,5 +2,5 @@
 title: "Packages"
 linkTitle: "Packages"
 description: "Create and manage packages in {{% ctx %}} Gateway."
-weight: 10
+weight: 100
 ---

content/en/docs/2025.3/Guides/cortex-gateway/settings/studio-import.md

@@ -0,0 +1,51 @@
+---
+title: "Studio Export"
+linkTitle: "Studio Export"
+description: "Export flows from {{% ctx %}} Gateway."
+weight: 50
+---
+
+# {{% param title %}}
+
+## Summary
+
+The Studio Export page allows exporting one or more flows into a Studio Package file, which may be used for archiving purposes, or [importing][Studio Import] flows into another {{% ctx %}}.
+
+|                              |                                                                 |
+|------------------------------|-----------------------------------------------------------------|
+| **Roles Required:**          | Admin                                                           |
+
+## Anatomy
+
+{{< figure src="/images/Studio Export.png" title="Studio Export" >}}
+
+## Actions
+
+### Export Flows
+
+Individual flows are selected by clicking the checkbox in the `Export?` column adjacent to the flow to be exported. If a group is selected, then all the flows contained in that group, and any sub-groups, will be implicitly set; any implicitly set may be individually deselected by clicking the checkbox adjacent to the flow.
+
+Clicking `Export` checks if selected flows have dependencies. If there are dependencies, an additional page will be shown to allow confirmation that these should be included in the export. By default these are selected but can be deselected. A Studio Package will then be created from the Master Versions in the Master Repository of the selected flows, including their group hierarchy. The package will then be downloaded to the host’s browser as a file named `export.studiopkg` or `export <n>.studiopkg`, where `<n>` represents an integer to avoid naming conflict with other Studio Package files contained in the same folder.
+
+It is not necessary to have View or Edit authorisation for the flows to be exported.
+
+See the [Export Individual Flows][Export Individual Flows tutorial] tutorial for a step-by-step guide.
+
+## Remarks
+
+### Known Limitations
+
+* The name of the Studio Package file cannot currently be customised.
+
+## See Also
+
+### Related Concepts
+
+None
+
+### Related Tutorials
+
+* [Export Individual Flows][Export Individual Flows tutorial]
+
+[Export Individual Flows tutorial]: {{< url path="Cortex.Tutorials.Administration.StudioExport.ExportIndividualFlows" >}}
+[Studio Import]: {{< url path="Cortex.Guides.UserGuides.UserInterfaces.Gateway.Admin.StudioImport.MainDoc" >}}

content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/Admin/packages/_index.md

@@ -0,0 +1,63 @@
+---
+title: "Studio Import"
+linkTitle: "Studio Import"
+description: "Import flows into {{% ctx %}} Gateway."
+weight: 25
+---
+
+# {{% param title %}}
+
+## Summary
+
+The Studio Import page allows importing one or more flows, contained in a Studio Package.
+
+|                              |                                                                 |
+|------------------------------|-----------------------------------------------------------------|
+| **Roles Required:**          | Admin                                                           |
+
+## Anatomy
+
+{{< figure src="/images/Studio Import.png" title="Studio Import" >}}
+
+## Actions
+
+### Favoured Hierarchy
+
+By default, the import favours the `system hierarchy`, and shows how the imported flows will map into the existing hierarchy. If flows to be imported already exist, they will be imported to the same location in the hierarchy; otherwise, any missing groups in the flow hierarchy will be added.
+
+It is possible to favour the `package hierarchy`, and this shows the hierarchy contained in the Studio Package. If flows to be imported already exist, they will be moved to the location specified in the Studio Package, adding any missing groups as necessary; otherwise, the hierarchy specified in the Studio Package will be created when the flows are imported.
+
+### Edit Import Locations
+
+The `Edit import hierarchy` switch enables editing the locations where flows should be imported to. This is useful if the default import location in the [favoured hierarchy][] for one or more flows needs changing.
+
+It is not necessary to have View or Edit authorisation for any flows or groups to view the entire hierarchy.
+
+### Import
+
+Individual flows contained in the Studio Package may be individually selected to be imported; it is not necessary that all the flows contained in the Studio Package are imported.
+
+When the selected flows are imported, they become the Master Version of the flows in the Master Repository, replacing any existing Master Versions.
+
+After importing the flows, it is necessary to check they are correctly configured in Studio Authorisation.
+
+See the [Import Individual Flows][Import Individual Flows tutorial] tutorial for a step-by-step guide.
+
+## Remarks
+
+### Known Limitations
+
+None
+
+## See Also
+
+### Related Concepts
+
+None
+
+### Related Tutorials
+
+* [Import Individual Flows][Import Individual Flows tutorial]
+
+[favoured hierarchy]: {{< ref "#favoured-hierarchy">}}
+[Import Individual Flows tutorial]: {{< url path="Cortex.Tutorials.Administration.StudioImport.ImportIndividualFlows" >}}

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

@@ -2,7 +2,7 @@
 title: "Package Management"
 linkTitle: "Package Management"
 description: "This section includes tutorials about managing packages on the {{% ctx %}} platform."
-weight: 1
+weight: 200
 ---
 
 # {{% param title %}}

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

@@ -0,0 +1,12 @@
+---
+title: "Studio Export"
+linkTitle: "Studio Export"
+description: "This section includes tutorials about exporting individual flows."
+weight: 100
+---
+
+# {{% param title %}}
+
+## Export Individual Flows
+
+{{< scribe title="How_to_use_Studio_Export_to_Export_Individual_Flows" id="eHoR7gKNR_qsvU8Qoa73KA" >}}

content/en/docs/2025.3/Tutorials/Administration/package-management.md

@@ -0,0 +1,12 @@
+---
+title: "Studio Import"
+linkTitle: "Studio Import"
+description: "This section includes tutorials about importing individual flows."
+weight: 50
+---
+
+# {{% param title %}}
+
+## Import Individual Flows
+
+{{< scribe title="How_to_use_Studio_Import_to_Import_Individual_Flows" id="kNzevcaURRexdsZKtpg_Ew" >}}

content/en/docs/2025.3/Tutorials/Administration/studio-export.md

@@ -28,4 +28,4 @@ If no useful message can be seen here, the service log files may contain more in
 
 If no solution can be found, please contact [{{% ctx %}} Service Portal][CORTEX Service Portal] for further assistance.
 
-[CORTEX Service Portal]: {{< url path="Cortex.ServicePortal.MainDoc" >}}
+[CORTEX Service Portal]: {{< url path="Cortex.ServicePortal.MainDoc" >}}

content/en/docs/2025.3/Tutorials/Administration/studio-import.md

@@ -50,7 +50,7 @@ If Windows Defender is not running on the server, ensure that the [Antivirus Exc
 1. Open a web browser.
 1. {{< section "/install-application-server/single-server/check-application-services.md">}}
 
-# Preserve installation files
+## Preserve installation files
 
 {{< section "/preserve-installation-files.md">}}