MC Environment Popular tab

<< Click to Display Table of Contents >>

Navigation:  Automation Server > Automation Server configuration and administration guide > System maintenance and monitoring > Environment settings and administration > Management Console > Environment options in Mangement Console >

MC Environment Popular tab

Popular tab

From this option you can configure the parameters for sending email for each environment (Development, Test, Production).




The parameters to be configured are:




Notifications options

Enable Email

Allows Bizagi to send emails, or prevents it. Select this option to permit sending e-mails. If it is not selected, emails will be ignored.

SMTP Server

Defines the name of the SMTP server. The SMTP can be local (localhost) for specific testing purposes in the Development environment.

For Testing and Production environments the server must be the company's server from where e-mails are sent.

SMTP Server Account

Defines the SMTP account (or address) used to send e-mails. It must be a valid e-mail address on the SMTP server.

If the local server (localhost) is used, the e-mail address may be a non-valid one. If a real SMTP server is used, the address must belong to the domain.

Send Email Copy to

Defines an e-mail account to which a copy of all mails sent by the application will be sent

Send Email BCC to

Defines an e-mail account to which a BLIND copy of all mails sent by the application will be sent



The Bizagi cloud offering includes the SMTP service. Therefore, Bizagi includes the SMPT server configuration when provisioning your Automation Service's environments. These parameters cannot be changed through deployment. Any request related to the SMTP configuration or parameters must be done with a support ticket.




Email integration

Enable lookup email

Enables the possibility to retrieve emails from the configured account and Complete tasks via email, without entering the Work Portal.

Connection type

Depending of your company's requirements the available options are Exchange, POP3 and IMAP.

Enable SSL

Defines whether Bizagi uses SSL to connect to your server. We recommend that you enforce use of SSL.

This option depends on your Mail Server configuration, and it is available when the connection type is POP3 or IMAP.


Exchange connections already enforce the use of HTTPS.


Defines the connection port to your Mail Server. This option is available when the connection type is POP3 or IMAP.


Defines the account that will receive email replies sent by end users.

Mailbox Service / Host

When Exchange is selected the Mailbox service receives the Exchange Web Service URL, which is an .asmx URL. The default URL for this service is https://[MailServer]/EWS/Exchange.asmx. Click here for more information about EWS and how to manage it,

When POP3 or IMAP are enabled, defines the server's name or IP of your Mail Server


Defines a valid user name within your mail server to perform the connection.


The account password.







Enable legacy web services (asmx)

This option grants access to Bizagi legacy services (asmx). For more information, refer to Web Service Security.

Enable WS-Security

This options grants access to Bizagi secure services (svc). For more information, refer to Web Service Security.


The user name token used for signing.

For authentication purposes of the web services, you must define a user name token (as specified by the WS-Security standard).


Define a password for the above user name token.

X509 Find Value

The common name of the installed X.509 certificate.

X509 Store Location

The location of the store where the X.509 certificate is installed.

You may use the MMC snap-in to verify such information (

X509 Store Name

The name of the store where the X.509 certificate is installed.

You may use the MMC snap-in to verify such information (

X509 Find Type

The value which filters how to use the Find Value parameter.

For the common name, use FindBySubjectName.

X509 Validation Mode

Choose from the valid options:

ChainTrust: This one validates the certificate using the certification authority. In .NET scenarios, it may be more reliable to use this option.

PeerTrust: This one is validated by the server by checking its trusted store (recommended). PeerTrust implies that the incoming certificate has to be in the Trusted People certificate folder.

PeerOrChainTrust: Any of the previous one.

None: Trust any certificate (not recommended).




SMS configuration

Default country code

This code will be used if a user's phone number doesn't have one.

Code validity period

The time in minutes in which the sent code will be valid.

Number of codes allowed

The number of times a user can request a code. Bizagi will not send any more codes if the number of requests reaches this number. Codes can be requested again when the time-out to between requests expires.

Time-out between code requests

The time in minutes that Bizagi will wait before sending new codes after reaching the maximum number of codes allowed.


Your SMS provider. Currently, our supported provider is Twilio.

Account SID

The security identifier that acts as a username.

Auth token

The security identifier that acts as a password.

From numbers

The numbers used to send the code according to the end user's location. The default number is used when there is no match for the user's country code.




We recommend using an exclusive account to retrieve incoming messages for email integration. Bizagi will read all incoming messages and will mark them as read.


For traces and troubleshooting, errors are recorded in the Window's Event viewer.