Skip to content

Commit ca7bc6f

Browse files
committed
Fix forgotten half sentence in "how restricted access works"
1 parent 3cac3b2 commit ca7bc6f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

sources/platform/collaboration/general-resource-access.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,9 @@ Access to resources that require explicit access — such as Actors, tasks or sc
2626

2727
If your **general resource access** is set to **anyone with ID can read**, you can just send this link to anybody, and they will be able to download the data even if they don’t have an Apify account. However, once you change the setting to **restricted**, this API call will require a valid token with access in order to work. In other words, you’ll have to explicitly share the dataset and you can only do that with people who have an Apify account.
2828

29-
When using the API, resources that are set to `Restricted` can be viewed only with a valid token with correct permissions is sent in the request. Alternatively, when a resource is set to **anyone with ID can read**, the resource could be viewed.
29+
When using the API, resources that are set to `Restricted` can be viewed only with a valid token with correct permissions is sent in the request. Alternatively, when a resource is set to **anyone with ID can read**, the resource could be viewed without authentication.
30+
31+
Even if your access is set to `Restricted` there are a few built-in exceptions that make collaboration and platform features work seamlessly. These are explained in the sections below.
3032

3133
### Named storages
3234

0 commit comments

Comments
 (0)