> For the complete documentation index, see [llms.txt](https://help.blinger.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blinger.io/documentation/settings/advanced.md).

# Subtab: Advanced

## General information

In this tab you can receive the access to:

* Action log
* Block send/receive files to a specific group of operators
* Email whitelist for downloading conversations
* Hide personal data from operators
* IP address whitelist
* Iframe integration
* Manage Webhooks

{% hint style="info" %}
By default, the access to these settings is restricted. Contact Blinger.io Support to get the access
{% endhint %}

## Action log

![](/files/-LnmNa7OQ3xIJC8N93Zk)

Information on each committed action of a super-admin or operator is recorded and displayed in the Action log. Information is displayed in the following order:

* the name of the account that performed the action
* account name for which the action was committed
* type of action
* IP address of the account that committed the action
* date and time of action
* action note

## Block send/receive files

This function allows you to prohibit receiving and sending files to specific groups of operators.

To configure, it is necessary to mark the type of action (receiving / sending), which must be prohibited for a particular group of operators.

![](/files/-LnmR-0O4DiN5tGwrMlW)

## List of email addresses for downloading conversations

The function allows you to limit the ability for operators to download correspondence with end-users and write down specific email addresses to which downloading is possible.

{% hint style="warning" %}
Super-admin account is not affected by this feature.
{% endhint %}

To configure, you must activate the "Restrict email addresses" and enter the email addresses to which the downloading of correspondence will be allowed.

![](/files/-LnmSb4VRwuLFnelcq0N)

## Hide personal data

The function allows you to hide from the operators of specific groups the personal data (contact) of end-users transmitted by social networks and instant messengers to Blinger.io.

{% hint style="warning" %}
Super-admin account is not affected by this feature.
{% endhint %}

To configure you need:

1. Activate "Hide data for all operators besides Super-Admin
2. If you want to hide the avatars there will activate "Hide avatars"
3. Select those groups of operators for which this function won't work
4. Click "Save"

![](/files/-LnmTsPkZ-4xZ6Rroe3y)

## IP address whitelist

The function allows you to set specific IP-addresses by which operators can have access to Blinger.io.

To configure you need:

1. Activate function
2. Enter IP-addresses to whitelist which you can log in your Blinger.io account
3. Click "Save"

![](/files/-LnmY24LA_g7GfiNrZPF)

## Iframe integration

Iframe allows you to embed part of the Blinger.io web interface in a third-party web solution.

The example of implementing iframe integration with bpm'online: [**https://marketplace.bpmonline.com/app/blingerio-connector-bpmonline**](https://marketplace.bpmonline.com/app/blingerio-connector-bpmonline)

More information about the setup steps on the page.

{% hint style="info" %}
For full integration via iframe, we recommend using [**webhooks**](/documentation/webhooks.md)
{% endhint %}

## Manage Webhooks

Webhooks allow you to transfer json-formatted data about events that occurred in Blinger.io. A detailed description of all the features is available [**here**](https://help.blinger.io/documentation/webhooks).

This section allows to receive the direct access to the Webhooks panel.

![](/files/-LnmZUy6-pOJM9d324Kt)

{% hint style="warning" %}
Just Super-admin account has the access to Webhooks panel
{% endhint %}