> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/kmp/setup-luciq-for-kmp/setup-bug-reporting/customize-report-fields.md).

# Customize Report Fields

Control which attachments users can add to a bug report from your KMP app, set a disclaimer, and enable auto screen recording.

You can control which attachment types are available, set a disclaimer, and (on iOS) set a minimum character count for comments.

### Attachment types

Enable or disable screenshot, extra screenshot, gallery image, and screen recording:

{% code title="Kotlin" %}

```kotlin
BugReportingKmp.setEnabledAttachmentTypes(
    screenshot = true,
    extraScreenshot = true,
    galleryImage = true,
    screenRecording = true
)
```

{% endcode %}

### Auto screen recording

You can enable automatic screen recording and (on iOS) set the maximum duration:

{% code title="Kotlin" %}

```kotlin
BugReportingKmp.setAutoScreenRecordingEnabled(true)
// iOS only
BugReportingKmp.setAutoScreenRecordingDurationIOS(seconds = 30)
```

{% endcode %}

### Disclaimer text

Show a disclaimer before the user sends a report:

{% code title="Kotlin" %}

```kotlin
BugReportingKmp.setDisclaimerText("By submitting you agree to our privacy policy.")
```

{% endcode %}

### Comment minimum character count (iOS)

On iOS you can require a minimum number of characters in the comment field:

{% code title="Kotlin" %}

```kotlin
BugReportingKmp.setCommentMinimumCharacterCount(limit = 10, reportTypes = listOf(ReportType.Bug))
// null reportTypes = applies to all report types
BugReportingKmp.setCommentMinimumCharacterCount(limit = 5, reportTypes = null)
```

{% endcode %}

This is a no-op on Android.

### User consent

Add a consent step to the bug reporting flow (e.g. for privacy or terms). You can make it mandatory and optionally apply an action when selected:

{% code title="Kotlin" %}

```kotlin
BugReportingKmp.addUserConsent(
    key = "privacy_consent",
    description = "I agree to share my data for support purposes.",
    mandatory = true,
    checked = false,
    action = UserConsentActionType.DropLogs  // optional: e.g. drop logs when accepted
)
```

{% endcode %}

`UserConsentActionType` can be: `DropAutoCapturedMedia`, `DropLogs`, `NoChat`.

### Invocation options

Set default invocation options (e.g. require comment, hide thank-you dialog, email field behavior):

{% code title="Kotlin" %}

```kotlin
BugReportingKmp.setInvocationOptions(listOf(
    InvocationOptions.CommentFieldRequired,
    InvocationOptions.EmailFieldOptional
))
```

{% endcode %}


---

# 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.luciq.ai/kmp/setup-luciq-for-kmp/setup-bug-reporting/customize-report-fields.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.
