> 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/premium-table/formula-syntax/identifiers/loggedin_email.md).
# LOGGEDIN\_EMAIL
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 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.inforiver.com/premium-table/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 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.