> 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/details/events.md).

# Events

The **event log** records what happens in your account and in your subscriptions.

It is a single log that is presented in **two ways**, depending on where you view it.

### The two views

| Where                   | Columns                                                | What it's for                                                                                       |
| ----------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------- |
| **My Profile > Events** | Scope · Message · Date                                 | See a summary of what happened and when.                                                            |
| **Home > Events**       | Event · IP · User · Organization · Subscription · Date | See the activity in more detail: who, from where, in which organization, and on which subscription. |

Both views allow you to **filter** to narrow down what you're looking for, and the Home view also includes the option to **Export** the log. On Home, the tabs **My events** and **Customer events** separate your activity from that of your customers.

### What each column records

* **Scope** — the area the event refers to (for example, Servers).
* **Event** — the type of action recorded (for example, Subscription - Signup, User - Valid login, or User - Logout).
* **Message** — the description of what happened, with a success or error indicator.
* **IP** — the IP address it came from, with its country.
* **User** — the user who triggered the event.
* **Organization** — the organization where it occurred.
* **Subscription** — the affected subscription, when applicable.
* **Date** — the date and time of the event.

### Event details

When you open an event, its full details are shown, with these fields:

| Field      | What it shows                                                 |
| ---------- | ------------------------------------------------------------- |
| Level      | The severity or type of the event (for example, Information). |
| Type       | The specific action (for example, User - Valid login).        |
| IP         | The source IP address.                                        |
| Country    | The country associated with that IP.                          |
| Message    | The description of what happened.                             |
| User agent | The browser and operating system it came from.                |
| Date       | The date and time of the event.                               |

### Session states

In access events, the state of the associated session may appear:

| State    | Meaning                                             |
| -------- | --------------------------------------------------- |
| Active   | The session is still open and in use.               |
| Inactive | The session exists, but is not active at this time. |
| Closed   | The session has been closed.                        |

### Next steps

* Learn how to view and export the log in the [How-to guides.](/docs-en/platform/accounts/how-to.md)
* Return to the concept in [My Profile.](/docs-en/platform/accounts/concepts/my-profile.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/platform/accounts/details/events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.