> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/formula-syntax/identifiers/loggedin_email.md).
# LOGGEDIN\_EMAIL
Retrieves the logged-in user’s email ID.
The **LOGGEDIN\_EMAIL** identifier returns the user email ID. It can be used along with a SETVALUE function to capture the user who updates a data input field.
### Example
The Last Updated At and Last Updated By housekeeping fields can be used to capture the user and time at which a data input field was updated. These fields however cannot be written back. Instead of using the built-in housekeeping columns, you can leverage the SETVALUE function with the LOGGEDIN\_EMAIL identifier and store the email ID in a text field.
In this example, we're capturing the user email ID when the status single select field is changed. The text fields can then be written back to the preferred destination(s).
Capture the email ID using the SETVALUE function
---
# 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.inforiver.com/formula-syntax/identifiers/loggedin_email.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.
