> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/organization-dashboard/organization-dashboard-v1/global-statistics.md).

# Global Statistics (Deprecated)

Global Statistics provides you global reports related to Events and Training and Certifications. These reports are not specific to a particular organization, these reports provides you data related across all organizations. These reports, charts and graphs provides you with the information related to the latest trends from the open source projects. It shows you the top enrolled trainings, top participated events, top speakers and many other details.

## Accessing Global Statistics

To access Global Statistics, perform the following steps:

1.Login to [Organization Dashboard](https://myorg.lfx.dev).

2.On the vertical sidebar navigation menu, click **Global Statistics**. You can select between **Events** and **Training & Certification**.

![Global Statistics](https://files.gitbook.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-MgAESFs0H7zYsmTgcOZ%2F-Mi7NB69PuSAdrxSlKmE%2F-Mi7OZ-fAf5G7RvYk1Jo%2FGlobal_Statitics.png?alt=media\&token=710f0ad4-6b12-440b-8da0-8f03356851c3)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.linuxfoundation.org/lfx/organization-dashboard/organization-dashboard-v1/global-statistics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
