---
title: "How to manage notifications"
slug: "notification-how-to-manage-notifications"
updated: 2026-11-03T14:48:26Z
published: 2026-11-03T14:48:26Z
canonical: "docs.senhasegura.io/notification-how-to-manage-notifications"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How to manage notifications

This document provides information on how to manage notifications. **Segura™ Platform** allows you to configure global notifications about each product to receive notifications on the screen, via email, Microsoft Teams or Slack.

## Requirements

- To use the SMS notification sending option, it's necessary to have the Zenvia integration properly configured. SMS notifications won’t be sent without this configuration. More information on how to configure the Zenvia integration in [How to integrate an SMS service](/v4-2/docs/integration-with-sms-service).
- For email notifications, ensure that a default email is correctly configured.

## Add a new notification

1. On **Segura™ Platform**, in the navigation bar, hover over the **Products menu** and select **Settings**.
2. In the side menu, select **Notifications > Global notifications**.
3. In the **Global notifications** report, click **Add**.
4. In the **General** tab, complete the following fields:
  1. **Notification name ***: enter a name for the notification.
  2. **E-Mail**: enable to send notifications through e-mails.
  3. **Screen**: enable to send notifications through the screen.
  4. **SMS**: enable to send notifications through SMS.
  5. **Microsoft Teams**: enable to send notifications through Microsoft Teams.
  6. **Slack**: enable to send notifications through Slack.
  7. **Send notifications only to contacts who have access to credentials or devices:** enable to only send notifications to the contacts who have access to credentials or devices.
5. Click **Continue**.
6. Optional: In the **Notification** tab, click **+ Add** to enter what kind of notifications you want to send.
7. Click **Continue**.
8. Optional: In the **Contacts** tab, click **+ Add** to enter the contacts to receive the notifications.
  1. For notifications sent via Slack, the contact's email address must match the email associated with their respective Slack account to ensure successful delivery.
9. In the **Review** tab, review all information entered previously and click **Save**.

## Edit a notification

1. On **Segura™ Platform**, in the navigation bar, hover over the **Products menu** and select **Settings**.
2. In the side menu, select **Notifications > Global notifications**.
3. In the **Global notifications** report, find the notification you want to edit and click **Edit**.
4. Make the necessary changes and save.

## Deactivate a notification

1. On **Segura™ Platform**, in the navigation bar, hover over the **Products menu** and select **Settings**.
2. On the side menu, select **Notifications > Global notifications**.
3. In the **Global notifications** report, find the notification you want to deactivate and click **Disable**.
4. In the confirmation modal, click **Yes**.

## Reactivate a notification

1. On **Segura™ Platform**, in the navigation bar, hover over the **Products menu** and select **Settings**.
2. On the side menu, select **Notifications > Global notifications**.
3. In the **Global notifications** report, select the **No** option in the **Enabled** filter and click **Filter**.
4. Find the notification you want to reactivate and click **Enable**.
5. In the confirmation modal, click **Yes**.

## Customize a notification

Some of the texts in the notification templates used by **Segura™ Platform** can be modified according to your needs. To customize your notifications, see the following steps:

1. On **Segura™ Platform**, in the navigation bar, hover over the **Products menu** and select **Settings**.
2. In the side menu, select **Notifications > Text customization**.
3. In the **Notification text** report, find the notification you want to customize.
4. In the **Action** column, click **Edit**.
5. In the **Notification text** form, complete the following fields:
  1. **Text type ***: select the notification type to be changed.
  2. **Active**: select if you want to enable the text customization. By default, it's marked as **Yes**.
  3. **Subject ***: expression for the subject of the email that will be sent in the notification.
  4. **Message text ***: rich text editor that allows editing of the default text of the email notification. This text should contain the email tags.
  5. Click **Save**.

### TAGs

An essential portion for creating custom email notification texts are the TAGs. They serve as placeholders for certain information about the user who will receive the report or notification. The TAGs used in **Segura™ Platform** are:

- `[#REQUEST_CODE#]`: request code in `S000000 format`.
- `[#REQUEST_STATUS#]`: request status.
- `[#REQUESTER#]`: user who is requesting access to password.
- `[#REQUEST_DATE#]`: date of request.
- `[#APPROVER#]`: name of the approver who will receive the request email.
- `[#ANSWERED_BY#]`: name of the approver who responded to the request.
- `[#ANSWER_DATE#]`: date when the request was answered by the approver.
- `[#ACTION#]`: requested action.
- `[#ACTION_LIST#]`: action requested on list format.
- `[#ACTION_LIST_SYSLOG#]`: action requested on list format using `syslog` template.
- `[#URL_APPROVE#]`: URL to approve access to password.
- `[#LINK_APPROVE#]`: link to approve access to password.
- `[#URL_REJECT#]`: URL to reject access to password.
- `[#LINK_REJECT#]`: link to reject access to password.
- `[#DEVICE_HOSTNAME#]`: device hostname.
- `[#DEVICE_IP#]`: device IP.
- `[#CREDENTIAL_USERNAME#]`: credential username.
- `[#CREDENTIAL_TYPE#]`: credential type.
- `[#REASON#]`: specified reason.
- `[#JUSTIFICATION#]`: reason specified by requester.
- `[#GOVERNANCE_ID#]`: governance ID.
- `[#START_DATETIME#]`: start date and time of requested access period in `MM/DD/YYYY hh:mm:ss` format.
- `[#END_DATETIME#]`: end date and time of requested access period in `MM/DD/YYYY hh:mm:ss` format.
- `[#START_DATETIME_STR#]`: start date and time of requested access period in `Tuesday, August 27 03:14 PM` format.
- `[#END_DATETIME_STR#]`: end date and time of requested access period in `Tuesday, August 27 03:14 PM` format.
- `[#START_DATE#]`: start date of requested access period in `MM/DD/YY` format.
- `[#END_DATE#]`: end date of requested access period in `MM/DD/YY` format.
- `[#START_TIME#]`: start time of requested access period in `h:mm` format.
- `[#END_TIME#]`: end time of requested access period in `h:mm` format.
- `[#CREDENTIAL#]`: credential involved in the request.
- `[#RESPONSIBLE#]`: name of certificate responsible.
- `[#CERT_ENVIRONMENTS#]`: certificate environments separated by comma.
- `[#CERT_SYSTEMS#]`: certificate systems separated by comma.
- `[#CERT_TAGS#]`: certificate tags separated by comma.
- `[#CERT_DESC#]`: certificate description.
- `[#COMMONNAME#]`: certificate common name.
- `[#ISSUED_BY#]`: certificate issuer information.
- `[#VALIDITY_INIT#]`: certificate validity start date.
- `[#VALIDITY_END#]`: certification expiration date.