Skip to content

Commit d87cd70

Browse files
authored
Merge branch 'main' into update_doc_for_ingesting_all_repos
2 parents 6df2731 + d6710a9 commit d87cd70

File tree

5 files changed

+56
-1
lines changed

5 files changed

+56
-1
lines changed

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

Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,57 @@ 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/allowAnyoneToViewRuns.png' width='70%' border='1px' />
139+
140+
</TabItem>
141+
142+
<TabItem value="api">
143+
144+
Add the `allowAnyoneToViewRuns` 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+
"allowAnyoneToViewRuns": true,
160+
...
161+
}
162+
]
163+
```
164+
165+
</TabItem>
166+
</Tabs>
167+
117168
### Define approval notifications
118169

119170
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: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,10 @@ 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+
4044
## Fetch an action run
4145

4246
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.

docs/customize-pages-dashboards-and-plugins/page/catalog-page.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -195,7 +195,7 @@ Initial filters are the most effective way to reduce loading times. You can defi
195195

196196
To define such a filter, use the `Initial filters` field when creating a page:
197197

198-
<img src='/img/software-catalog/pages/initialFiltersForm.png' width='50%' border='1px' />
198+
<img src='/img/software-catalog/pages/initialFiltersForm.png' width='50%' border='1px' style={{borderRadius:'8px'}} />
199199

200200
<br/><br/>
201201

78.1 KB
Loading
18.4 KB
Loading

0 commit comments

Comments
 (0)