Connecting a social account establishes access; it does not mean every channel function works. Identify the chosen account, granted permissions and intended task. Start with a specific purpose and verify it in the correct account before relying on it for publishing or ads.
Specify the function to connect
Decide whether the task is publishing, interaction analysis, messaging, ad measurement or in-channel selling. Requirements can differ. Do not choose broader permissions merely because a connection screen offers them.
Distinguish content accounts from advertiser accounts and catalogs. For multiple stores or brands, maintain an internal account and authorized-owner reference without passwords or access tokens.
Verify account identity before confirmation
Check the username, page and business shown during authorization. A personal browser session can surface a different account from the one intended. If the correct account is absent, resolve provider access first.
Use the official connection flow provided by the platform. Do not put account passwords in product text or public support messages, and do not expose access tokens in shared files.
Distinguish access types
Scroll the table horizontally to see all columns.
| Function | What it establishes | What it does not establish |
|---|---|---|
| Account identity | Selected authorized account | Every permission |
| Interaction reading | Access to specified data | Messaging access |
| Content publishing | The tested format works | Every format and channel |
| Ads or shopping | Approved function availability | Every business and market is eligible |
Test the intended task, not just a connected label
After connection, confirm the destination account and test the actual function through an appropriate authorized action: reading information, saving a draft or publishing an approved test when needed. Read access does not establish publishing or messaging access.
Mollkom availability depends on enabled services, provider permissions and account state. Connecting TikTok or Instagram does not automatically enable in-channel shopping, every message type or every publishing format.
Plan for connection failures
Assign ownership for expired authorization or changed permissions and a way to detect failed publishing. Keep non-secret operation identifiers and statuses, and avoid publishing again while the previous outcome is unknown.
After ownership changes or reconnection, recheck destinations and scheduled work. Resolve rejections through official channels rather than bypassing country or business eligibility with inaccurate information.
Common questions
Is a connected status enough to begin scheduling?
Verify the account, function and an actual test result first, then check each scheduled operation’s status.
Should passwords be shared with the team?
Use appropriate official permissions and connection flows instead of distributing credentials in shared files or chats.
Your next step
Continue with the social-to-store sales journey, or register and start your store. Apply the process to a small sample before expanding.
Sources and references
Information reviewed on 27 September 2026. Service availability and provider terms can change.