Skip to main content

How to remove a team member from your Enterprise account

Remove a Manager or Collaborator from your Enterprise account, and keep feeds syncing when the person you remove owns connected social accounts.

Written by Mario T.

Removing a staff member or Feed Collaborator takes their access to your account and its feeds away. If feeds still sync on social accounts that person connected, Juicer warns you first so those feeds do not quietly stop updating. This article shows how removal works and what to do when you see the warning. To add people instead, see Inviting other users to your Enterprise account.

Remove a team member

  1. Click your email address at the bottom left of the dashboard and, under Enterprise settings, choose Team settings.

  2. On the Manage Staff tab, find the person you want to remove. Staff members are listed under Account owner & staff, and people with access to specific feeds under Feed Collaborators.

  3. Click the ✕ next to a staff member's email address, or Remove next to a Feed Collaborator.

  4. Click OK when your browser asks whether you want to remove this user from your Enterprise account and all associated feeds.
    ​

You cannot remove the account owner. To hand the account to someone else first, see Changing account ownership.

What happens to their connected social accounts

When someone connects an Instagram, Facebook, or other social account to Juicer, the connection belongs to them. What happens on removal depends on who connected it last.

  • A teammate who stays reconnected it last. The connection moves to that teammate automatically and the feeds keep syncing.

  • A teammate who stays already has their own connection to the same social account. The feeds that teammate works on keep syncing on their connection.

  • Feeds still depend on a connection nobody else holds. Juicer stops the removal and shows a warning, as described below.

If you see the warning

The page is titled Feeds still use connections followed by the email address of the person you are removing. It lists each connection (platform and account name) along with the feeds that rely on it. If you remove the person anyway, their connections leave with them and those feeds stop updating.

To keep the feeds working, choose one of these options.

  1. Ask a teammate who stays and works on those feeds to reconnect the listed accounts on the Connections page (the link in the warning takes you there).

  2. Go back to Manage Staff and click the ✕ (or Remove) again. Once a teammate has reconnected the accounts, the warning no longer appears.

If you are fine with those feeds going quiet, click Remove anyway. Click Cancel to leave the person on the account.

⚠️ Important: Feeds that stop updating show their sources in a reconnect state until someone on the account connects the social account again. Posts already in the feed stay.

Removing users with the API or MCP

The same check applies when you remove a user with the Juicer API (DELETE /users/:id) or the Juicer MCP server. If feeds still sync on the connections that user owns, the request fails with a 409 error and the code user_has_connections_in_use, plus the list of connections and feeds. Repeat the request with force=true to remove the user anyway. In MCP, set force to true only after you have confirmed the feeds may stop updating. See Juicer MCP server – Connecting your AI agent for setup.

Troubleshooting

  • "No feeds depend on … connections any more, so you can remove them."
    A teammate now holds the connections, so the warning no longer applies. Click the ✕ (or Remove) again to remove the person.

  • A feed stopped updating after a removal
    Open the feed, find the source marked for reconnecting, and have a teammate on the account reconnect that social account.

If a removal is blocked and you cannot tell which connection is the cause, or a feed stopped syncing after you removed someone, contact us with the email of the removed person, the feed name, and the social account it uses and we will take a look.

Did this answer your question?