Posting by itself
Posting by itself lets a pipeline schedule its own posts with nobody's click. It is off unless GreenMind has turned it on and approved your brand. Draft and review are the normal way to use pipelines, and nothing here is needed to use them.
It only decides whether a post a pipeline made goes out through the brand's own account. Nothing here likes, votes, follows, reposts or replies.
What it takes
All of these have to say yes, and they are asked again for every post:
- GreenMind has posting by itself switched on.
- GreenMind has approved your brand.
- GreenMind has not held this pipeline.
- The pipeline is on, and has not stopped itself.
- A person has approved enough of this version's posts.
- Every account the post goes to allows it, by its network's class.
When any says no, the post goes to the review queue instead, as if the outbox proposed it. They are asked again at the post's minute, so a post scheduled by itself can still be held back. It then waits with the note "Its pipeline may no longer post by itself, so this waits for a person to approve it."
Asking for it
This takes somebody who may publish the brand's pipelines, by default an Admin.
- In the editor, set the outbox to Posts scheduled by itself where allowed, else for approval, set its Budget, and save.
- On the pipeline's page, Posting by itself now shows. Under GreenMind's approval for the brand, say what its pipelines will post by themselves, and press Ask GreenMind.
- The request shows as Waiting, then Approved or Refused, with anything GreenMind said. An approval can later show as Withdrawn, which holds every pipeline of the brand at once. After a refusal or a withdrawal you can ask again.
Why a post waits
Posting by itself on the pipeline's page shows Posting by itself now or Sending posts for approval, and lists what is holding it back, in these words:
| The page says | What to do |
|---|---|
| Posting by itself is switched off across GreenMind for now. | Nothing you can do. Posts wait for approval. |
| GreenMind has not approved this brand to post by itself. | Ask GreenMind, or wait for the answer. |
| GreenMind has held this pipeline's posting by itself. | Read GreenMind's note on the page. Only GreenMind lets it go. |
| It stopped posting by itself, and waits for a person to turn it back on. | See When it stops. |
| Its first posts on this version go for approval, so people see what it makes. | Approve its posts. The page shows how many so far and how many it needs. |
Making a new version live starts the count of approved posts again. A version the optimiser made keeps the count. A post the pipeline already scheduled by itself goes out as the version its run started on said, whichever version is live by then; pausing the pipeline holds it.
Each network's class
Each network has a class, and Where it posts shows it for each channel, with why.
| Network | Class | What it means |
|---|---|---|
| X, Bluesky, Mastodon, Discord | Posts by itself | Its network welcomes scheduled posts. |
| Blog | Posts by itself | It is the brand's own, so no network's rules apply. |
| Facebook Page, Instagram, Threads | With an admin's consent | Each account needs an admin's consent for this pipeline. |
| YouTube, TikTok, Reddit, LinkedIn page | Approved post by post | Every post waits for approval. |
| Steam announcements, store pages and other channels posted to by hand | Approved post by post | A person posts these from a task. |
GreenMind can hold a channel stricter than this, and the page then says "GreenMind holds it stricter than its network does."
A post goes out by itself only if every account on it allows it. If one outbox names X and YouTube, each of its posts waits for approval, YouTube's class being what it is. To post to X by itself, give YouTube a pipeline of its own.
Giving consent
For a network marked With an admin's consent, the page may say "On these networks, posting by itself is open to GreenMind's own brands first. This brand's posts here wait for approval for now." Posts to those networks then wait, whatever else is set.
Otherwise, each account is listed with its channel:
- Somebody who administers the account, and may publish the brand's pipelines, presses I administer this account, and consent. This records that you administer it and agree this pipeline may publish to it without asking each time, with your name and the date.
- Consent is for one pipeline and one account.
- Withdraw consent takes it back, for anybody who may edit the brand's pipelines. Posts it already scheduled are held back.
Accounts lent by another brand
An account another brand lends yours needs that brand's say too, on any network. Until somebody there agrees, its posts wait for approval.
The lending brand's Pipelines page lists these under Posting by itself through your accounts. Somebody who may publish there presses I may publish for this brand, and agree, or Withdraw consent later. See Sharing.
When it stops
A pipeline stops posting by itself if something looks wrong. Its posts go for approval from then on, anything it had scheduled by itself is held back, and the people looking after it are told. The page gives the reason:
- It stopped after several failed posts in a row.
- It stopped because a post was refused, or held back as too like a recent one, which networks read as spam.
- It stopped because a network kept asking it to slow down.
- It stopped because its latest posts did far worse than the account's usual.
- It stopped because it reached its budget.
A refusal by a network also stops every other pipeline in the org posting by itself through that account.
Only a person turns it back on. Look at what happened, put it right, and press Turn posting by itself back on. That takes somebody who may publish the brand's pipelines. Lately lists what has happened and who did it.
The pipeline can still run throughout. Pausing it, or setting the outbox back to drafts or proposals, stops it posting by itself at any time.