> For the complete documentation index, see [llms.txt](https://docs.compliance.phalcon.blocksec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliance.phalcon.blocksec.com/manual/quick-start.md).

# Quick Start

This guide will walk you through the basic steps to effectively use the Phalcon Compliance App to monitor risks. Follow these core workflows to configure risk engines, scan for address risks, and receive timely alerts.

{% hint style="info" %}
**Looking to integrate via API?** Check out the [API Documentation](/api-documentation/introduction.md) for authentication, endpoints, and code examples.
{% endhint %}

## Review and Configure Risk Engines

A risk engine is a set of customizable rules that define the risks to be detected and trigger alerts. It is the core engine of your compliance monitoring system.

<figure><img src="/files/Qv5Xrp1BPw4XmZOcNzFj" alt="Risk Engines page overview"><figcaption></figcaption></figure>

### Review Default Risk Engines

We have preset 13 address risk engines and 12 transaction risk engines based on FATF guidelines and industry best practices. A detailed list of risk engines can be found here: [Default Risk Engine List](/manual/risk-engines/default-engines.md)

Actions:

* Navigate to the Risk Engines page (/risk-engines).
* Review the trigger conditions for each risk engine (e.g., value thresholds, risk indicators).
  * Adjust the conditions to match your business needs and regional requirements (e.g., changing a $50,000 threshold to $10,000).
* Ensure the required risk engines are enabled (toggle in the risk engine details).

## Screen Addresses or Transactions

### Scan an Address

Each address is automatically screened against all active address-type risk engines. You can screen addresses individually or through bulk import.

<figure><img src="/files/e9lhNgvUHung0ZGUlKsK" alt="Searching for an address in the search bar"><figcaption></figcaption></figure>

We searched for the address 0xc7A2aBc3b88f1465c4b3A4E7Bf2D2d59897851BB (Bybit Exploiter) and added it to Phalcon on the Ethereum chain.

<figure><img src="/files/cz5HPG6pdKDZKor4cvSx" alt="Adding an address to Phalcon on Ethereum" width="375"><figcaption></figcaption></figure>

After screening, this address has been identified with a **Critical** risk level and has triggered **3 unresolved alerts**, requiring immediate action.

<figure><img src="/files/4jxp9qEPxWTN51mIC38W" alt="Address screening result showing Critical risk level"><figcaption></figcaption></figure>

Click on the address to view its details, including basic information, screening information, and triggered alerts.

<figure><img src="/files/KVViCaSvmhtbpKjHnFVl" alt="Address details page with risk information and alerts"><figcaption></figcaption></figure>

#### Continuous Monitoring

Enable Monitor for an address to continuously track risk changes:

* Automatically detect new risks as transactions occur.
* Receive alerts when risk status changes — new risks detected or existing risks cleared.
* No manual re-screening needed — the system adjusts scan frequency based on address activity.

You can enable Monitor from the address details page or from the address list action menu. See [Monitor](/manual/monitor.md) for details.

### Screen a Transaction

Each transaction is automatically checked against all active transaction-type risk engines. On the Transactions page, you can screen transactions individually or through bulk import.

After searching for the transaction hash `0xde64ab6dccf27bda99fa7efdc2fcc58475859dae4fd95a8da267dc0994ab5971`, the system automatically retrieves and decodes the transfer details, allowing the user to select the transfer to be screened.

<figure><img src="/files/1LZnUuamR5S6klbVTTa7" alt="Selecting transfers to screen from a transaction" width="375"><figcaption></figcaption></figure>

After screening, this transaction has been identified with a **Critical** risk level and has triggered **2 unresolved alerts**, requiring immediate action.

<figure><img src="/files/411roXUmunhhhJNAM8Dd" alt="Transaction screening result showing Critical risk level"><figcaption></figcaption></figure>

Click on the transaction to view its details, including basic information, token transfers, and triggered alerts.

<figure><img src="/files/QRrC5vwMumoUhOVvET9B" alt="Transaction details page with risk information and alerts"><figcaption></figcaption></figure>

## Add Notification Channels

Add notification channels so that users can be immediately notified when an alert is triggered. Phalcon supports multiple notification channels, including email, Telegram, Slack, Lark, Discord, Pagerduty, and Webhook.

Here, we use Telegram as an example.

<figure><img src="/files/qUNy8H5qilOni0WeP7Ss" alt="Creating a Telegram notification channel" width="563"><figcaption></figcaption></figure>

To activate the Telegram notification channel, users should add the Phalcon Telegram Bot as a contact on Telegram. Click the link below to add this bot.

[@BlockSecPhalcon\_bot](https://t.me/BlockSecPhalcon_bot)

Then use the `/getchatid` command to get the chat ID. The Phalcon Telegram bot uses this chat ID to send alerts to the user's Telegram.

<figure><img src="/files/i7sDLcju0IEJxsty83Mk" alt="Getting chat ID from Phalcon Telegram bot"><figcaption></figcaption></figure>

You can also add the bot to a group, and the alert notifications will be sent to that group.

Notification channels should be bound to specific risk engines to be notified of alerts triggered by that particular risk engine.

<figure><img src="/files/MjBdiBNimOoqZvizNcZK" alt="Binding notification channels to risk engines"><figcaption></figcaption></figure>

To learn more details about the creation steps for each notification channel, visit [Notification Channels](/manual/notification-channels.md)

### Summary

After completing the steps above, the user has successfully created a risk engine, understood the address screening process, and linked notification channels, allowing for a seamless compliance workflow.

## Default Risk Engine List

For a complete list of all preset risk engines and their descriptions, see [Default Risk Engine List](/manual/risk-engines/default-engines.md).