-
Notifications
You must be signed in to change notification settings - Fork 232
Document how to run Actors with restricted access (whitelabel access) #2948
Copy link
Copy link
Open
Labels
debtCode quality improvement or decrease of technical debt.Code quality improvement or decrease of technical debt.documentationImprovements or additions to documentation.Improvements or additions to documentation.medium priorityMedium priority issues to be done in a couple of sprints.Medium priority issues to be done in a couple of sprints.t-docsIssues owned by technical writing team.Issues owned by technical writing team.t-integrationsIssues with this label are in the ownership of the integrations team.Issues with this label are in the ownership of the integrations team.
Description
Activity
Metadata
Metadata
Assignees
Labels
debtCode quality improvement or decrease of technical debt.Code quality improvement or decrease of technical debt.documentationImprovements or additions to documentation.Improvements or additions to documentation.medium priorityMedium priority issues to be done in a couple of sprints.Medium priority issues to be done in a couple of sprints.t-docsIssues owned by technical writing team.Issues owned by technical writing team.t-integrationsIssues with this label are in the ownership of the integrations team.Issues with this label are in the ownership of the integrations team.
Why?
The Whitelabel access section
doesn't mention that an Actor run with a partner's API token gets full access to that partner's
Apify account by default. Partners running arbitrary Store Actors need to sandbox those runs with
a scoped token. We have a guide for it, but it's internal-only.
What?
Publish the internal guide in the public docs and link it from
#### Whitelabel access:Guide: How to execute Apify Actors with restricted access
Target section:
sources/platform/integrations/integrate-with-apify.md,#### Whitelabel access(under
### Pricing options).How?
Up to the implementer — the guide is the source of truth for the content. Two notes:
#### Whitelabel accessis probably better than expanding thesection in place; the guide is long and also relevant outside the whitelabel context.
current UI before publishing.