Once an identity is created, click the Configuration button on the identity card to access its full settings. The configuration panel is organized into the following sections:
Contact Details
LinkedIn
Email
Likings opt-out
Share Identity Link
Contact Details
If you connected a LinkedIn account when creating the identity, this section is automatically populated with the LinkedIn profile data — including your name, profile picture, job title, and LinkedIn URL. If you created the identity manually, it reflects the information you entered. All fields can be edited at any time.
Editable fields
Profile Picture
First Name
Last Name
Job Title
LinkedIn URL
Email
Schedule Meeting URL
Phone Number
Working Hours
From the Contact Details section you can configure Working Hours for the identity. This setting defines the time zone, days, and hours during which the identity is active. Campaigns associated with this identity will only execute actions during the specified working hours.
For example, if you set working hours to Monday–Friday, 9:00–18:00 CET, the identity will not send any messages outside of that window.
LinkedIn Settings
The LinkedIn configuration section contains two tabs: Rate Limits and Withdrawals.
Note: The Daily scrapings setting is only available if the identity has Sales Navigator enabled.
Rate Limits
Define the daily activity limits for the identity on LinkedIn:
Warning: Increasing daily connection requests or message limits beyond the recommended defaults can trigger LinkedIn automation detection, which may result in temporary account restrictions. If you do increase them, do so temporarily and monitor closely.
Setting | Default | Description |
Daily connection requests | 20 per day | The maximum number of connection requests the identity can send per day. Increasing this value carries the risk of LinkedIn detecting automation and temporarily restricting your account. |
Daily messages limit | 100 per day | The maximum number of LinkedIn messages the identity can send per day. Significant increases are not recommended. |
Daily scrapings | Varies | Only available for identities with LinkedIn Sales Navigator. This value represents the number of additional scrapings the identity can perform beyond the shared account pool. The total scraping capacity equals the Enginy pool allocation plus the identity's Sales Navigator capacity. |
Withdrawals
Withdrawing old pending invitations helps keep your LinkedIn account healthy and avoids hitting LinkedIn's pending invitation limits. Manage pending LinkedIn connection requests that have not been accepted:
Important: After withdrawing a connection request, you cannot send a new request to the same person for 3 weeks.
Automatic withdrawal — Enable the option "Automatically withdraw pending invitations" and set a threshold in days (e.g., 7 days). Connection requests pending longer than this period will be automatically withdrawn.
Manual withdrawal — Select and withdraw pending requests in bulk from the Withdrawals tab.
History — View the full history of withdrawn connections.
Email Configuration
The Email configuration section contains three tabs: Manage, Email Rate, and Signature.
Manage Email Addresses
Connect one or multiple email addresses to the identity. Supported providers include Google, Microsoft, and IMAP.
Connect a Google Email Account
Connect a Google Email Account
To connect a Google account to Enginy, sign in with the Google account you want to use.
Before you continue, you can review Enginy's Privacy Policy and Terms of Service using the links provided.
Connect a Microsoft 365 / Azure Email Account
Connect a Microsoft 365 / Azure Email Account
This section explains how to connect a Microsoft 365 (Outlook) email account to Enginy. The integration uses the industry-standard OAuth 2.0 authentication protocol to ensure secure access without storing your password.
For Users: "Approval Required" Screen
If you attempt to connect your email and see a screen stating "Approval required" after logging in, follow these steps:
Enter a brief justification in the text box (e.g., "Required for CRM integration").
Click the Request approval button.
This sends a notification to your IT administrator so they can review and approve the request.
For IT Administrators: Grant Permissions
To allow users to connect their Microsoft 365 email accounts, an Azure Administrator must adjust the tenant configuration in the Microsoft Entra Admin Center (formerly Azure AD). Choose one of the following solutions.
Solution A: Grant Tenant-Wide Admin Consent (Recommended)
This method explicitly authorizes the Enginy application for your entire organization.
Navigate to Microsoft Entra Admin Center > Enterprise applications.
Search for and select the Enginy AI application.
In the left menu, select API permissions.
If you see warnings such as "Admin consent required," click the button labeled Grant admin consent for [Organization Name].
Solution B: Modify User Consent Settings
If you prefer to allow users to authorize applications themselves:
Navigate to Microsoft Entra Admin Center > Applications > Enterprise applications > Consent and permissions > User consent settings.
Ensure that "Allow user consent for apps from verified publishers" is selected.
Note: Enginy AI is a verified publisher.
Troubleshoot a Failing Connection
If the integration fails despite granting consent, check for Conditional Access Policies that may be blocking third-party applications:
Go to Microsoft Entra Admin Center > Protection > Conditional Access > Policies.
Check for policies affecting "All cloud apps."
Look for blocks related to legacy authentication, non-compliant devices, or untrusted locations.
Exclude the Enginy application from restrictive policies, or create a specific exception.
Symptom | Likely Cause | Resolution |
"Approval required" screen appears when connecting | Organization requires admin consent for third-party apps | Request approval from your IT administrator, or have the admin grant tenant-wide consent (Solution A above) |
Connection fails after admin consent was granted | Conditional Access Policies blocking third-party applications | Review and exclude Enginy from restrictive Conditional Access Policies |
Permissions granted but connection still does not work | Permission propagation delay in Azure | Use the Admin Browser workaround described below, or wait and retry after a few minutes |
Alternative: Connect via Admin Browser
Note: This is a workaround for situations where permission propagation is delayed.
If the standard procedures above do not resolve the issue, the Azure Administrator can attempt to connect the email integration directly:
Open the browser where the Azure Administrator is already logged in with their Azure Admin permissions.
Log in to the Enginy platform on that same browser (using a member account).
Navigate to the email integration settings and attempt to connect the email account.
Because the browser session already holds valid Azure Admin credentials, this action often bypasses user-level restrictions and forces the initial connection.
Required Permissions (Scopes)
For your security review, the Enginy integration requests the following Microsoft Graph permissions:
Permission | Purpose |
| Send emails via SMTP |
| Send emails via Microsoft Graph |
| Read and write access to mailbox messages |
| Read basic mail properties |
| Read mailbox messages |
| Read the signed-in user's profile |
| Maintain access without re-authentication |
References
Configure how users consent to applications — Microsoft Learn
Grant tenant-wide admin consent — Microsoft Learn
Conditional Access: Targeting Resources — Microsoft Learn
Overview of permissions and consent — Microsoft Learn
Connect an Email Account via IMAP in Enginy
Connect an Email Account via IMAP in Enginy
Connecting an inbox via IMAP lets Enginy access your mailbox to sync and read incoming emails (e.g., for conversation tracking). To send emails, Enginy uses SMTP. That’s why the setup requires both IMAP (incoming) and SMTP (outgoing) details.
Before you start
Make sure you have:
The email address you want to connect
The password (or an App Password if your provider requires it)
Your provider’s server details:
IMAP Host and IMAP Port
SMTP Host and SMTP Port
Tip: For many providers (Google, Microsoft, etc.), you may need to enable IMAP/SMTP access or generate an App Password, especially if 2FA is enabled.
How to connect
Fill in the fields:
Email: the inbox address you want to connect
Password: your password or App Password
IMAP Host: your provider’s IMAP server
IMAP Port: the IMAP port
SMTP Host: your provider’s SMTP server
SMTP Port: the SMTP port
Click Connect.
Enginy will validate the connection and, if everything is correct, the inbox will be ready to use.
Common ports (quick reference)
These are the most common secure options (they can vary by provider):
IMAP
993 (SSL/TLS) ✅ recommended
143 (non-SSL / STARTTLS depending on provider)
SMTP
465 (SSL)
587 (STARTTLS) ✅ very common/recommended
Best practices
Use TLS/SSL ports whenever possible (IMAP 993, SMTP 465/587).
If your account has 2FA, your normal password often won’t work—use an App Password.
If this inbox is used for campaigns, consider connecting a dedicated sending inbox.
Troubleshooting
Symptom | Likely Cause | Resolution |
Connection fails with “Authentication failed” / “Invalid credentials” | Wrong password, or 2FA is enabled and the provider requires an App Password | Double-check the email/password. If 2FA is enabled, generate an App Password and use it instead of your normal password. |
“Cannot connect” / timeout error | IMAP/SMTP host or port is incorrect, or network/firewall is blocking the connection | Verify the IMAP/SMTP host and port. Try secure defaults: IMAP 993 (SSL) and SMTP 587 (STARTTLS) or 465 (SSL). Check firewall/VPN restrictions. |
IMAP connects, but sending emails fails | SMTP settings are incorrect or SMTP is blocked by the provider | Verify SMTP Host/Port and whether the provider requires SSL/STARTTLS. Make sure SMTP is enabled for the mailbox in the provider settings. |
Connection succeeds, but no emails appear / no sync | IMAP access is disabled on the mailbox, or the provider limits IMAP | Enable IMAP access in the provider/admin settings. If the provider restricts IMAP, use another connection method (OAuth, if available). |
Connection fails after changing the mailbox password | Stored credentials are no longer valid | Reconnect the inbox with the updated password (or new App Password). |
“Too many login attempts” / temporary lock | Provider rate limits or security policies triggered | Wait and try again later. Reduce repeated attempts. If available, whitelist the login location/IP or review provider security alerts. |
Works for some mailboxes but not for others | Provider/admin policies differ per user (security rules, IMAP disabled, restricted apps) | Compare mailbox settings and policies. Ask your IT/admin to enable IMAP/SMTP or allow third-party access for that user. |
Connection fails only on corporate domains (e.g., Microsoft/Google Workspace) | Admin policies require approval for third-party access or block basic auth | Ask the admin to allow IMAP/SMTP access (or provide an App Password). If basic auth is blocked, use the provider’s recommended secure method where possible. |
Emails send, but deliverability is poor (spam/bounces) | Domain reputation issues, missing SPF/DKIM/DMARC, or aggressive sending volume | Ensure SPF/DKIM/DMARC are configured. Warm up the inbox and lower sending volume. Use multiple inboxes / “Shuffle” if applicable. |
Load balancing — When multiple email addresses are connected and the campaign's Email Inbox setting is set to "Shuffle," Enginy distributes leads across all available inboxes.
Lead continuity — If a lead starts a sequence with a specific email address and you later disconnect that address, the system will not reassign the lead to another connected address. Instead, the lead will produce an error. To resolve this, you must reconnect the original email address.
Warning: If you disconnect an email address that has active leads mid-sequence, those leads will fail. The only way to fix this is to reconnect the same address that initiated the conversation.
Warm-Up
The Warm-Up feature trains an email address through an external provider to reduce spam detection and increase deliverability.
Detail | Value |
Cost | Varies on quantity; contact your Account Manager for pricing details. |
Estimated duration | 2 weeks |
Requirements during warm-up:
Pause all campaigns that use the identity (and therefore the email address being warmed up). Not mandatory but highly recommended to warm up properly.
Avoid sending any emails from that address outside of Enginy.
Tip: Following these requirements ensures the warm-up process completes successfully and your sender reputation improves as expected.
Email Rate
Configure the sending limits per email address to avoid spam filters:
Setting | Recommended Value |
Emails per day | 30 per inbox |
Emails per hour | 5 per inbox |
Notes:
Maximum allowed to configure is 80 emails sent per inbox per day and 10 emails sent per inbox per hour.
If you need to temporarily increase this rate for a valid reason, contact Support to request an increase. However, this isn't recommended, as it can harm your email reputation and reduce deliverability. If you decide to proceed, make sure that:
You've already been sending at this volume consistently.
Your sending domains have a strong reputation.
Signature
Create or edit the email signature that the identity will use when sending emails. You can use the built-in text editor, or switch to Advanced HTML Mode to paste HTML code directly.
Share Identity Link
Inside the configuration menu, the Share identity link button generates and copies a link that allows the owner of the identity to update their connection status (LinkedIn or email) without needing direct access to the Enginy platform. This is useful for refreshing credentials or connecting / reconnecting accounts. The link is valid for 24 hours.
