---
title: "Extension settings"
manual: "Event management and registration"
version: "8.6"
permalink: "https://docs.typo3.org/permalink/derhansen/sf_event_mgt:extconf@8.6"
source: "ForAdministrators/Configuration/Extension/Index.rst"
rendered: "2026-09-26T09:22:10+00:00"
---

# Extension settings {#extconf}

Some general settings can be configured in the Extension Configuration.

1.  Go to **Admin Tools > Settings > Extension Configuration**
1.  Choose **sf_event_mgt**

## Records {#records}

### Slug behaviour `slugBehaviour` {#slug-behaviour-slugbehaviour}

-   **slugBehaviour**

    -   *Type:* string, keyword
    -   *Default:* unique

    Choose one of the following slug behaviours:

    -   **uniqueInSite**

        The same slug can be used for news in different sites. Use this
        setting *only* if no event records are shared between sites.

    -   **unique**

        The same news title in different sites will lead to different slug names.

## E-Mail {#e-mail}

### Use FluidEmail for email notifications `useFluidEmail` {#use-fluidemail-for-email-notifications-usefluidemail}

-   **useFluidEmail**

    -   *Type:* bool
    -   *Default:*

    -   **If active, all notifications generated by the extension will be sent using**

        FluidEmail.

        Note, that the body content of the email is rendered using the internal
        `FluidRenderingService` and then send using the TYPO3 system email layout.
        So if you want to change the email content, the templates in
        `Resources/Private/Notification/` must be overwritten.

## Payment {#payment}

### Enable payment method 'invoice' `enableInvoice` {#enable-payment-method-invoice-enableinvoice}

-   **enableInvoice**

    -   *Type:* bool
    -   *Default:* 1

    Enable payment method 'invoice'

### Enable payment method 'transfer' `enableTransfer` {#enable-payment-method-transfer-enabletransfer}

-   **enableTransfer**

    -   *Type:* bool
    -   *Default:* 1

    Enable payment method 'transfer'

## Backend {#backend}

### Hide registrations in event record by limit `hideInlineRegistrations` {#hide-registrations-in-event-record-by-limit-hideinlineregistrations}

-   **hideInlineRegistrations**

    -   *Type:* bool
    -   *Default:*

    Enable feature to hide registrations when editing an event in the backend

### Hide registrations in event record by limit `hideInlineRegistrationsLimit` {#hide-registrations-in-event-record-by-limit-hideinlineregistrationslimit}

-   **hideInlineRegistrationsLimit**

    -   *Type:* int
    -   *Default:* 500

    Max amount of registrations to display before event registrations will be hidden when editing an event.