> For the complete documentation index, see [llms.txt](https://docs.sumble.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sumble.com/system-setup-and-configuration/admin-portal/signal-configurations.md).

# Signal configurations

Create and manage the signal configurations that decide which signals your team gets.

A signal configuration is a standing rule, such as "any job post at my accounts that mentions Kubernetes". Each one produces [signals](https://docs.sumble.com/our-data/signals.md) of one type, at one priority, for the accounts your reps own. Manage them in the **Signal configurations** section of the **Configurations** tab in [My Team](https://docs.sumble.com/system-setup-and-configuration/admin-portal.md).

## Who can change them

* **Admins** on an Enterprise account with signals can create, edit, duplicate, reorder and delete configurations. Everyone at the company shares them.
* **Other Enterprise members** see them read-only.
* **Pro users** can edit or delete their own configurations, but not create new ones.
* **Champion alerts** are set up by Sumble. Ask your account team to change one.

## Create or edit a configuration

Click **Create Signal**, or click a row to edit it. In **Configure signal**:

| Field                                    | What it does                                                                                                                                                                                                                                                                        |
| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Signal name**                          | What reps see on the signal.                                                                                                                                                                                                                                                        |
| **Signal event type**                    | What kind of change triggers it, such as **First mention of tech in org**, **Recent hires in job function**, **Any mention of keyword in job listing** or **Funding round raised**. The types are explained in [Signals](https://docs.sumble.com/our-data/signals.md#signal-types). |
| **Filter**                               | Which events count: the technologies, job functions, projects, keywords, locations and other conditions. **Search with this filter** opens the matching search so you can check what it catches.                                                                                    |
| **Track increasing or decreasing trend** | For trend types, whether to alert on growth or decline.                                                                                                                                                                                                                             |
| **Minimum job level**                    | For hires, job function and mention types, the most junior level that counts.                                                                                                                                                                                                       |
| **Priority**                             | High, medium or low. Reps can filter alerts by priority.                                                                                                                                                                                                                            |
| **Sales play**                           | What your team should do when the signal appears.                                                                                                                                                                                                                                   |
| **Days to look back**                    | How far back to look for matching events.                                                                                                                                                                                                                                           |

The **Signal preview** on the right shows examples that match. Click **Create signal** or **Save changes**.

**Duplicate** copies a configuration, and **Delete** removes it after you confirm.

## Order matters

Each rep gets a limited number of signals per run, and Sumble fills that budget from the top of the list down. Drag rows to put the configurations that matter most at the top, so a busy one lower down can't crowd them out.

## Check how a configuration performs

The **Frequency** column shows how many signals each configuration sent in the last 7 days. To find configurations that are too noisy or too quiet, see [Tuning your signals](https://docs.sumble.com/web-app/account-intelligence/intent-signals/tuning-signals.md).
