Skip to content

Commit 092fb96

Browse files
authored
Merge pull request #2969 from port-labs/revert-2961-task_t4iypz/view-action-runs-permission-fixed
Revert "add permission to view action runs"
2 parents be37dda + 07a4ddc commit 092fb96

File tree

3 files changed

+0
-57
lines changed

3 files changed

+0
-57
lines changed

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

Lines changed: 0 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -114,58 +114,6 @@ Add the `requiredApproval` field to your action:
114114
</TabItem>
115115
</Tabs>
116116

117-
## Configure visibility for action runs
118-
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.
120-
121-
122-
- **When enabled (default):** All organization members can view the action’s runs.
123-
- **When disabled:**
124-
- **Admins** can view all runs.
125-
- **Approvers** can view runs they are assigned to approve.
126-
- **Members** can only view their own runs.
127-
128-
This ensures that sensitive operational data remains accessible only to authorized users, while maintaining flexibility and transparency where needed.
129-
130-
131-
<Tabs groupId="config-method" queryString values={[
132-
{label: "UI", value: "ui"},
133-
{label: "API", value: "api"},
134-
]}>
135-
136-
<TabItem value="ui">
137-
138-
<img src='/img/self-service-actions/rbac/viewRunAccess.png' width='70%' border='1px' />
139-
140-
</TabItem>
141-
142-
<TabItem value="api">
143-
144-
Add the `isViewRunAccess` field to your action:
145-
146-
```json showLineNumbers
147-
[
148-
{
149-
...
150-
"invocationMethod": {
151-
"type": "WEBHOOK",
152-
"url": "https://example.com"
153-
},
154-
"trigger": {
155-
...
156-
"operation": "CREATE",
157-
}
158-
// highlight-next-line
159-
"isViewRunAccess": true,
160-
...
161-
}
162-
]
163-
```
164-
165-
</TabItem>
166-
167-
</Tabs>
168-
169117
### Define approval notifications
170118

171119
By default manual approval notifications are sent via **Email** to users who have [approval permissions](#define-approvers).

docs/actions-and-automations/reflect-action-progress/reflect-action-progress.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -37,11 +37,6 @@ In addition to the methods mentioned above, `admins` can find action runs using
3737
- Go the [entity page](/customize-pages-dashboards-and-plugins/page/entity-page.md) of your desired entity, then select the `Runs` tab.
3838
This page will display all action runs that have been executed for the selected Entity.
3939

40-
## Who can view action runs
41-
42-
Run visibility is controlled by the action’s permissions. See [Configure visibility for action runs](/actions-and-automations/create-self-service-experiences/set-self-service-actions-rbac/#configure-visibility-for-action-runs) for details.
43-
44-
4540
## Fetch an action run
4641

4742
Once an `actionRun` is created, it will have a unique `runId`. Using this id, you can interact with the action run using Port's API.
-73.8 KB
Binary file not shown.

0 commit comments

Comments
 (0)