docs: fix high and medium inaccuracies in collaboration and access pages#2728
Open
mtrunkat wants to merge 2 commits into
Open
docs: fix high and medium inaccuracies in collaboration and access pages#2728mtrunkat wants to merge 2 commits into
mtrunkat wants to merge 2 commits into
Conversation
general-resource-access.md: - Correct storage-only access level label to "Anyone with ID or name can read" list_of_permissions.md: - Add missing "Build" permission to the Actor table - Rename "Manage access keys" to "Manage access tokens" - Rename "Update subscription" to "Manage billing" - Remove non-grantable "Reset password" user permission - Add "View payouts" and "View monetization" user permissions organization_account/index.md: - Fix organization creation limit from 5 to 10 - Document that Creator-plan accounts can't be converted to organizations organization_account/setup.md: - Move security settings from the Account tab to the "Security & Privacy" tab
Contributor
|
✅ Preview for this PR (commit |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates Apify collaboration/access documentation to correct several high- and medium-severity factual inaccuracies (limits, UI locations, permission names/coverage, and storage access-level wording) to better match the current platform behavior.
Changes:
- Corrected organization-account guidance (organization creation limit, conversion constraints, and where security settings live in Console).
- Updated the permissions reference to include the missing Actor Build permission and align naming with the product (“access tokens”, “billing”, etc.).
- Fixed the storage sharing access-level label for named storages.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| sources/platform/collaboration/organization_account/setup.md | Updates where organization security settings are configured; minor wording cleanup needed. |
| sources/platform/collaboration/organization_account/index.md | Updates org creation limit and adds Creator-plan conversion restriction; minor wording precision needed. |
| sources/platform/collaboration/list_of_permissions.md | Adds Actor Build permission and updates organization/user permission labels to match product naming. |
| sources/platform/collaboration/general-resource-access.md | Corrects the label for the named-storage extra access level; minor grammar cleanup needed. |
mtrunkat
commented
Jul 3, 2026
|
|
||
| Before converting your personal account into an organization, make sure it has a username. | ||
|
|
||
| You can't convert your account to an organization while you're on the Creator plan. Upgrade to a different plan to continue. |
Member
Author
There was a problem hiding this comment.
This one is taken almost verbatim from the Console string account.organization.convertToOrganization.cannotConvertCreatorPlan.label in en.organization.ts: "You can't convert your account to an organization while you're on the Creator plan. Upgrade to a different plan to continue." So the doc reflects the current Console behavior. Happy to revert or reword if that guard is changing.
Generated by Claude Code
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrects high- and medium-severity discrepancies in the collaboration and access docs, verified against
apify-core.organization_account/index.md- organization limit is 10 per owner (not 5); added that Creator-plan accounts can't be converted to organizations.list_of_permissions.md- added the missing Actor Build permission; renamed "Manage access keys" -> "Manage access tokens" and "Update subscription" -> "Manage billing" to match the code; removed the non-grantable "Reset password" row; added "View payouts" and "View monetization".organization_account/setup.md- organization security settings live under the separate Security & Privacy tab, not the Account tab.general-resource-access.md- storage access-level label is "Anyone with ID or name can read".Generated by Claude Code