{"meta":{"title":"Limiting interactions in your organization","intro":"You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your organization.","product":"Building communities","breadcrumbs":[{"href":"/en/communities","title":"Building communities"},{"href":"/en/communities/moderating-comments-and-conversations","title":"Moderation"},{"href":"/en/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization","title":"Limit interactions in org"}],"documentType":"article"},"body":"# Limiting interactions in your organization\n\nYou can temporarily enforce a period of limited activity for certain users in all public repositories owned by your organization.\n\n## About temporary interaction limits\n\nLimiting interactions in your organization enables temporary interaction limits for all public repositories owned by the organization. Enabling an interaction limit for a repository restricts certain users from commenting, opening issues, creating pull requests, reacting with emojis, editing existing comments, and editing titles of issues and pull requests.\n\nWhen you enable an interaction limit, you can choose a duration for the limit: 24 hours, 3 days, 1 week, 1 month, or 6 months. After the duration of your limit passes, users can resume normal activity in your organization's public repositories.\n\nThere are three types of interaction limits.\n\n* **Limit to existing users:** Limits activity for users with accounts that are less than 24 hours old who do not have prior contributions and are not collaborators.\n* **Limit to prior contributors:** Limits activity for users who have not previously contributed to the default branch of the repository and are not collaborators.\n* **Limit to repository collaborators:** Limits activity for users who do not have write access to the repository.\n\nMembers of the organization are not affected by any of the limit types.\n\nWhen you enable organization-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on limiting activity for an individual repository, see [Limiting interactions in your repository](/en/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository).\n\nOrganization owners and moderators can also block users for a specific amount of time. After the block expires, the user is automatically unblocked. For more information, see [Blocking a user from your organization](/en/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization).\n\n## Limiting interactions in your organization\n\n1. In the upper-right corner of GitHub, click your profile picture, then click ** Organizations**.\n\n2. Select an organization by clicking on it.\n\n3. Under your organization name, click ** Settings**. If you cannot see the \"Settings\" tab, select the **** dropdown menu, then click **Settings**.\n\n \n\n4. *For organization owners:* In the \"Access\" section of the sidebar, select ** Moderation**, then click **Interaction limits**.\n\n *For organization moderators:* In the sidebar, click **Interaction limits**.\n\n5. Under \"Temporary interaction limits\", to the right of the type of interaction limit you want to set, select the **Enable** dropdown menu, then click the duration you want for your interaction limit.\n\n## Limiting concurrent open pull requests for users without write access\n\nAcross all public repositories owned by your organization, you can set a maximum number of pull requests that a user without write access can have open at the same time. This limit applies separately to each repository, so a user without write access can have up to the configured maximum number of open pull requests in *each* public repository owned by the organization, not across the organization as a whole. When a user without write access reaches the limit in a repository, they must close an existing pull request or wait for someone with write access to merge one before they can open a new one.\n\nThis setting helps maintainers manage contribution volume by preventing users from opening an excessive number of pull requests, which can overwhelm review queues and trigger unnecessary CI runs. The limit only applies to users without write access—users with write access or higher are not affected.\n\nDraft pull requests do not count toward a user's limit. Only open, non-draft pull requests are counted when determining whether a user has reached the maximum.\n\nThe organization-level limit takes precedence, but if a repository owned by your organization has its own pull request limit configured after the organization-level limit, the repository-level limit overrides the organization-level limit. See [Limiting interactions in your repository](/en/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository#limiting-concurrent-open-pull-requests-for-users-without-write-access).\n\n### Configuring the pull request limit\n\nTo configure the pull request limit, navigate to the **Interaction limits** settings page following the same steps described in [Limiting interactions in your organization](#limiting-interactions-in-your-organization), then under **Pull request limits**, select the maximum number of concurrent open pull requests allowed for users without write access. You can also use the REST API to configure the pull request limit. See [REST API endpoints for organization interactions](/en/rest/interactions/orgs#update-pull-request-creation-cap-for-an-org).\n\n## Further reading\n\n* [Reporting abuse or spam](/en/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)\n* [Managing an individual's access to an organization repository](/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-an-individuals-access-to-an-organization-repository)\n* [Permission levels for a personal account repository](/en/repositories/managing-your-repositorys-settings-and-features/repository-access-and-collaboration/permission-levels-for-a-personal-account-repository)\n* [Repository roles for an organization](/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization)\n* [Managing moderators in your organization](/en/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)"}