View this page in the latest version of Appian. Email Share Share via LinkedIn Reddit Email Copy Link Print On This Page Purpose The Email page in the Admin Console allows you to manage email settings for the environment. Access To access the Email page, go to the Admin Console. Then, in the left navigation menu, under Integration, click Email. Settings The Email page contains the following settings. Outbound Email Toggle The Outbound Email Toggle tab allows you to enable or disable the ability for Appian to send email. Many features are unavailable when outbound email is turned off including: Automatic email alerts for the following: Autoscaled process errors Portal errors Record type sync failures Site errors Multi-factor authentication Send Email smart service User email notifications for tasks and news Process KPIs in Process HQ Email Sender Authentication The Email Sender Authentication tab allows you to authenticate email sending domains using DomainKeys Identified Mail (DKIM). DKIM is a standard email authentication method that adds a digital signature to outgoing messages. Receiving mail servers that receive messages signed with DKIM can verify messages actually came from the intended sender, and not another party impersonating the sender. To authenticate an email sending domain using DKIM: In the Administration Console, under INTEGRATION, select Email. Go to the Email Sender Authentication tab. Click New Sender Domain Authentication. For Sender Domain, enter the email domain to authenticate, such as example.com, then click Authenticate. To complete sender domain verification, create the DNS record for the domain using the DKIM DNS record that displays. Note: If you use a DKIM/DMARC verification/reporting tool (i.e. Valimail) that requires or recommends DNS delegation for your DKIM records, you will need to first create and verify the TXT record generated in the Appian Admin console directly in your DNS zone before delegating the record. If the DNS record isn't ready to be verified, click VERIFY LATER. You can verify the DNS record at a later time by going back to the Email Sender Authentication tab and clicking the Domain name. After the DNS record has been created, verify the created record by clicking VERIFY NOW. If verification is successful, the verification status of the domain will be updated and emails sent from the authenticated domain will be signed. Note: If you are an Appian Cloud customer and have DNS VPN enabled for your Appian Cloud environment, and your DKIM DNS Record Name includes a domain name that is configured to go over the VPN tunnel, then you must either set up your DNS server configurations such that DNS resolution for the DKIM DNS Record Name resolves to the correct public IP address, or work with Appian Support to exempt the DKIM DNS Record Name from going over the VPN tunnel. Process Error Alert Email Settings The Process Error Alert Email Settings tab lets you choose how recipients are added to the emails sent to process administrators. By default, process alert emails are sent with the recipients in the Bcc field. This protects users' information from being seen by the other recipients. If you need alert recipients to see each other, you can choose to use the To field instead. All recipients will be visible to each other when this option is selected. To update the alert email setting to use the To field: Go to the Email section in the Admin Console. Click the Process Error Alert Email Settings tab. Select Send process alerts with recipients in the To field. On the confirmation dialog, click Confirm. Click SAVE CHANGES. Client Certificates You can select the client certificates that your Appian environment uses to securely connect to the mail servers you've configured to handle email for the environment. To select client certificates to use with your mail server(s): Upload the client certificates for the mail server(s) you want to use. Go to the Email section in the Admin Console. Click the Client Certificates tab. Scroll or drag to pan · ⌘+/⌘− to zoom · Esc to close Tip: The certificate name in the Client Certificates dropdown lists displays in the format: Subject (Thumbprint). For Outbound SMTP Server, select a client certificate for Appian to use when sending email messages. For Email Pollers, select a client certificate for each mail server your Appian environment has been configured to poll. Click SAVE. Appian automatically starts using the selected certificate(s); no restart is required. OAuth 2.0 The OAuth 2.0 tab in the Email page of the Admin Console allows you to configure OAuth 2.0 Client Credentials Grant authentication for outbound email sending and inbound email polling. OAuth 2.0 authentication is an alternative to username and password authentication for mail servers that require modern authentication, such as Microsoft Exchange Online and Microsoft 365. Note: Microsoft is disabling username and password authentication for Microsoft Exchange Online by default at the end of December 2026. Administrators using Microsoft 365 mailboxes must configure OAuth 2.0 to keep email working after that date. OAuth 2.0 email authentication has the following limitations: Supported providers: Microsoft Exchange Online and Microsoft 365 only. Google Workspace is not supported. Supported grant type: Client Credentials Grant only. Outbound SMTP: A single OAuth 2.0-authenticated SMTP server. Existing SMTP configuration is unaffected. Inbound polling: Multiple OAuth 2.0-authenticated pollers, each configured independently. OAuth 2.0 is disabled by default. When OAuth 2.0 is disabled, Appian uses username and password authentication. Your existing username and password configuration is preserved and unaffected when OAuth 2.0 is enabled. For self-managed environments, no restart is required to enable, disable, or change OAuth 2.0 settings. Tip: If you disable OAuth 2.0 after enabling it, Appian automatically falls back to username and password authentication. To set up OAuth 2.0 email authentication: Complete the prerequisites for OAuth 2.0 email authentication. Enable the OAuth 2.0 option. Configure the outbound SMTP server to send email using OAuth 2.0. Configure inbound email pollers for each mailbox Appian polls using OAuth 2.0. Prerequisites for OAuth 2.0 email authentication Before configuring OAuth 2.0 email authentication in Appian, you must have an app registration in the Microsoft Entra admin center with the appropriate mail permissions. See Microsoft's documentation to create and configure one. Collect the following values from your app registration before you begin: Client ID: The application (client) ID. Client Secret: The client secret value. Token URL: The OAuth 2.0 token endpoint (for example, https://login.microsoftonline.com/<TENANT_ID>/oauth2/v2.0/token). OAuth Scope: The permissions the access token grants for accessing the mail server (for example, https://outlook.office365.com/.default). Enable OAuth 2.0 email authentication To enable OAuth 2.0 authentication for email: In the Admin Console, under INTEGRATION, select Email. Go to the OAuth 2.0 tab. Select Enable OAuth 2.0 authentication for email. Click SAVE CHANGES. You can now add outbound SMTP and inbound poller configurations. OAuth 2.0 becomes active for connections that have a configuration. Connections without a configuration continue to use username and password authentication. Configure the OAuth 2.0 outbound SMTP server The Outbound SMTP Server section of the OAuth 2.0 tab lets you configure the credentials Appian uses to send email through your Microsoft Exchange Online SMTP server. Only one outbound OAuth 2.0 SMTP server configuration is supported per Appian environment. To add an outbound SMTP server configuration: In the Admin Console, under INTEGRATION, select Email. Go to the OAuth 2.0 tab. In the Outbound SMTP Server section, click + ADD CONFIGURATION. Enter the following fields: Field Description Name A unique name to identify this configuration. Client ID The application (client) ID from your Microsoft Entra app registration. Client Secret The client secret value from your Microsoft Entra app registration. Appian encrypts this value and never writes it to disk or logs. Token URL The OAuth 2.0 token endpoint for your Microsoft Entra ID tenant (for example, https://login.microsoftonline.com/<TENANT_ID>/oauth2/v2.0/token). OAuth Scope The permissions the access token grants for accessing the mail server. The scope is specific to your identity provider (for example, https://outlook.office365.com/.default). Grant Type The OAuth grant type. The default is "Client Credentials". Server The hostname of your Exchange SMTP server (for example, smtp.office365.com). Port The SMTP port number. The default is 587. If your mail server uses a different port, change this value. Email Address The mailbox used to authenticate and send email. The From address of all outbound emails must match this address exactly. Click CREATE. Note: Microsoft Exchange Online enforces sender authorization. If the From address of an outbound email does not match the Email Address configured here, Microsoft Exchange Online rejects the message. All outbound emails—including those sent by the Send Email smart service and processes using custom email senders—must use the OAuth-authorized sender address. Configure OAuth 2.0 inbound email pollers The Inbound Email Poller section of the OAuth 2.0 tab lets you configure OAuth 2.0 credentials for each mailbox Appian polls for incoming email. Each poller configuration is independent; some pollers can use OAuth 2.0 while others continue to use username and password authentication. In self-managed environments, you can add, edit, or remove poller configurations without restarting the environment. Changes apply immediately on the node handling the update. If your self-managed environment is configured to use multiple nodes, all other nodes pick up the change from the primary node within 5 minutes. For each mailbox to poll using OAuth 2.0: In the Admin Console, under INTEGRATION, select Email. Go to the OAuth 2.0 tab. In the Inbound Email Poller section, click + ADD CONFIGURATION. Enter the following fields: Field Description Name A unique name to identify this poller configuration. Client ID The application (client) ID from your Microsoft Entra app registration. Client Secret The client secret value from your Microsoft Entra app registration. Appian encrypts this value and never writes it to disk or logs. Token URL The OAuth 2.0 token endpoint for your Microsoft Entra ID tenant (for example, https://login.microsoftonline.com/<TENANT_ID>/oauth2/v2.0/token). OAuth Scope The permissions the access token grants for accessing the mail server. The scope is specific to your identity provider (for example, https://outlook.office365.com/.default). Grant Type The OAuth grant type. The default is "Client Credentials". Server The hostname of your IMAP or POP3 mail server (for example, outlook.office365.com). Port The mail server port number. The default is 993. If your mail server uses a different port, change this value. Email Address The email address of the mailbox Appian polls. Store Protocol The protocol Appian uses to connect to the mail server and retrieve messages. Valid values: "IMAP" or "POP3". Use IMAP unless your mail server requires POP3. Click SAVE. Note: Other inbound polling settings, such as polling interval, mail folder, and partial fetch behavior, are configured in the Appian CR configuration file. OAuth 2.0 poller configurations in the Admin Console control authentication only. After saving your OAuth 2.0 configuration, verify the connection is working by following the steps in Test the email service. Feedback Was this page helpful? SHARE FEEDBACK Loading...