> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/retail-lending/help-center/faqs/logs.md).

# Logs

Short answers to common questions about Logs.

<details>

<summary>What does "Unattributed" mean in Changed by?</summary>

No person made the change, for example a sign-in recorded by the system. See [Change History](broken://pages/hnfZ2mjGTLJMpNRBpjFQ).

</details>

<details>

<summary>Why does a change have no channel?</summary>

Many changes made in the staff portal have no channel and show "-". To identify the source, open the change and read **Executed by** and **Workflow**. See [Change History](broken://pages/hnfZ2mjGTLJMpNRBpjFQ).

</details>

<details>

<summary>Why do I see in a change?</summary>

Passwords, MFA secrets and tokens are masked. A change to a masked value is still recorded, so the change detail shows that the value changed without revealing it. See [Change History](broken://pages/hnfZ2mjGTLJMpNRBpjFQ).

</details>

<details>

<summary>Can I share a payload from API Calls &#x26; Errors?</summary>

Share the correlation ID instead. Payloads hold data exchanged with providers, including phone numbers, street addresses, dates of birth from identity checks and IP addresses. See [API Calls & Errors](broken://pages/zju4J3WT3yx3VJ1hCAHF).

</details>

<details>

<summary>How do I find every email conversation for an application?</summary>

Search by the application ID, taken from the application's page address. Application numbers are matched in the email subject. See [Email Logs](broken://pages/bTq9PZoC5BWflcTS6rLQ).

</details>

<details>

<summary>Can one intake session create more than one application?</summary>

Yes. Each application appears under **Application**. See [Intake Sessions](broken://pages/i16W8u7qrHlsoFlSKapc).

</details>

<details>

<summary>Why don't the filters on API Calls &#x26; Errors work on every record?</summary>

**All statuses** filters API calls only. **All categories** and **All entity types** filter errors only. Select **API calls only** or **Errors only** first for a list of one record type. See [API Calls & Errors](broken://pages/zju4J3WT3yx3VJ1hCAHF).

</details>

<details>

<summary>What does a dash in place of a name mean in Operation Logs?</summary>

No signed-in user started the operation. An `HTTP_INBOUND` operation with no user and `HTTP 401` is a request that arrived without a valid sign-in. See [Operation Logs](broken://pages/hJqFBHgMmKwytSqlXuJE).

</details>

<details>

<summary>Which role can open Logs?</summary>

Tenant Administrator can open every Logs tab, and Loan Officer can open Logs. The other roles in the module access table can't. See [Module Access](broken://pages/EebOasKPKQhWq9ggrFQL).

</details>

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://2966508920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff06WQMAu97E0STor0yyS%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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.uptiq.ai/retail-lending/help-center/faqs/logs.md?ask=<question>&goal=<user_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.
