From 9e5604d4a3e2bffcbc85c97e8c593bd29fe1e2b0 Mon Sep 17 00:00:00 2001 From: emmaviolet Date: Fri, 10 Jun 2022 15:34:44 +0100 Subject: [PATCH 1/3] Clarifies what is included in GHEC user dormancy reports --- .../managing-dormant-users.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md index 23956f2557b3..214df67d2729 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md @@ -62,4 +62,13 @@ topics: 1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**. ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png) +{% tip %} + +**Tip** +For the purposes of assessing user dormancy, user activity is scoped to include only user activity associated with organizations, repositories, or sign-on events that are associated with the enterprise. For example, if a user has recently commented on an issue in a public repository not associated with the enterprise, they may be considered dormant; however, if they have recently commented on an issue in a public repository associated with an organization in your enterprise, they will not be considered dormant and will not appear on a dormant user report. + +In the case of web sign-on events, only sign-on events through via an SSO domain associated with your enterprise are considered user activity associated with the enterprise. + +{% endtip %} + {% endif %} From c9361b4bb4caf4bf9aad4fa45cbcb4a661873e6f Mon Sep 17 00:00:00 2001 From: Emma Makinson Date: Fri, 17 Jun 2022 14:22:38 +0100 Subject: [PATCH 2/3] wording tweaks Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com> --- .../managing-users-in-your-enterprise/managing-dormant-users.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md index 214df67d2729..f857694b507f 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md @@ -65,7 +65,7 @@ topics: {% tip %} **Tip** -For the purposes of assessing user dormancy, user activity is scoped to include only user activity associated with organizations, repositories, or sign-on events that are associated with the enterprise. For example, if a user has recently commented on an issue in a public repository not associated with the enterprise, they may be considered dormant; however, if they have recently commented on an issue in a public repository associated with an organization in your enterprise, they will not be considered dormant and will not appear on a dormant user report. +For the purposes of assessing user dormancy, user activity is scoped to include only user activity associated with organizations, repositories, or sign-on events that are associated with the enterprise. For example, if a user has recently commented on an issue in a public repository not associated with the enterprise, they may be considered dormant. However, if they have recently commented on an issue in a public repository associated with an organization in your enterprise, they will not be considered dormant and will not appear in the Dormant User report. In the case of web sign-on events, only sign-on events through via an SSO domain associated with your enterprise are considered user activity associated with the enterprise. From adcb8ff78f777ce3d5f7b1003ed04deab744b63e Mon Sep 17 00:00:00 2001 From: Emma Makinson Date: Fri, 17 Jun 2022 14:22:52 +0100 Subject: [PATCH 3/3] Adds colon Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com> --- .../managing-users-in-your-enterprise/managing-dormant-users.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md index f857694b507f..220d91b4dd31 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md @@ -64,7 +64,7 @@ topics: {% tip %} -**Tip** +**Tip:** For the purposes of assessing user dormancy, user activity is scoped to include only user activity associated with organizations, repositories, or sign-on events that are associated with the enterprise. For example, if a user has recently commented on an issue in a public repository not associated with the enterprise, they may be considered dormant. However, if they have recently commented on an issue in a public repository associated with an organization in your enterprise, they will not be considered dormant and will not appear in the Dormant User report. In the case of web sign-on events, only sign-on events through via an SSO domain associated with your enterprise are considered user activity associated with the enterprise.