Connection problems

When you connect X, LinkedIn or Threads (from Settings, Getting started or the Digital Brain), you may see a window titled This [platform] profile is already connected to another Typeshare account. Each X, LinkedIn or Threads profile can only be connected to one Typeshare account, and the profile you just signed in with already belongs to a different Typeshare account. Nothing was connected.

The window explains two cases:

• Wrong profile? You were signed in to the wrong profile on the platform. Log out of the platform (for example log out of X in your browser), log in to the right profile, then go to Settings > Channels and click Connect again.
• Your profile? It is your profile, but it's on another Typeshare account, often one you made earlier with a different email. Log out of Typeshare and sign in with that X or LinkedIn profile: it opens the account the profile is on. Go to Settings > Channels and click Disconnect on that platform. Then log back in to this account and connect it here.

If that other Typeshare account has no plan (for example an old account from classic Typeshare), it opens on the upgrade page. Click Settings at the bottom of the page, then Channels, and click Disconnect there. If the profile is the only way to sign in to that old account, it can't be disconnected; delete the old account in Settings > General instead. That frees the profile but deletes everything on the old account.

Removing Typeshare from the apps connected to your X or LinkedIn account doesn't free the profile: the link is on Typeshare's side.

If you can't get into the other account, send a note from Help & feedback in the account menu and the team will move the profile for you.

Click Got it to close the window.

When you click Connect for X or LinkedIn and the profile is on another Typeshare account that isn't in use, Typeshare moves the profile to the account you're signed in to, so you don't see the "already connected" window. Signing in to X or LinkedIn on the Connect step shows the profile is yours.

An account counts as not in use when it has no plan (or its plan ended), has never bought anything, and has had no post written, edited or scheduled in the last 60 days. The old account and everything on it stay as they are; only the X or LinkedIn connection moves. You can still sign in to the old account with its email or other login.

An account that has a plan, including one set to cancel, or that has been used in the last 60 days, keeps its profile, and you see the "already connected" window instead. Threads profiles never move this way.

The message [platform] did not grant access means you cancelled or declined the permission screen on X, LinkedIn or Threads, so nothing was connected. Go to Settings > Channels and click Connect again, and allow access when the platform asks.

If you see Could not connect [platform] instead, something went wrong on the way back to Typeshare. Wait a moment and try Connect again.

[platform] didn't finish connecting means you came back from X, LinkedIn or Threads, but Typeshare couldn't match the return to the Connect you started, so nothing was connected. It happens when the sign-in on the platform is finished in a different tab or browser than the one you clicked Connect in, or takes more than an hour.

Go to Settings > Channels, click Connect again, and finish the platform's sign-in in that same tab.

If LinkedIn stops on its own page (a security check, a code sent to your email or phone, or a LinkedIn error) and never sends you back, Typeshare never hears about it and nothing is connected. Finish any check LinkedIn asks for, then click Connect again in Settings > Channels. If you're already signed in to LinkedIn in that browser, the connection usually takes a few seconds. If LinkedIn keeps showing an error, contact support from the help chat with a screenshot of what LinkedIn shows.

You came back from X, LinkedIn or Threads, but Typeshare couldn't read the account you just signed in with, so the agent isn't connected yet. Typeshare already tries a second time before showing this. Wait a moment, then click Connect again in the agent's room. If it keeps happening, connect the account in Settings > Channels first, then go back to the agent's room and click Use with that account's name.

If it says the platform "didn't give Typeshare posting access" instead, connect again and approve access when the platform asks.

If it says "this page lost track of your workspace", reload the page and click Connect again.

A red Needs reconnecting label next to an account in Settings > Channels means Typeshare can no longer use that account. The access expired, or it was revoked on the platform (for example you removed Typeshare from your X or LinkedIn app permissions). It also shows when Threads no longer lets Typeshare read your profile, which can happen to a Threads account connected long ago in classic Typeshare. Until you fix it, nothing can be published there, and scheduled posts to that platform will fail.

To fix it:

