> For the complete documentation index, see [llms.txt](https://doc.autoreach.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.autoreach.tech/settings-and-configuration/multi-account.md). # Multi-Account Management Manage your X, LinkedIn, and Instagram accounts from a single AutoReach dashboard. Each account has its own limits, activity window, and health status, and is assigned a proxy from your proxy pool (proxies can be shared across accounts or dedicated, see [Proxies](#proxy-configuration) below). ## Account Slots One subscription includes **one account slot per platform**: 1 LinkedIn, 1 X, and 1 Instagram account. Offers and sequences are unlimited. To connect more than one account on the same platform, contact support at . There is no self-serve add-on for extra accounts. Each connected social account can also attach up to **2 email mailboxes** (one Gmail and one Outlook) for email outreach. See [Email Channel](/outreach-and-sequences/email-channel.md). ## Account Status Each account shows one of these statuses: | Status | Description | | --------- | ----------------------------------------------- | | Active | Operating normally | | Paused | Paused - no actions scheduled | | Suspended | Suspended due to safety issue - review required | | Expired | Authentication expired - re-connect required | ## X Accounts ### Authentication X accounts connect through the AutoReach Chrome Extension, which links your active browser session to AutoReach. ### Configuration * **Daily action limits**- configurable per account * **Activity window**- time frame when actions execute (default is two blocks, 09:00-13:00 and 14:00-18:00, Mon-Fri, weekends off, max 8h/day total), per-account, so each X account can have its own start/end/timezone. Set on the account's detail page under the Configuration tab. * **Calendar**- per-account booking link and webhook setup (Calendly or Cal.com) * **Browser fingerprint**- per-account OS spoofing (Auto/macOS/Windows/Linux) * **Proxy**- the proxy assigned to the account from your proxy pool (see [Proxy Configuration](#proxy-configuration)) ## LinkedIn Accounts ### Authentication LinkedIn accounts connect through the Chrome Extension, same as X. ### Configuration Each LinkedIn account exposes the same per-account configuration as X (activity window, calendar, browser fingerprint, assigned proxy) from **Accounts → \[account] → Configuration**. ### Connection Limits LinkedIn connection requests have a daily limit tracked per-account. You can set the daily connection limit on each LinkedIn account to any whole number from 1 to 100 (default 15, which is the recommended starting point). See [Supported Actions](/outreach-and-sequences/supported-actions.md#connection-request) for deferral behavior. ## Instagram Accounts Instagram accounts connect through the Chrome Extension and expose the same per-account configuration as X and LinkedIn (activity window, browser fingerprint, assigned proxy). ## Proxy Configuration Proxies are **optional** and managed in one place: the [**Proxies**](https://github.com/tiwanaca/autoreach-docs/blob/main/proxies/README.md) page. From there you can view your proxy pool and which accounts are assigned to each proxy, add a proxy, edit or remove a proxy, and assign a proxy to a specific account. One proxy can be **shared across all three platforms** (LinkedIn, X, and Instagram) or you can assign a dedicated proxy per account, your choice. You have two proxy options, chosen during onboarding: * **Managed proxy**- an IPRoyal ISP residential static proxy provided by AutoReach. It is **free during your trial**, then **$15/mo** per managed proxy if you do not cancel. By default one managed proxy is shared across your accounts. * **Bring your own (BYOP)**- use your own proxy at no extra cost. Enter the host, port, username, password, and type (HTTP or SOCKS5). AutoReach verifies connectivity before saving so you do not assign a dead proxy. If an account has no proxy assigned, it cannot run actions and is paused until you assign one. ### Antidetect Browsers If you run AutoReach inside an antidetect browser (SunBrowser, GoLogin, Multilogin, Dolphin Anty, Incogniton, Kameleo, AdsPower, and similar tools), you must configure your proxy inside the antidetect browser itself, not through the AutoReach extension. These browsers manage proxies at the browser launch layer and block extensions from calling Chrome's proxy API. If the extension tries to apply proxy settings, the browser kills the popup process before any error can be caught, which looks like the extension crashing or closing instantly. How AutoReach handles this: * The extension tries to auto-detect antidetect browsers from the user agent and skips proxy API calls when it matches * Detection is best-effort. Most antidetect browsers spoof their user agent to look like vanilla Chrome, which is the whole point of using one, so auto-detection will often miss them on first launch * Your proxy still works normally because the antidetect browser routes traffic through it at the network layer What you need to do before opening the extension on an antidetect browser: 1. Configure the proxy inside your antidetect browser profile first (this is the default workflow for these tools) 2. Do not configure a separate proxy in the extension popup. Leave proxy settings empty or set to "browser-managed" 3. If the popup closes instantly the first time you open it, that is the proxy API being called before detection kicks in. Set `__skip_proxy_api` to `true` in the extension's `chrome.storage.local`, then reopen the popup If you hit this crash, contact support with your browser name and version so we can add it to the detection keyword list and prevent it for other users. ## Pausing and Resuming **Pause**: All pending actions are cancelled and no new actions are scheduled. Associated warmup strategies and sequences are automatically paused. **Resume**: Account reconnects and operations resume. Previously paused warmup strategies and sequences are reactivated. ## Account Health Each account card on the Accounts page displays: * **Status badge**- the account's current state: Active, Sleeping (outside its activity window), Paused, Setup (no proxy assigned yet), Inactive, Expired, or Suspended * **API calls today**- how much of the account's daily activity allowance has been used so far today, shown as `used / total`. Every action AutoReach performs through the account consumes API calls: sending DMs and connection requests, enriching profiles, engagement actions (likes, comments, follows), and searches. When the allowance is used up, AutoReach automatically pauses activity on that account and resumes after the counter resets the next day. This is a safety mechanism that keeps the account's daily activity at a healthy level. A dash means the counter has not loaded yet. * **Proxy**- Configured (verified and working), Not verified, or Required (no proxy assigned) * **Last active**- when the account last performed an action * **Added**- when the account was connected Check the Accounts page regularly. Error indicators may signal proxy issues or authentication expiration. ## Deleting Accounts From an account's detail page, click **Delete Account** to permanently remove it. Deletion is irreversible and removes: * The account connection * All associated conversations, sequence enrollments, and warmup state for that account Deleting an account does **not** cancel or remove its proxy. Because a proxy can be shared across multiple accounts, proxies are managed separately on the [Proxies](https://github.com/tiwanaca/autoreach-docs/blob/main/proxies/README.md) page. If you want to stop paying for (or remove) a proxy after deleting an account, remove it there. Removing a managed proxy cancels its IPRoyal order and lowers your $15/mo proxy add-on accordingly. You will see a confirmation modal listing the consequences before the delete proceeds. Active campaigns using the account are affected. **Base account protection**- the primary account on your workspace cannot be deleted. If you need to remove it, contact support. A separate modal blocks the action and explains this. ## Next Steps * [**Account Safety**](/settings-and-configuration/account-safety.md): Error handling, cooldowns, and cascade pause behavior * [**Blacklisting**](/settings-and-configuration/blacklisting.md): Exclude specific accounts from outreach --- # 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://doc.autoreach.tech/settings-and-configuration/multi-account.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.