--- title: "Signals" slug: "signals" updated: 2024-09-22T20:56:19Z published: 2024-09-22T20:56:19Z canonical: "docs.processmaker.com/signals" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.processmaker.com/llms.txt > Use this file to discover all available pages before exploring further. # Signals > [!TIP] > [**Plan Availability:**](https://www.processmaker.com/products/pricing/) ![Professional](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Standard.png)![Professional](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Professional.png)![Enterprise](https://cdn.document360.io/2d311614-fcb7-4424-8b4c-d4d3091eebeb/Images/Documentation/Enterprise.png) ## BPMN 2.0 Signals Signals communicate information from one isolated Process model element to another. Signals are part of the [BPMN 2.0 specification](https://www.omg.org/spec/BPMN/2.0/About-BPMN/) to broadcast or receive data from a broadcast across Processes, and/or Pools within the same Process model. Similar to radio broadcasting, one Signal-type element designed to broadcast [Request data](/v1/docs/request-data-and-json) broadcasts that data, while another Signal-type element designed to listen for that Signal from a potentially isolated Process model element receives none, all, or part of that Request data from the broadcasting element. These are throwing Signal-type elements that broadcast Request data: - [Intermediate Signal Throw Event](/v1/docs/intermediate-signal-throw-event) element - [Signal End Event](/v1/docs/signal-end-event) element These are catching Signal-type elements that listen for a broadcasting Signal to receive part of or its complete Request data: - [Signal Start Event](/v1/docs/signal-start-event) element - [Intermediate Signal Catch Event](/v1/docs/intermediate-signal-catch-event) element - [Boundary Signal Event](/v1/docs/boundary-signal-event) element [Signal Manager](/v1/docs/signals) contains all Signals regardless of whether they are used for broadcasting or listening BPMN elements. Signal-type Process model elements may then subscribe (or use) that Signal. ## Collection Signals Each [Collection](/v1/docs/collections) has [three Signals that may independently be enabled or disabled to broadcast its Signal](/v1/docs/configure-a-collection#enable-collection-signals-for-subscription) when each occurrence of the following functions in that Collection: - **Create a Collection record:** [A new Collection record is created](/v1/docs/create-a-new-collection-record). - **Edit a Collection record:** [A Collection record is edited](/v1/docs/edit-a-collection-record). - **Delete a Collection record:** [A Collection record is deleted](/v1/docs/delete-a-collection-record). Each Collection's Signals are created and display in Signal Manager when that Collection is created. Any Signal-type Process model element that subscribes to (uses) a Collection Signal listens for when one of these Collection Record events occur. For example, a Signal Start Event element may listen for when a record in the Collection associated with that Signal is created. Manage Collection Signals from Signal Manager. ## User Signals User Signals broadcast information pertaining to four user-type events. User Signals may be enabled or disabled independently of one another. Follow these steps to use a User Signal: 1. [Create a Signal](/v1/docs/create-a-new-signal) in Signal Manager. In the **Signal ID** setting for the new Signal, use the Signal ID value for the corresponding user-type event from the following table. For example, to create a Signal that triggers each time a new user account is created, enter `user_create` in its **Signal ID** setting. 2. [Enable the toggle key for that user-type event](/v1/docs/user-signals-settings#enable-or-disable-a-user-signal). If that user-type event's toggle key is not enabled when that Signal is to trigger, that Signal does not trigger. Administrators may control when these user-type events may occur regardless of how Process Designers implement those Signals in Process models. Any Signal-type Process model element that subscribes to (uses) a User Signal listens for when one of these user-type events occur. For example, a [Signal Start Event](/v1/docs/signal-start-event) element may listen for when a new user is created to start a Request that requisitions equipment for that user. Similarly, use a "Delete" User Signal to start a Request that offboards the deleted user's access from organizational applications, infrastructure, and resources. Below is a description of each user-type event and the Signal ID value to use for its corresponding Signal. | User-Type Event | Description of Event | Signal ID | | --- | --- | --- | | Create | [A new user account is created](/v1/docs/create-a-new-user-account). | `user_create` | | Delete | [A user account is deleted](/v1/docs/deleted-user-accounts). | `user_update` | | Read | A user account is accessed in either of the following ways: - [A user account is viewed](/v1/docs/user-accounts#view-all-scripts). - [A user profile is viewed](/v1/docs/profile-settings#view-another-users-profile-information). | `user_read` | | Update | [A user account is edited](/v1/docs/edit-a-user-account). | `user_delete` | When a User Signal event triggers, the following occurs: - That User Signal broadcasts the `_user` [Magic Variable](/v1/docs/magic-variables) containing the user account affected by that User Signal event. For example, the full name set in the affected user account is accessible with JSON dot notation as `_user.fullname`. See the `_user` Magic Variable to reference any JSON object within this Magic Variable. - The User Signal event broadcasts any User Enhanced Properties and the affected user account's corresponding values. Manage User Signals from the [**User Signals** tab](/v1/docs/user-signals-settings) in **Settings**. ## Related - [View and Search for Signals](/view-and-search-for-signals.md) - [Create a New Signal](/create-a-new-signal.md) - [Edit a Signal](/edit-a-signal.md) - [Delete a Signal](/delete-a-signal.md)