Skip to content

Commit 66401f3

Browse files
authored
Update time criteria for a dormant user (#53979)
1 parent 1c2ccb6 commit 66401f3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-dormant-users.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ topics:
2929
When assessing user dormancy, we only consider organizations, repositories, or sign-on events that are associated with the enterprise. For example, a user who has recently commented on an issue in a public repository outside of the enterprise may be considered dormant, while a user who has commented on an issue in a public repository within the enterprise will not be considered dormant.
3030
{% endif %}
3131

32-
A user account is considered to be dormant if the user {% ifversion ghec %} hasn't performed any of the previous activities in the past 90 days.{% elsif ghes %} meets the following criteria:
32+
A user account is considered to be dormant if the user {% ifversion ghec %} hasn't performed any of the previous activities in the past 30 days.{% elsif ghes %} meets the following criteria:
3333

3434
* The user's account has existed for longer than the dormancy threshold {% data variables.location.product_location %}.
3535
* The user hasn't performed any of the previous activities within the dormancy threshold.

0 commit comments

Comments
 (0)