Skip to content

Commit 1f0d6f9

Browse files
committed
fix PR
1 parent 41179f5 commit 1f0d6f9

File tree

2 files changed

+2
-5
lines changed

2 files changed

+2
-5
lines changed

docs/actions-and-automations/create-self-service-experiences/set-self-service-actions-rbac/set-self-service-actions-rbac.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -116,15 +116,14 @@ Add the `requiredApproval` field to your action:
116116

117117
## Configure visibility for action runs
118118

119-
When creating or editing a self-service action, you can also control who can **view its runs**.
119+
When creating or editing a self-service action, you can also control who can **view its runs**, using the relevant toggle in the `Permissions` tab.
120120

121-
A new toggle — **“Let anyone in this organization view this action’s runs”** — defines visibility for runs associated with the action.
122121

123122
- **When enabled (default):** All organization members can view the action’s runs.
124123
- **When disabled:**
125124
- **Admins** can view all runs.
126125
- **Approvers** can view runs they are assigned to approve.
127-
- **Regular members** can only view their own runs.
126+
- **Members** can only view their own runs.
128127

129128
This ensures that sensitive operational data remains accessible only to authorized users, while maintaining flexibility and transparency where needed.
130129

@@ -136,8 +135,6 @@ This ensures that sensitive operational data remains accessible only to authoriz
136135

137136
<TabItem value="ui">
138137

139-
Scroll down the `Permissions` tab and set `Enforce manual approval` to `Yes`. This will introduce some new options:
140-
141138
<img src='/img/self-service-actions/rbac/viewRunAccess.png' width='70%' border='1px' />
142139

143140
</TabItem>
-114 KB
Loading

0 commit comments

Comments
 (0)