← All posts

A calmer setup for social media teams

A social media team rarely manages one account. There's the brand's main profile, regional accounts, a support account, and often clients' accounts too. Several people post, reply and report — at different hours, from different places.

The usual setup — everyone logged into everything in their own browser, passwords in a chat thread — works until it doesn't: a login prompt nobody can answer because the two-factor code goes to someone on holiday, a "suspicious login" lock because the account was opened from four countries in a day, or a former freelancer who can still post.

Here is a calmer way to run it.

Put each account in its own profile

Give every social account a profile: a separate browser with its own cookies and logins. Logged in once, it stays logged in for everyone who is allowed to open it.

  • Save the account's login and two-factor secret in the profile (they stay on the computer, not on our server). The profile can show the current two-factor code, so the whole team isn't waiting for one person's phone.
  • Set the profile's platform to the network, so it opens straight on the right page.
  • Use groups per brand or client, and tags per network.

Keep the account's location consistent

Social networks protect accounts by watching where they are used from. A brand account that moves between the agency's office, a freelancer's home in another country and a phone on mobile data — all in one afternoon — looks like a takeover attempt.

  • Give each account's profile a stable proxy in the account's home market and keep it.
  • Let time zone and language follow the proxy (the default).
  • Run a leak check once: it confirms the network sees only the proxy, not each team member's own connection.

The result: wherever your team members are, the account keeps seeing the same, familiar "device" and location.

One person in an account at a time

Two people replying in the same account at once can overwrite each other's session. While a profile is open on one computer, it is locked for the rest of the team, and the others see who has it. When they close it, cookies are synced — encrypted on the computer before upload — and the next person continues where they left off.

If your team truly needs several people in one account at the same time, a manager can allow it in Login security; whoever closes last then saves the session.

Access that matches the job

  • Community managers open and post in the accounts of their brands: give their role access to those groups only.
  • Freelancers get just the profiles they work on, ideally as guests through Share with an account — no seat on your plan, no view of the other accounts, and gone with one click when the project ends.
  • Clients who want to look in can get Can see or Can open access to their own profile, without your passwords.
  • Managers see everything, manage people, and read the activity log: who opened which account, when and from which computer.

Require two-factor sign-in for the whole team. Your team's accounts can open every brand you manage; they deserve the same protection as the brands' own passwords.

Routine work without the clicking

  • Window synchronizer: check the notifications of five regional accounts at once — what you do in one window happens in the others.
  • Window tools: open the same link in every open profile, or type the same reply text into each focused field.
  • Flows: open each account in the morning, take a screenshot of the notifications, and collect them for the daily report.

Social networks have strict rules on automation. Use flows for checks and reporting; posting, following, liking and messaging should stay with people, the way the platforms expect.

When someone leaves

  1. Remove them from the team (or stop sharing with the guest). Their access to the team's profiles ends immediately; profiles they had open are released.
  2. Change the passwords of accounts they knew, and rotate two-factor secrets if they saw them.
  3. Check the activity log for anything unusual in their last days.

Run only accounts you own or are authorized to run, and follow each network's terms. Our Acceptable Use Policy describes what the service may and may not be used for.