> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/notifications/advanced-notifications/users-log.md).

# Users log

### What does the Users screen show in the advanced notifications module?

The Users screen in the Rich notification module keeps a log of all the users who open your app. It is simply a log of user sessions occurring on your app. 

You can view the following session date on the Users screen:

* Subscribed: Confirms if a user is subscribed to your app’s notifications. 
* Last active: A timestamp of the last time a user was active. 
* Usage duration: The total duration a user has logged on your app. 
* Sessions: The number of sessions a user has initiated.
* First session: A timestamp of the first time a user was active. 
* Device: The device the user is using – Android or iOS. 
* Language: The default language of the user’s mobile device. 

{% hint style="success" %}
This information is populated automatically as more sessions are logged on your app. 
{% endhint %}


---

# 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.appmysite.com/app/notifications/advanced-notifications/users-log.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.