[EDI] Managing access to your personal repositories (#57121)

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: jc-clark

content/account-and-profile/concepts/index.md

@@ -17,4 +17,5 @@ children:
   - /changing-your-github-username
   - /email-addresses
   - /scheduled-reminders
+  - /personal-repository-access-and-collaboration
 ---

content/account-and-profile/concepts/personal-repository-access-and-collaboration.md

@@ -0,0 +1,48 @@
+---
+title: Personal repository access and collaboration
+intro: 'Learn how to manage access and collaboration for repositories you own with your personal account on {% data variables.product.github %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Repositories
+  - Privacy
+  - Open Source
+shortTitle: Access to repositories
+---
+
+## About collaboration in a personal repository
+
+You can collaborate with others on repositories you own by inviting them as collaborators. Collaborators have access to contribute to your code and manage issues and pull requests.
+
+{% ifversion ghec %}
+
+If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% endif %}
+
+To add a collaborator, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository).
+
+{% ifversion fpt or ghec %}
+
+{% data reusables.repositories.private_forks_inherit_permissions %}
+
+## About successors
+
+We recommend inviting another {% data variables.product.company_short %} user to be your successor, to manage your user owned repositories if you cannot. As a successor, they will have permission to:
+
+* Archive your public repositories.
+* Transfer your public repositories to their own user owned account.
+* Transfer your public repositories to an organization where they can create repositories.
+
+Successors cannot log into your account.
+
+An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see [AUTOTITLE](/free-pro-team@latest/site-policy/other-site-policies/github-deceased-user-policy).
+
+To request access to manage repositories as a successor, please contact us through the {% data variables.contact.contact_support_portal %}.
+
+For more information, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories).
+
+{% endif %}

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md

@@ -21,6 +21,6 @@ children:
   - /removing-a-collaborator-from-a-personal-repository
   - /removing-yourself-from-a-collaborators-repository
   - /maintaining-ownership-continuity-of-your-personal-accounts-repositories
-shortTitle: Access to your repositories
+shortTitle: Manage repository access
 ---
 

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md

@@ -19,30 +19,11 @@ topics:
   - Repositories
 shortTitle: Invite collaborators
 ---
-## About collaboration in a personal repository
-
-To collaborate with users in a repository that belongs to your personal account on {% data variables.product.prodname_dotcom %}, you can invite the users as collaborators.
-
-If you want to grant more granular access to the repository, you can create a repository within an organization. For more information, see [AUTOTITLE](/get-started/learning-about-github/access-permissions-on-github).
-
-{% ifversion ghec %}
-
-If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
-
-{% endif %}
-
-{% data reusables.repositories.private_forks_inherit_permissions %}
 
 ## Inviting a collaborator to a personal repository
 
 You can send an invitation to collaborate in your repository directly to someone on {% data variables.product.prodname_dotcom %}{% ifversion fpt or ghec %}, or to the person's email address{% elsif ghes %}.{% endif %}.
 
-{% ifversion fpt or ghec %}
-
-{% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people. For more information, see [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch).
-
-{% endif %}
-
 1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %}. For more information, see [AUTOTITLE](/get-started/start-your-journey/creating-an-account-on-github).{% endif %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
@@ -54,9 +35,6 @@ You can send an invitation to collaborate in your repository directly to someone
 1. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
 {% endif %}
 
-## Further reading
+## Next steps
 
-* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account)
-* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository)
-* [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository)
-* [AUTOTITLE](/organizations/organizing-members-into-teams)
+* For reference information, see [AUTOTITLE](/account-and-profile/reference/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account)

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md

@@ -14,19 +14,6 @@ redirect_from:
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories
 shortTitle: Ownership continuity
 ---
-## About successors
-
-We recommend inviting another {% data variables.product.company_short %} user to be your successor, to manage your user owned repositories if you cannot. As a successor, they will have permission to:
-
-* Archive your public repositories.
-* Transfer your public repositories to their own user owned account.
-* Transfer your public repositories to an organization where they can create repositories.
-
-Successors cannot log into your account.
-
-An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see [AUTOTITLE](/free-pro-team@latest/site-policy/other-site-policies/github-deceased-user-policy).
-
-To request access to manage repositories as a successor, please contact us through the {% data variables.contact.contact_support_portal %}.
 
 ## Inviting a successor
 

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md

@@ -1,6 +1,6 @@
 ---
 title: Removing a collaborator from a personal repository
-intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
+intro: 'You can remove a collaborator from your personal repository at any time.'
 redirect_from:
   - /articles/how-do-i-remove-a-collaborator
   - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
@@ -22,9 +22,6 @@ topics:
   - Repositories
 shortTitle: Remove a collaborator
 ---
-## Deleting forks of private repositories
-
-While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
 
 ## Removing collaborator permissions from a person contributing to a repository
 
@@ -33,7 +30,6 @@ While forks of private repositories are deleted when a collaborator is removed,
 {% data reusables.repositories.click-collaborators-teams %}
 1. To the right of the collaborator you want to remove, click **Remove**.
 
-## Further reading
+## Next steps
 
-* [AUTOTITLE](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)
-* [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/removing-an-outside-collaborator-from-an-organization-repository)
+* For reference information, see [AUTOTITLE](/account-and-profile/reference/permission-levels-for-a-personal-account-repository#removing-a-collaborator).

content/account-and-profile/reference/permission-levels-for-a-personal-account-repository.md

@@ -66,6 +66,12 @@ The repository owner has full control of the repository. In addition to the acti
 
 ## Collaborator access for a repository owned by a personal account
 
+{% ifversion fpt or ghec %}
+
+{% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people. For more information, see [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch).
+
+{% endif %}
+
 Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
 
 > [!NOTE]
@@ -95,6 +101,10 @@ Collaborators can also perform the following actions.
 | {% endif %} |
 | Remove themselves as collaborators on the repository | [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository) |
 
-## Further reading
+If you want more granular control of permissions to the repository, you can create a repository within an organization. For more information, see [AUTOTITLE](/get-started/learning-about-github/access-permissions-on-github).
+
+## Removing a collaborator
+
+While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
 
-* [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)
+When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.