Yadulink / Documentation / Multi-account

Organize several LinkedIn accounts without losing sales control.

Multi-account management becomes useful when each account keeps its limits, owner, signals, lists, and reporting instead of creating indistinct volume.

Multi-account

What to isolate per account

Each account should keep its context: audience, country, language, sequence, risk level, CRM owner, and signal history.

Multi-account

Role of permissions

Agencies and sales teams should separate who can observe, prepare, launch, or change an action. MCP and API should follow the same split.

Multi-account

Multi-account reporting

Reporting should show which accounts create replies, which accumulate unhandled signals, and which should be paused.

Verified facts

What this documentation should make explicit.

Purpose

Multi-account management becomes useful when each account keeps its limits, owner, signals, lists, and reporting instead of creating indistinct volume.

Workflow proof

Each account should keep its context: audience, country, language, sequence, risk level, CRM owner, and signal history.

Assistant prompt

Help me structure a multi-account LinkedIn setup in Yadulink with workspaces, permissions, reporting, CRM owners, and guardrails.

Verification method

How to turn the guide into an operational test.

  1. 01 Management framework Separate accounts by workspace, client, brand, or sales team.
  2. 02 Management framework Define permissions: read, prioritization, reporting, action, or admin.
  3. 03 Management framework Map each account to its lists, sequences, CRM owner, and guardrails.