Recipient method reference
The tables below list the fields on the Create Recipient page and the requirements of each delivery method.
Common fields
| Field | Required | Description |
|---|
| Name | Yes | The recipient name. Accepts only letters, numbers, underscores (_), hyphens (-), spaces, and dots (.) |
| Method | Yes | Email, Slack, Teams, or Telegram |
| Level | Yes | VPC (default) or Project. See the Level table below |
By method
| Method | Field to fill | Verification |
|---|
| Email | Address | None |
| Slack | Slack channel | Sign in to the Slack workspace through the Sign in to your workplace link before selecting a channel |
| Teams | Webhook URL | Click Send test message to check the webhook. Create the webhook with Microsoft Teams Workflows |
| Telegram | Telegram ID | Get the chat ID through the Get Telegram chat ID link, then click Send verification link. For a group, add the FPT Cloud Guard bot to the group |
Level
| Level | Can be used for |
|---|
VPC | Every alert type in the VPC where the recipient was created, except Object Storage alerts |
Project | Object Storage alerts only, in every VPC of the Project |
Anyone with permission to create or edit an alert can select any valid recipient in Notify to, regardless of who created the recipient.
See also