Reconnect A Social Profile
Statusbrew connects to your social accounts using access tokens issued by each social network. When a token expires or becomes invalid, you'll need to reconnect the profile to restore publishing, Engage, and Reporting.
Who Can Do This
Primary Owner, Owner, or Admin role in Statusbrew. For Facebook and Instagram, you must also have Full Control access to the page in Facebook Business Settings.
Why Profiles Disconnect
Profiles disconnect when their access token is no longer valid. Common causes:
You changed your password on the social network
You revoked Statusbrew's access in the social network's app settings
The user who originally connected the profile lost admin access on the social network side
Most social networks issue tokens naturally with a built-in expiry date
When a profile disconnects, scheduled posts won't publish, Engage stops loading new activity, and analytics data stops collecting until the profile is reconnected.
How To Reconnect A Disconnected Profile
Profiles that need reconnection show a red indicator in the Profiles list.
Go to Settings.
Select Profiles.
Find the profile marked with a red indicator and click Reauthenticate.
You'll be redirected to the social network. Follow the prompts to log in and restore access.
Facebook and Instagram only: During the reauth flow, Facebook will show a permissions screen. Do not uncheck any permissions. If permissions are missing after reconnecting, Statusbrew may appear connected but still fail to publish, comment, or like returning a permissions error (Error #200). If this happens, see Common Publishing Errors or Common Engage Errors.
How To Proactively Refresh Access

You don't have to wait for a disconnection. Refreshing access proactively is a good troubleshooting step if you're seeing unexpected errors even though the profile appears to be connected.
Go to Settings.
Select Profiles.
Click (More) beside the profile you want to refresh.
Select Refresh access and follow the prompts.
FAQs
My profile shows as connected but I'm still getting errors. What's wrong?
A connected profile can still be missing permissions. This happens when permissions were deselected during reauthentication. The token is valid, but Statusbrew's access is incomplete. Go to Facebook Business Integrations, confirm all permissions for Statusbrew are enabled, then reauthenticate.
Does reconnecting affect my scheduled posts or Engage conversations?
No. Reconnecting restores access without affecting your scheduled content or existing conversations. Posts already in the queue will publish as normal once the profile is reconnected.
Do I need to reconnect all profiles or just the ones showing errors?
Only profiles marked with a red indicator need reconnection. You can also use Refresh access on any profile proactively if you're troubleshooting errors on a profile that appears connected.
Why am I getting Error #200 after reauthenticating?
Error #200 is a permissions error from Meta. It means Statusbrew doesn't have the access it needs, even though the profile appears connected.
The most common cause is that one or more permissions were unchecked during the Facebook reauth flow. The token gets renewed, but without full permissions, actions like publishing, commenting, or liking still fail.
To fix it:
Go to Business Integrations in your Facebook settings.
Find Statusbrew and click View and edit.
Make sure every permission is toggled on for all your pages.
Click Save, then reauthenticate the profile again in Statusbrew.
Why am I getting a LinkedIn OrganizationAcls or permission error while reauthenticating a profile?
This error means LinkedIn is not allowing the connected LinkedIn user to access the Page/organization permissions needed to reauthenticate the profile.
You may see an error like:
LinkedInResponseException
OrganizationAcls
Viewer is not allowed to view organizationAcls
ADMINISTRATOR_READ=false
RoleState APPROVED
This usually happens when the LinkedIn account being used does not have the required admin permissions for that LinkedIn Page, or LinkedIn is not returning the admin permission correctly during reauthentication.
To fix this:
Make sure you are logging in with the LinkedIn account that has admin access to the Page. Check the Page access directly inside LinkedIn. If access was recently granted, wait for LinkedIn to reflect the permission update, then try again.
Reauthenticate the LinkedIn profile in Statusbrew using the correct LinkedIn admin account.
If the same error persists after confirming admin access, contact the Statusbrew team via chat and share the error message. The Statusbrew team can check the profile connection from the backend.
Why does the wrong social profile open when I try to connect or reconnect an account?
This usually happens because your browser is already logged in to another account on that social network.
For example, you may be trying to connect a different LinkedIn, Facebook, or Instagram profile, but the network keeps opening an already logged-in account or an account that was previously connected.
To fix this, try connecting the profile from an incognito/private browser window.
Before reconnecting, make sure:
You are logged in to the correct account on the native social network.
You have the required admin/page access for the profile you want to connect.
You are not logged in to a different account in the same browser session.
If incognito works, the issue was likely caused by the browser using an old or incorrect login session.