> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/troubleshoot/idemia-morpho-unable-to-use-transaction-logs-and-manage-configuration-keys-in-mbtb.md).

# MBTB sections are unavailable

Restore MBTB functions when Transaction Logs, key management, and reader configuration sections are unavailable.

When MBTB sections are greyed out (Transaction Logs, Manage Configuration Keys, Controller Feedback, Event config, Wiegand, and Files Management), the reader must be in **on-demand security**.

1. Change the reader to the **on-demand security** setting. To put the reader into on-demand security, see the related page [Enable On-Demand Security](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/configure/idemia-readers-morpho-how-to-enable-the-on-demand-security-state.md), which explains how to enable the On-demand Security state on IDEMIA Morpho readers.
2. Connect with **TLS Configuration = None**.

You can connect to the reader with TLS Configuration Factory, but connecting with Factory leaves these sections greyed out and unusable.


---

# 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://help.security.gallagher.com/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/troubleshoot/idemia-morpho-unable-to-use-transaction-logs-and-manage-configuration-keys-in-mbtb.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.