1. Code42 Support
  2. Incydr
  3. Incydr administration
  4. Configuring

Configure message services

Updated

Overview

Incydr's Message Services enable you to send Code42 Instructor lessons to users via email, Microsoft Teams, and Slack. Email is always active, but Teams and Slack require some initial authorization and configuration steps before they can be used to send Code42 Instructor lessons to users. Configuration instructions for each message service are provided below.

Considerations

Configure message services

To configure message services, select Administration > Integrations > Message Services.

Message Services

Email

Email is always available as a message service. No configuration is required in order to email Code42 Instructor lessons to users in response to a change in position or their risky activity.

Incydr automatically creates a new email message in your default email client:

Customize the email sender address

  • Click Settings to customize the email sender address for Instructor lessons so users see lesson emails as coming from your domain, instead of from code42.com.
  • Instructor uses AWS SES to send lesson emails. To prevent emails from being blocked by email filters, add a Send Policy Framework (SPF) record in your DNS that allows AWS to send the email on your behalf. You may also connect with your email provider to accept AWS SES emails for your domain.
Set up mailto: links in your preferred email client
Although no additional configuration is required for email message services in Incydr, be sure to set up mailto: links so that they open correctly in your preferred webmail or desktop email client.

Microsoft Teams

Not available for Incydr Gov F1 and Gov F2 product plans

Authorize Microsoft Teams

To send messages from Incydr to users via Microsoft Teams, you must first download and install the Code42 app for Teams.

  1. Sign in to the Code42 console as a user with the Customer Cloud Admin role.
  2. Go to Administration > Integrations > Message Services.
  3. On the Microsoft Teams panel, click Authorize.
    Incydr requests access to your organization's Microsoft Teams instance, and lists the permissions required.
  4. Click Accept.
  5. Click Download Code42 app for Teams.
  6. Sign in to your Microsoft Teams client, then:
    1. Upload the Code42 app .zip file you downloaded above to Teams. Choose the Upload a custom app option. See Microsoft support for detailed instructions.
    2. Click Add to a team and choose the team with the members you want to receive messages from Incydr.
  7. From the Code42 console, view and edit Alert rules settings to specify which Code42 Instructor lessons to send to users via Teams.
Required Microsoft Teams settings
You must have permissions within Microsoft Teams to upload custom apps to your team, which may require you to:
  1. Enable custom apps in your org-wide default setting. (In the Org-wide app settings, set Allow interaction with custom apps to On.) See Microsoft support for detailed instructions.
  2. Create a custom app policy and assign it to the appropriate users. See Microsoft support for detailed instructions.

Deauthorize Microsoft Teams

To stop using the Microsoft Teams integration:

  1. Sign in to the Code42 console as a user with the Customer Cloud Admin role.
  2. Go to Administration > Integrations > Message Services.
  3. On the Microsoft Teams panel, click Deauthorize.
  4. In the confirmation dialog, click Got it, deauthorize.
    The connection between Code42 and Teams is removed. In addition, Code42 attempts to automatically uninstall and remove the Code42 app from your Team. Even if removal of the app fails, the connection is still deauthorized.

If the automated app removal failed and you plan to reauthorize later, you must first manually delete the existing Code42 app by signing in to your Microsoft Teams client and removing the app before re-installing. See Microsoft support for detailed instructions.

Slack

Before you can send messages from Incydr to users via Slack, you must authorize Code42's connection to your Slack workspace.

Connect to Slack

  1. Use either a web browser or the Slack desktop app to verify that you are signed in to your organization's Slack workspace.
  2. Sign in to the Code42 console.
  3. Go to Administration > Integrations > Message Services.
  4. On the Slack panel, click Authorize.
    In the same tab, Incydr requests access to your organization's Slack workspace, and lists the request and permissions needed for the connection.
  5. Approve the Code42 third-party connection via the steps specific to your role and permissions in Slack:
    • If you are a Workspace Owner or app manager in your Slack workspace, click Allow to approve the Code42 third-party service connection.
      You are returned to Incydr and Code42's connection to Slack is activated.
    • If you are not a Slack Workspace Owner or app manager, do the following:
      1. Click Submit to send a request to your organization's Slack Workspace Owner or app managers to approve the Code42 third-party connection.
      2. Work with your organization's Slack Workspace Owner or app managers to approve the Code42 request and grant permission to allow the Code42 third-party service connection to Slack.
      3. Return to Incydr and click Authorize on the Slack panel in Message Services again.
      4. When the Slack request and required permissions open in the same tab, click Allow to approve the connection.
        You are returned to Incydr and Code42's connection to Slack is activated.

To deliver Code42 Instructor lessons to users in response to risky activity, set up actions settings in alert rules.

Disconnect from Slack

To disconnect an active Slack connection, click Deauthorize. When the prompt appears notifying you that Code42 Instructor lessons will no longer be sent to users as Slack messages, click Got it, deauthorize.

When you deauthorize the connection to Slack, Code42 automatically uninstalls its application from your Slack workspace to remove the connection. If this attempt is unsuccessful (for example, if you or your Slack Workspace Owner have already removed the Code42 application), the connection is still deauthorized.

Deauthorization can fail due to network issues that interfere with communication to your Slack workspace. If deauthorization fails, try again later or contact your Slack Workspace Owner.

Troubleshoot connection errors

The Code42 connection to Slack can fail for the following reasons:

  • Code42's third-party service connection to Slack was not activated and its authorization has timed out
  • Network issues are occurring that interfere with communication to your Slack workspace

If Code42 fails to establish a connection to Slack or cannot deliver Code42 Instructor messages to users in Slack messages, try again later or contact your Slack Workspace Owner.

External resources

Slack documentation: