Update managing-a-branch-protection-rule.md (#39236)

Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>

content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches.md

@@ -28,7 +28,7 @@ topics:
 ---
 ## About branch protection rules
 
-You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule.
+You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule. Actors may only be added to bypass lists when the repository belongs to an organization.
 
 By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings.
 

content/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule.md

@@ -55,6 +55,12 @@ For more information about each of the available branch protection settings, see
 
 When you create a branch rule, the branch you specify doesn't have to exist yet in the repository.
 
+{% note %}
+
+**Note:** Actors may only be added to bypass lists when the repository belongs to an organization.
+
+{% endnote %}
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.repository-branches %}