> ## Documentation Index
> Fetch the complete documentation index at: https://help.pipelime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Channels overview and availability

> What LinkedIn, WhatsApp, Instagram and MercadoLibre each do, where they appear in the app, and what decides whether you can use them.

export const UiPath = ({children}) => {
  const parts = String(children).split(/\s*(?:→|>)\s*/).filter(Boolean);
  return <span className="pl-path">
      {parts.map((part, index) => <span key={`${index}-${part}`}>
          {index > 0 && <span className="pl-path__sep">→</span>}
          {part}
        </span>)}
    </span>;
};

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

LinkedIn, WhatsApp, Instagram and MercadoLibre are the four channels besides email that a workspace can connect an account to. Each one is gated on its own, so having one of them says nothing about the other three.

## Where each channel lives

Every channel has an accounts page inside the **Integrations** list, alongside **Email Accounts**: **LinkedIn Accounts**, **WhatsApp Accounts**, **Instagram Accounts** and **MercadoLibre Accounts**. Three of the four also have a conversation screen under **Communication**: **LinkedIn Chat**, **WhatsApp Chat**, and a row labelled just **MercadoLibre**, which carries a count of the [buyer questions still waiting on an answer](/en/channels/mercadolibre-questions). Instagram has no row under **Communication**: [its comments](/en/channels/connect-instagram) are read and answered on one connected account, under that account's **Posts & Comments** tab.

Seeing one of a channel's two screens does not mean seeing the other. Each accounts page has a permission of its own (`read-linkedin-accounts`, and the same pattern for the other three), while the three conversation screens share a single permission, `read-messages`, with **Inbox**.

<Screenshot id="channels/overview--sidebar" frame="bare" alt="The expanded sidebar with every channel switched on: an Overview, Outreach and Leads group, then Communication showing Inbox, LinkedIn Chat, WhatsApp Chat and MercadoLibre, then Meetings, then a closed Integrations row at the bottom" caption="Captured with every channel switch on, so this is the longest the Communication group gets. In the app as it ships, only Inbox and LinkedIn Chat are in it." />

## What decides whether a channel is in your sidebar

Four things, applied in this order.

Your role goes first. Without the permission behind a row, the row is gone and nothing further down can bring it back. Then your workspace's own menu: individual rows can be forced on or off for one workspace, which beats both checks below. It is set up on request, and no screen in your own settings changes it.

Third is the feature switch. **WhatsApp Accounts**, **WhatsApp Chat**, **Instagram Accounts**, **MercadoLibre Accounts** and **MercadoLibre** each sit behind one, it is set when the app is built, and all five are switched off in the app as it ships: hidden for everyone, and no plan you buy brings one back. LinkedIn has no switch of this kind, so its two rows are never hidden this way.

Last is the channel's own availability check, which passes if the channel is switched on for everybody, if your account holds a seat for that channel on its plan, or for a staff session. LinkedIn is switched on for everybody in the shipped app, so it clears this check in every workspace. This check reads your account rather than the workspace, so it can never make one of your workspaces differ from another. [Why can't I see a menu item?](/en/settings-team/why-cant-i-see-a-menu-item) works through the same four layers from the other end.

## What an accounts page looks like

Open <UiPath>Integrations → LinkedIn Accounts</UiPath> and you get a banner about how the credentials are held, then a card carrying **Connect Account** (1), a search box, four counters reading Total Accounts, Active, Paused and Errors (2), and a table of what is connected. **WhatsApp Accounts** and **Instagram Accounts** are built from the same pieces and the same four counters; on WhatsApp the counters sit above the card rather than inside it. The button is there only for a role that may connect accounts on that channel. Reading the list and adding to it are two different permissions.

<Screenshot id="channels/overview--accounts-list" url="/linkedin-accounts" alt="The LinkedIn Accounts page: a security banner, a card headed LinkedIn Accounts with a Connect Account button on the right, a search box, four counters reading Total Accounts 1, Active 1, Paused 0 and Errors 0, and a table with one connected account" caption="Connect Account goes grey once you have used up the accounts your plan allows on that channel, and says so in a tooltip." marks={[{ n: 1, x: 90, y: 31 }, { n: 2, x: 29, y: 48 }]} />

**MercadoLibre Accounts** is the one that reads differently. Its button is **Connect account**, and its four numbers count connected accounts, synced listings, unanswered questions and the accounts that need attention. While anything is unanswered that counter carries an **Answer now** link, which takes you to the **MercadoLibre** screen.

## Related

<CardGroup cols={2}>
  <Card title="Connect a LinkedIn account" icon="link" href="/en/channels/connect-linkedin-account">
    Sign in with your LinkedIn credentials rather than OAuth, clear whichever checkpoint LinkedIn asks for, and reconnect a session that drops.
  </Card>

  <Card title="Connect a WhatsApp number" icon="smartphone" href="/en/channels/connect-whatsapp">
    Scan a QR code or enter a pairing code, exactly like WhatsApp Web's own linked-devices flow.
  </Card>

  <Card title="How your channel credentials are handled" icon="shield" href="/en/channels/security-of-connected-accounts">
    What actually happens to the password you type into a connect dialog, and how it differs by channel.
  </Card>

  <Card title="Why can't I see a menu item?" icon="eye-off" href="/en/settings-team/why-cant-i-see-a-menu-item">
    The four layers again (role, workspace menu, feature switch, plan) when a row you expect is missing.
  </Card>
</CardGroup>