• LinkedIn, Threads or Substack: click Reconnect and sign in again.
• X or Bluesky: click Disconnect, then Connect, and sign in again.

The row may also say "Access was revoked. Reconnect to keep publishing here."

If you connect X and see "X didn't give Typeshare posting access. Connect X again and approve access when X asks.", X sent you back to Typeshare without the permission Typeshare needs to post for you. Go to Settings > Channels, click Connect on X again, and approve access on the X screen.

The same problem can show up when you publish: "Typeshare needs posting access to your X account. Reconnect X in Settings → Channels." In the Write editor the X tile then says "X isn't connected yet", even if Settings > Channels lists X. To fix it, go to Settings > Channels, click Disconnect on X, then Connect, and sign in again.

If it still fails after that, contact support from the help chat.

Typeshare posts to X through its own X developer account, and that account has hit its limit with X. It isn't your X account or your post: nothing needs reconnecting and the post is saved. The Typeshare team is alerted automatically. Posts don't go out on their own once it's fixed, so try again in a little while: publish from the Write editor again, or for an agent post that shows as failed, open it and publish it again. A scheduled post that failed this way needs to be scheduled again.

LinkedIn connections expire after about 60 days. That is LinkedIn's rule, not a Typeshare setting. Settings > Channels shows "Expires in N days" on the LinkedIn row so you can see it coming.

In the last 7 days before it runs out, a Reconnect button appears on the LinkedIn row: click it and sign in to LinkedIn again to renew it. Once LinkedIn has expired, the row shows Needs reconnecting and posts to LinkedIn can't go out until you reconnect.

LinkedIn can also end a connection before that date, for example when you remove Typeshare from your LinkedIn permissions. Publishing then says "Your LinkedIn connection has expired or was revoked. Reconnect LinkedIn in Settings → Channels, then try again." Go to Settings > Channels and click Reconnect on LinkedIn (if the row has no Reconnect button, click Disconnect, then Connect), sign in again, and publish the post again.

Substack logins expire, and Substack can reject a saved login (for example after you log out of Substack everywhere). When that happens, the Substack row in Settings > Channels shows Needs reconnecting and one of these messages:

• "The Substack login lapsed. Reconnect to keep publishing here."
• "Substack rejected the saved login (...). Reconnect to keep publishing here."
• "Substack needs reconnecting to keep publishing here."

To fix it:

1. Use Chrome (or Edge, Brave or Arc) on a computer, with the Typeshare Connector extension added and turned on. Without it, reconnecting can't work: the Connector window stays on Add the Typeshare Connector.
2. In that same browser, open substack.com and check you're logged in as the right @handle.
3. In Typeshare, in the same browser, go to Settings > Channels and click Reconnect on Substack.
4. Follow the Connector window. It finishes by itself once it finds the extension and your Substack login, and ends on Substack is connected.

A post that failed because of this may say "Your Substack session has ended, so this could not be published. Reconnect Substack in Settings → Channels, then try again." After reconnecting, publish the post again.

If the Connector window says That didn't connect with "Substack didn't accept the login in this browser":

1. Click Open Substack, log out of Substack, then log back in.
2. Come back to the Typeshare tab and click Try again.

If it fails again, or a post still says the Substack session has ended right after you reconnected, contact support from the help chat. Say which message you saw, so support can look up exactly what Substack answered.

No. A "Confirm it's you on Substack" window, or "Substack wants to confirm it's you before sending this newsletter", is Substack's own security check, not your login ending. Enter the 6-digit code Substack emails you and carry on. See "Why does Substack ask me for a code when I publish?".

Substack itself was down or overloaded when Typeshare asked it to send or check your code. Nothing was published. Wait a few minutes, then click to resend the code or enter it again. If it keeps happening, check Substack is working in your browser, then contact support from the help chat.

"Your Substack account doesn't have a publication yet, so there's no newsletter to send this to." means Substack has no newsletter (publication) on the account you connected. Substack Notes still go out, because they come from your profile; a newsletter needs a publication to be sent from.

