A post can fail because the connected account is missing a role or permission the network requires in order to publish. The connection itself is fine. Reconnecting helps only when the person signing in holds the role that is missing.
What happened
The post did not go out. CivAll asked the network to publish it, and the network answered that the connected account is not allowed to do that.
Nothing was published. The failed post is not retried automatically. Once the role is corrected, you publish it again yourself.
The permission in question belongs to the network, not to CivAll. This is about what Facebook, Instagram, TikTok, or YouTube lets the connected account do. It is not about who on your team is allowed to use CivAll.
Why this is not the same as an expired connection
An expired connection and a missing permission look similar from the outside. Both stop a post, and both are often answered by reconnecting. They are different problems, and treating one as the other is why some accounts get reconnected several times without improving.
- An expired connection means the credential ran out. Signing in again produces a new one, and the same person can do it. See Post failed: the account needs to be reconnected.
- A missing permission means the credential is current but the access behind it is too narrow. Signing in again reproduces exactly the same narrow access, unless the person signing in holds something more.
The rule to carry away: reconnecting only helps if the person reconnecting actually holds the missing role. Fix the role on the network first. Reconnect second.
What to do
- Find out what is missing. The failure notice names the network and, where we know it, the specific condition. The sections below cover the four networks this comes up on most.
- Fix it on the network. Grant the role, convert the account type, or move the access to someone who has it. This work happens in the network's own settings, not in CivAll.
- Reconnect the account in Accounts, signing in as someone who now holds that role.
- Publish the post again.
The Facebook account connected to this Page does not currently hold the Page role needed to publish.
This is the usual result after staff turnover. Someone connected the Page while they administered it, then left the organization or moved to another department, and their Page access was reduced or removed. The connection kept working until it did not.
Check the Page roles on Facebook, then reconnect the Page from Accounts with someone who has full access. Reconnecting as the person who lost the role will not work, and it is the most common wasted step here.
Because this follows staff turnover, it is worth checking every Page that person connected rather than only the one that failed.
Instagram publishing needs a Business or Creator account linked to a Facebook Page you administer. One of those conditions is not being met.
There are three ways to land here.
- The Instagram account is a personal account rather than a Business or Creator account.
- It is a Business or Creator account, but it is not linked to a Facebook Page.
- It is linked to a Page, but the connected Facebook account does not administer that Page. In that case, read the Facebook section above first, because that is the real problem.
Confirm the Instagram account is a Business account linked to the Page, then reconnect it. Since Instagram publishing runs through the linked Page, the Page's access has to be sound before the Instagram connection can be.
TikTok
TikTok did not grant every permission publishing needs when this account was connected.
TikTok presents its permissions during sign-in, and it is possible to complete the connection while leaving some of them unchecked. The account then connects successfully and fails later, at the moment a post needs the permission that was skipped.
Reconnect TikTok and accept all of the requested permissions.
YouTube
The connected Google account does not have upload rights on this YouTube channel.
Having access to a Google account is not the same as being able to upload to a channel, particularly on brand channels where several Google accounts hold different levels of access.
Reconnect the channel with a Google account that can upload to it. Take care to sign in as the intended account, because a personal Google account and the one that manages the channel are easy to confuse in a browser that is already signed in to both.
Other networks
On networks with no specific guidance, the failure means the same thing in general terms: the connected account is missing a permission that network requires in order to publish. Check the account's role or access on the network, then reconnect it in Accounts and publish again.
After the role is fixed
Publish the failed post again.
Then check the Planner for other posts scheduled on that account while the permission was missing. They failed at their send times and were not held for later. Anything still worth sending has to be published or rescheduled by hand.
If a newly connected account has never published successfully, it is worth confirming the role was in place at the time it was connected. Connecting a social account covers what each network expects before the connection is made.