> For the complete documentation index, see [llms.txt](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/9.-settings/9.7-campaign-management/9.7.3-email-campaign/sendgrid-account-list.md).
# Sendgrid account list
## Interface of Sengrid account list
* **Display name:** system display name
* **Sendgrid email address:** Sendgrid email address
* **Account status:**
* **Active:** email is in active state
* **Inactive:** email in inactive state
* **Action:**
* **Edit:** edit existing Sendgrid account
* **Delete:** delete Sendgrid account
## Add a new Sengrid email account
Email campaigns are sent from Sendgrid email or SMTP. With Sendgrid email, admin needs to add a Sendgrid account according to the following instructions:
* **Step 1:** Access the SendGrid Account Management screen, click the "Add New Account" button
* **Step 2:** Enter all information in the Add SendGrid account screen and click “Create New”. The information to enter includes as shown:
* **SendGrid email address:** The email address registered with the Sendgrid account
* **Display name:** The name displayed on the SendGrid Account Management screen for easy lookup when needed
* **API key:** Admin enter the generated API key here. Create API key according to instructions at link ;
* **Public key:** Access your SendGrid account, select Signed Event Webhook Requests > Verification Key. Copy the “Verification Key” and paste it in the Public key field.
* **Domain authentication:** Leave as default
* **Status:** If enabled, the email status will be displayed: successfully sent, opened mail, .. (Only applicable to SendGrid). If off, show only successful or failed submission
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.stringeex.com/stringeex-tong-dai-cham-soc-and-quan-ly-khach-hang/en/ii.-system-features/9.-settings/9.7-campaign-management/9.7.3-email-campaign/sendgrid-account-list.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.