Skip to content

Commit 7f5f9c9

Browse files
committed
Update wording
1 parent 993ae5d commit 7f5f9c9

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

sources/platform/actors/running/permissions.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,10 +49,12 @@ This approach ensures the Actor has everything it needs to function while protec
4949

5050
When you browse Actors in Apify Console or Store, you’ll notice a small badge next to each Actor showing its permission level. Hover over the badge to see a short explanation of what access that Actor will have when it runs under your account.
5151

52-
** Limited permissions Actor **
52+
**Limited permissions Actors**
53+
5354
![Limited-permissions badge shown on Actor detail page](../development/permissions/images/end_user_ux_limited_permissions.png)
5455

55-
** Full permissions Actor **
56+
**Full permissions Actors**
57+
5658
![Full-permissions badge shown on Actor detail page](../development/permissions/images/end_user_ux_full_permissions.png)
5759

58-
Over time, the distinction between these permission levels will be more visible — for example, Actors requiring full permissions will have an orange badge, might rank lower in the Store or show additional confirmation dialogs. Whenever possible, prefer Actors that use **limited permissions**: they’re safer, easier to trust, and still powerful enough for most workflows.
60+
Over time, the distinction between these permission levels will become more prominent. For example, Actors requiring full permissions may display an orange badge, appear lower in Store rankings, or show extra confirmation dialogs when you run them. Whenever possible, choose Actors that use **limited permissions**. They are safer, easier to trust, and sufficient for most workflows.

0 commit comments

Comments
 (0)