Skip to content

Commit 6af1ff3

Browse files
author
Donna-Marie Smith
committed
added Studio Hierarchy content
1 parent 09a4bf0 commit 6af1ff3

File tree

3 files changed

+10
-15
lines changed

3 files changed

+10
-15
lines changed

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

Lines changed: 0 additions & 7 deletions
This file was deleted.

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

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,25 +9,27 @@ weight: 70
99

1010
## Summary
1111

12-
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.
13-
14-
| | |
15-
|------------------------------|-----------------------------------------------------------------|
16-
| **Roles Required:** | Admin |
12+
The Studio Hierarchy page is used to move one or more flows from one group to another.
1713

1814
## Anatomy
1915

20-
{{< figure src="/images/Studio Authorisation.png" title="Studio Authorisation" >}}
16+
{{< figure src="/images/Studio Hierarchy.png" title="Studio Hierarchy" >}}
17+
18+
Only flows that the user has Edit permissions for are displayed.
2119

2220
## Actions
2321

24-
### View
22+
### Move Flows
23+
24+
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.
2525

26+
If a Group is selected, then only the flows contained in that selected group are moved to another group; not the group itself.
2627

2728
See the [Manage Flow Hierarchy][Manage Flow Hierarchy tutorial] tutorial for a step-by-step guide.
2829

29-
### Edit
30+
### Commit Changes
3031

32+
Once all the necessary flows have been moved in the hierarchy, all the changes can be committed using the Commit button.
3133

3234
See the [Manage Flow Hierarchy][Manage Flow Hierarchy tutorial] tutorial for a step-by-step guide.
3335

177 KB
Loading

0 commit comments

Comments
 (0)