|
1 | 1 | ---
|
2 | 2 | title: Limiting interactions in your organization
|
3 |
| -intro: 'Organization owners can temporarily restrict certain users from commenting, opening issues, or creating pull requests in the organization''s public repositories to enforce a period of limited activity.' |
| 3 | +intro: 'You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your organization.' |
4 | 4 | redirect_from:
|
5 | 5 | - /github/setting-up-and-managing-organizations-and-teams/limiting-interactions-in-your-organization
|
6 | 6 | - /articles/limiting-interactions-in-your-organization
|
7 | 7 | versions:
|
8 | 8 | free-pro-team: '*'
|
| 9 | +permissions: Organization owners can limit interactions in an organization. |
9 | 10 | ---
|
10 | 11 |
|
11 |
| -After 24 hours, users can resume normal activity in your organization's public repositories. When you enable organization-wide activity limitations, you can't enable or disable interaction limits on individual repositories. For more information on per-repository activity limitation, see "[Limiting interactions in your repository](/articles/limiting-interactions-in-your-repository)." |
| 12 | +### About temporary interaction limits |
12 | 13 |
|
13 |
| -{% tip %} |
| 14 | +Limiting interactions in your organization enables temporary interaction limits for all public repositories owned by the organization. {% data reusables.community.interaction-limits-restrictions %} |
14 | 15 |
|
15 |
| -**Tip:** Organization owners 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](/articles/blocking-a-user-from-your-organization)." |
| 16 | +{% data reusables.community.interaction-limits-duration %} After the duration of your limit passes, users can resume normal activity in your organization's public repositories. |
16 | 17 |
|
17 |
| -{% endtip %} |
| 18 | +{% data reusables.community.types-of-interaction-limits %} |
| 19 | + |
| 20 | +Members of the organization are not affected by any of the limit types. |
| 21 | + |
| 22 | +When 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](/articles/limiting-interactions-in-your-repository)." |
| 23 | + |
| 24 | +Organization owners 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](/articles/blocking-a-user-from-your-organization)." |
| 25 | + |
| 26 | +### Limiting interactions in your organization |
18 | 27 |
|
19 | 28 | {% data reusables.profile.access_profile %}
|
20 | 29 | {% data reusables.profile.access_org %}
|
21 | 30 | {% data reusables.organizations.org_settings %}
|
22 |
| -4. In your organization's Settings sidebar, click **Interaction limits**. |
23 |
| - |
24 |
| -5. Under "Temporary interaction limits", click one or more options. |
| 31 | +1. In the organization settings sidebar, click **Moderation settings**. |
| 32 | +  |
| 33 | +1. Under "Moderation settings", click **Interaction limits**. |
| 34 | +  |
| 35 | +{% data reusables.community.set-interaction-limit %} |
25 | 36 | 
|
26 |
| - - **Limit to existing users**: Limits activity for organization users with accounts that are less than 24 hours old who do not have prior contributions and are not collaborators. |
27 |
| - - **Limit to prior contributors**: Limits activity for organization users who have not previously contributed and are not collaborators. |
28 |
| - - **Limit to repository collaborators**: Limits activity for organization users who do not have write access or are not collaborators. |
29 | 37 |
|
30 | 38 | ### Further reading
|
31 | 39 | - "[Reporting abuse or spam](/articles/reporting-abuse-or-spam)"
|
|
0 commit comments