Add content about FGP for org-level Copilot usage metrics (#58918)

content/copilot/concepts/copilot-metrics.md

@@ -51,10 +51,14 @@ License and seat management data are not included in {% data variables.product.p
 
 ## How are metrics attributed across organizations?
 
+> [!NOTE]
+> You can grant **organization-only visibility** into {% data variables.product.prodname_copilot_short %} usage metrics without providing enterprise-level access.
+>
+> You can do this by creating an organization custom role that includes the "View organization {% data variables.product.prodname_copilot_short %} metrics" permission, and assigning that role to users who need visibility into metrics for a single organization. See [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles).
+
 Organization-level {% data variables.product.prodname_copilot_short %} usage metrics are based on organization membership, not on where individual actions occur. To appear in an enterprise’s metrics, a user must have an active {% data variables.product.prodname_copilot_short %} seat assigned within that enterprise (in any organization that belongs to the enterprise). As a result, a single user’s usage may appear in multiple organization dashboards, while that same user is counted only once in the enterprise-level total. Organization-level analytics are intended for visibility into adoption and usage within an organization and are not designed to be directly compared to enterprise-level totals.
 
-Organization-level {% data variables.product.prodname_copilot_short %} analytics are available starting December 12, 2025. This is the first date for which organization-level reports are provided. 
-
+Organization-level {% data variables.product.prodname_copilot_short %} analytics are available starting December 12, 2025. This is the first date for which organization-level reports are provided.
 
 Once a user has a seat in the enterprise, their usage is attributed to **every organization they belong to**, regardless of where the seat is assigned.
 

content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-organization-roles.md

@@ -69,6 +69,9 @@ Organization permissions do not grant read, write, or administrator access to an
 | {% ifversion secret-scanning-alert-dismiss-custom-role %}                                        |
 | Review and manage {% data variables.product.prodname_secret_scanning %} alert dismissal requests | Review and manage {% data variables.product.prodname_secret_scanning %} alert dismissal requests for your organization. | [AUTOTITLE](/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/enabling-delegated-alert-dismissal-for-secret-scanning) |
 | {% endif %}                                                                                      |
+| {% ifversion copilot %}                                  |
+| View organization {% data variables.product.prodname_copilot_short %} metrics                    | View {% data variables.product.prodname_copilot_short %} usage metrics for your organization. | [AUTOTITLE](/copilot/concepts/copilot-metrics) |
+| {% endif %}                                                                                    |
 
 {% endrowheaders %}
 

data/reusables/organizations/additional-permissions.md

@@ -9,7 +9,7 @@
 
 For more information, see [AUTOTITLE](/discussions).
 
-### Issue and Pull Requests
+### Issue and pull requests
 
 * Assign or remove a user
 * Add or remove a label
@@ -21,14 +21,14 @@ For more information, see [AUTOTITLE](/discussions).
 * Delete an issue
 * Mark an issue as a duplicate
 
-### Merge Queue
+### Merge queue
 
 * Request a solo merge
 * Jump to the front of the queue
 
 For more information, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue).
 
-### Pull Request
+### Pull request
 
 * Close a pull request
 * Reopen a closed pull request