Archer Notifications in Microsoft Teams

Bring Archer notifications into the flow of work

Stay informed. Act faster. Without leaving Teams.

 Risk and compliance work doesn’t always happen inside Archer alone; it happens where teams collaborate every day. With Archer Notifications in Microsoft Teams, your organization can receive important Archer updates directly in Teams, alongside the conversations and tools your teams already use.

This integration ensures critical notifications are seen sooner, acted on faster, and never lost in crowded inboxes while email continues to serve as a reliable backup.

Why Teams notifications matter

With Teams notifications enabled, users benefit from:

• Real‑time visibility into important Archer events, right in Teams
• Faster response times, as notifications appear where work is already happening
• Reduced email overload, without removing email as a trusted channel
• Consistent messaging, with the same content delivered across email and Teams

This approach ensures that important Archer updates never get missed, whether users are checking email or working inside Teams.

What does this include?

Once enabled, Archer notifications are delivered through the ArcherGRC app in Microsoft Teams, which appears in the Teams app rail alongside other frequently used apps.

Key capabilities include:

Consistent formatting with email

• MS Teams notifications mirror the email content users already receive
• Subject lines, message body, headers, footers, and links remain unchanged
• Common formatting such as bold and italic text is preserved

There’s nothing new to configure for users, notifications simply appear in another place they already work.

Notification‑only experience

• The ArcherGRC app is designed to inform, not to take action
• Users cannot reply to messages or perform actions directly from MS Teams
• Any follow‑up actions continue to happen in Archer, just as they do today

Support for multiple Archer instances

• Multiple Archer instances (production and non‑production) can connect to the same Microsoft Teams tenant
• Each instance can be connected or disconnected independently by its Archer administrator
• Notifications clearly indicate which instance they are coming from, helping users avoid confusion between environments

Broad notification coverage

• All Archer notifications are supported except “Action by Email” notifications that contain interactive buttons (such as Approve or Reject)

Easy disconnect when needed

• Archer administrators can disconnect Teams integration at any time from the Global Notifications page
• Once disconnected, Teams notifications stop immediately for that instance

How to enable Archer notifications in Microsoft Teams

Enabling Teams notifications is a simple, three‑step process involving Archer support representative, Microsoft Teams Admin, and Archer Admin.

Step 1: Contact Archer Support 

To enable, please open a case with Archer Support via the Portal on the Archer Community. In the Subject & Description fields, request to enable the ‘Notification in Teams’ feature and choose ‘SaaS Requests’ as the Affected Area Category. Upon confirmation the feature has been enabled, follow the process listed below to configure.

Step 2: Get the ArcherGRC app installed in your Microsoft Teams environment

Before users can receive notifications:

• The ArcherGRC app must be pre installed by your organization’s Microsoft Teams Admin
• We recommend pre‑installing the app for users, so notifications begin automatically once the connection is established
• This can be done from the Microsoft Teams Admin Center by adding ArcherGRC to installed apps and applying the appropriate permissions

Step 3: Configuration by the Archer Administrator

Once the Teams app is installed:

• An Archer Admin enables the integration from the Admin Panel → Notifications → Global Notifications
• A new Connect button appears under Microsoft Teams notification settings
• The admin enters the organization’s Microsoft Tenant ID (available from your Microsoft Admin) and selects Connect
• After a successful connection, the button changes to Disconnect, confirming that Teams integration is active

Note: In case of ArcherGRC app being approved to be used (not pre installed) by your MS Teams admin, each user will need to search for this app in MS Teams and add it before they can receive Teams notifications.



Once configured, the user who receives email notifications from that Archer instance will also start receiving the same notifications in Microsoft Teams.

Important considerations

To set the right expectations, please note the following behaviors:

• This feature is available only for Archer SaaS customers 
• Notifications are delivered as 1:1 message to individual users 
  • Posting to Teams channels is not supported
  • Distribution lists and Archer groups are not supported
• Microsoft Teams notifications depend on email notifications 
  • Email notifications must remain enabled
• Each user must have: 
  • A valid email address in Archer
  • A Microsoft Teams account using the same email address
• MS Teams notifications can be enabled only at the instance level. Individual notification level configuration is not supported. Once enabled, all notifications generated from that instance will be delivered through MS Teams.

If these conditions are met, Teams notifications will be delivered automatically.

Also available: Archer notifications in Slack

If your organization prefers Slack for day‑to‑day collaboration, Archer offers a similar notification integration with Slack as well.

This allows users to receive Archer notifications directly in Slack, following the same philosophy:

• Timely visibility
• Consistent messaging
• Reduced reliance on Email alone

Learn more about Archer Notifications in Slack here to choose the collaboration experience that best fits your teams.