-
Notifications
You must be signed in to change notification settings - Fork 143
feat: Update organization docs with more answers #2134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
feat: Update organization docs with more answers #2134
Conversation
Co-authored-by: marek <marek@apify.com>
|
Cursor Agent can help with this pull request. Just |
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
|  | ||
|
|
||
| Next, set the organization's name and click **Convert**. | ||
| Next, enter an organization name and click **Convert**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use this opportunity to change click to select
| Next, enter an organization name and click **Convert**. | |
| Next, enter an organization name and select **Convert**. |
| Next, set the organization's name and click **Convert**. | ||
| Next, enter an organization name and click **Convert**. | ||
|
|
||
| The name you enter here becomes the organization's display name only. The original account **username** stays the same, so any public Actors or API references (for example `my_profile/my_actor`) keep their existing URLs. A new personal account is created for you with the same login credentials and a username derived from the original one (for example `my_profile-owner`). Use that new personal account to manage and own the organization. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The name you enter here becomes the organization's display name only. The original account **username** stays the same, so any public Actors or API references (for example `my_profile/my_actor`) keep their existing URLs. A new personal account is created for you with the same login credentials and a username derived from the original one (for example `my_profile-owner`). Use that new personal account to manage and own the organization. | |
| The name you enter becomes the organization's display name. The original account **username** stays the same, so any public Actors or API references (for example, `my_profile/my_actor`) keep their existing URLs. A new personal account is created for you with the same login credentials and a username based on your original username with `-owner` added (for example, `my_profile-owner`). You'll use this new personal account to manage and own the organization. |
Clarify the organization account conversion flow by explaining the impact of naming on display name vs. username, and details about the auto-created personal owner account.
Slack Thread
Note
Clarifies org conversion naming behavior, preserves URLs/usernames, and documents the auto-created personal owner account.
sources/platform/collaboration/organization_account/index.md:usernameand public URLs remain unchanged, and a new personal owner account is auto-created with a derived username to manage the organization.Written by Cursor Bugbot for commit 5c71ef7. Configure here.