1. On Substack, start your publication (substack.com → Start writing), or check you're signed in to the account that runs it.
2. Back in Typeshare, publish again. Typeshare checks Substack for a new publication when you publish, so you don't need to reconnect.

If you started your publication after connecting Substack, Typeshare also picks it up on its own within a day, or straight away from Settings > Channels > Substack > Refresh from Substack.

"Substack refused this on (publication) (...). Your Substack login still works, so reconnecting won't fix it." means your Substack login is fine (Notes still go out), but your publication refused the newsletter. Reconnecting won't change it. Check on Substack that the account Typeshare shows in Settings > Channels is an admin of that publication. If it is, contact support from the help chat with the message you saw.

The Typeshare Connector doesn't ask which Substack account to use. It connects whichever account is logged in to Substack in that Chrome browser. If you have more than one Substack account, disconnecting and reconnecting brings back the same one until you change your Substack login.

To fix it:

1. In Chrome, go to substack.com and log out.
2. Log in to the Substack account you want, and check your profile shows the right @handle.
3. In Typeshare, go to Settings > Channels, click Disconnect on Substack, then click Connect.
4. Check that the Substack is connected window shows the right @handle.

Use the same Chrome window (and the same Chrome profile) for Substack and Typeshare, because the extension only sees the Substack login in the browser it's running in.

Check these in order:

1. Browser: connecting Substack needs Chrome (or Edge, Brave or Arc) on a computer. Phones, tablets and other browsers can't run the Typeshare Connector extension. Use Copy link to this page to open the same step in Chrome.
2. Extension: if the window stays on Add the Typeshare Connector after you installed it, make sure the extension is turned on in Chrome, then return to the Typeshare tab.
3. Substack login: if it says "You're not logged in to Substack right now", click Log in to Substack, log in in the same browser, then come back and click I'm logged in.
4. Substack didn't accept the login: Substack sometimes refuses a fresh login for a few seconds, so the Connecting to Typeshare step keeps trying by itself for up to half a minute. If That didn't connect says "Substack didn't accept the login in this browser", click Open Substack, log out and back in, then come back and click Try again. This also happens if Typeshare checked while you were still logging in.
5. Other errors: if you see That didn't connect with another reason, read it and click Try again. Still stuck? Contact support from the help chat.

Some browsers (often Safari or Firefox) block copying. When that happens you see "Could not copy the link. Copy it from here:" with the link underneath: select the link in that message and copy it yourself, or copy the address from your browser's address bar. Then open it in Chrome on a computer.

The agent has no account to post with on that platform. This happens when you disconnect the account from the agent's Info tab: the agent stays disconnected, even if you reconnect the same account in Settings › Channels, so a reconnect never switches an agent back on behind your back. To fix it, open the agent's chat and press Use @yourhandle on the connection card, or connect the account again from the agent's Info tab. Then press Post now, or let the post go out at its next slot.

If X or LinkedIn is the only way you sign in to Typeshare and your account has no verified email, Typeshare won't disconnect it, because you would be locked out. You see "[platform] is the only way to sign in to this account."

To change which account is connected, log out of Typeshare and log back in with the platform account you want.

In the Write editor, a platform tile with a dashed outline, or the message "[platform] isn't connected yet. You can preview, but not post.", means that platform isn't connected in Settings > Channels. You can still write and preview the post for that platform, but it won't publish there.

Click Connect in that message to open Settings on Channels and connect the account. Then return to your post.

Add first comment is hidden until LinkedIn approves Typeshare for comment access. If a post already has a first comment and the editor says "Your LinkedIn connection needs comment access. Reconnect after access is enabled, or remove the first comment.", your LinkedIn connection doesn't have permission to post comments. To publish now, click Remove first comment under the comment box, then post again.

On a post that's already scheduled, the same message shows where the editor says your changes are saved, and your edits to that post don't save until you click Remove first comment. Reconnecting LinkedIn doesn't help yet: Typeshare can't ask LinkedIn for comment access until LinkedIn approves it.