> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-view-and-export-events.md). # How to Review and Export Your Events Review your account's event log, narrow it down with filters, and export it whenever you need to. Check the event log to see what has happened in your account and subscriptions: logins, sign-ups, or errors. It's a single log, but you can access it from three places, depending on the scope you need, and export it whenever you want. > #### 📘 **What will you get?** > > Find the events you're interested in from the place that suits you best and, if you need to, download them to save them or review them outside the platform. ### Before you begin You need to be logged in. The log is the same in the three places; what changes is the scope and the level of detail: * **My Profile > Events** — your personal activity, in summary view. * **Home > Events** — all your activity, aggregated across your organizations, in detailed view. * **Organization > Events** — the activity of a single organization, in detailed view. ### From My Profile Open the **user menu** (bottom left), go to **My Profile** and open the **Events**. It is the summary view of **your** activity, with three columns: **Area**, **Message** (with a status icon, green if successful and red if there was an error) and **Created**. You can sort by any of them and narrow it down with **Filters**. ![My Profile > Events, summary view of your activity](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FCR0STa6As830yRWGkysR%2FEventos.png?alt=media\&token=86049e61-167c-4a5a-a717-0a0650d6893e) ### From Home In **Home > Events** you can see the aggregated activity of all your organizations, in detailed view. The columns are **Event**, **IP**, **User**, **Organization**, **Subscription** and **Created**, all sortable. At the top you have **Filters** and **Export**. ![Home > Events, detailed view of all your organizations](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FtgwcNTsZCpm79AL0udsD%2FEventos_N1.png?alt=media\&token=b27ae153-bb2b-4b10-9439-fa3969066434) ### From an organization With an organization selected, go to **Organization > Events**. You only see the activity of that organization, also in detailed view, with the columns **Event**, **IP**, **User**, **Subscription** and **Created**. Since you're already in an organization, the Organization column does not appear here. You also have **Filters** and **Export**. ![Organization > Events, detailed view of a single organization](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F7dXe1MBSpYzarmTXtxKo%2FEventos_N3.png?alt=media\&token=d2d67f69-2332-4730-800e-669dff3715a3) ### View event details In detailed views, click any row to open its details **Event data**, with all its information: **Level**, **Type**, **IP**, **Country**, **Message**, **User agent** and **Date**. Click **Close** to return to the list. ![Event data details](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Ft2t2Q51ouycIdglyTVOZ%2FEvento_de_Ejemplo_N3.png?alt=media\&token=8d039069-34e1-4ac7-827c-3da032106843) ### Narrow it down with filters Click **Filters** to reduce the list to what you're looking for. In detailed views you can filter by **Level**, **Type**, **Scope**, **User**, **Organization** and **Session status**. Combine them to find a specific event. ![Event log filters](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FTr4uX45CJSQQ5ZY3U1ve%2FFiltros.png?alt=media\&token=085fdd58-cbf9-4a28-8b1a-f08e80dfaaf7) ### Export the log In detailed views (Home or Organization), click **Export**, in the top right, to download the events. > #### 🚧 **Export format** > > When you consult this guide, confirm in the panel the format of the file generated by Export. ### Conclusion The event log gives you traceability of what happens in your account and subscriptions. You have three entry points depending on what you're looking for: your activity in My Profile, the global activity on Home, and that of a specific company in its organization. Check it whenever you need to verify a login or an action, and export it if you want to keep it separately. ### Next steps * Review what each column and each status means in [Events.](/docs-en/platform/accounts/details/events.md) * Return to the panel overview in [The panel.](/docs-en/platform/organizations/concepts/the-organization-panel.md) --- # 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.plenit.com/docs-en/platform/accounts/how-to/how-to-view-and-export-events.md?ask=&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.