There are multiple ways to engage users on the Amplifier platform. Here, we will outline a few ways to engage users manually and using automation.

Send Messages To Users From The Users Grid

When you need to send a custom message to a specific user, or multiple users you can do so through the users grid. Navigate to "Health Dashboard" and then the "Users" tab. Find the user(s) you want to message and select them using the checkbox in the first column. Notice an Action Bar appears at the bottom of the screen. The action bar shows how many users are selected, and has a Chat Bubble button on the far right of the bar. Click the Chat Bubble () to send a custom message as Ampy. 

After clicking the Chat Bubble button, a custom message modals appears. Select the engagement channel, e.g. Slack or Email, and enter your custom message.

Send Messages To Users From The Findings Grid

When you need to send a custom message to a specific user, or multiple users you can do so through the findings grid. This also allows you to include context of a related finding. The findings grid can be found in two locations.

1. User Profile
   1. Navigate to "Health Dashboard"
   2. Click the "Users" tab
   3. Find the user(s) you want to message and click the name
   4. the findings grid will be located at the bottom of the user's profile view
2. Findings Grid View
   1. Navigate to "Security Findings"
   2. Apply and remove any required filters

Once you are on the findings grid, select specific findings using the checkbox in the first column. Notice an Action Bar appears at the bottom of the screen. The action bar shows how many findings are selected, and has a Chat Bubble button on the far right of the bar. Click the Chat Bubble to send a custom message as Ampy.

After clicking the Chat Bubble button, a custom message modals appears. Select the engagement channel, e.g. Slack or Email, and enter your custom message.

Send Engagements To Users From The Findings Grid

This is the fastest and way to trigger an engagement for a specific finding. The Engagement Flow can be in any state when manually sending the engagement, i.e. ACTIVE, PAUSED, or GHOST. The findings grid can be found in two locations.

1. User Profile
   1. Navigate to "Health Dashboard"
   2. Click the "Users" tab
   3. Find the user(s) you want to message and click the name
   4. the findings grid will be located at the bottom of the user's profile view
2. Findings Grid View
   1. Navigate to "Security Findings"
   2. Apply and remove any required filters

Once you are on the findings grid, select specific findings using the checkbox in the first column. Notice an Action Bar appears at the bottom of the screen. The action bar shows how many findings are selected, and has a Arrow Flow button on the far right of the bar. Click the Arrow Flow to trigger engagements as Ampy.

After clicking the Flow Arrow button, an engagement modals appears. It show how many users might be engaged, and which engagements might trigger. Note that the the engagements might not trigger if there are cohort restrictions in place. Enable the following options based on your use case.

• Override working hours - When checked the engagement is triggered as soon as possible. If sending these outside of working hours, it might be a good idea to leave this unchecked so that the user gets a Slack or Teams notification during working hours the next day.
• Override ghost or inactive mode - by default only ACTIVE engagement flows are triggered, but this allows you to trigger flows that are in the PAUSED or GHOST state while developing and testing the flows. When checked, engagements will send live Slack or Teams messages to users.

Send Engagements To Users with Amplifier Automation

The simplest option is to rely on the Amplifier Platform to automatically trigger engagements when findings are discovered. This can easily be accomplished by changing an Engagement Flow's status to ACTIVE. Navigate to "AI Automation Studio". The status column contains a drop down allowing you to easily change the status. Change to this column are saved automatically and do not need to be published. Note that it might take up to 10 minutes for engagement flow states to trickle through the system causing a slight delay in sending out engagements after the status has been changed.

• ACTIVE - engagements are sent directly to the end user upon discovery. If a QA channel is configured in Slack, engagements are also sent there.
• PAUSED - engagements are not processed for this flow configuration.
• GHOST - engagements are NOT send to end users. They are only sent to a QA channel if one is configured for Slack.