Approvals and auto-approve

Every teammate has one switch that decides whether it asks you first: Auto-approve. With it off, anything that goes out in public or changes your live site waits in the teammate’s chat for your answer. With it on, the teammate does it on its own. There is nothing in between, and nothing to set per channel.

What asks first

With auto-approve off, a teammate stops and asks before it:

• publishes an article to your website,
• publishes a post to your social channels,
• applies a page fix to your live pages, or undoes one,
• deletes an article or a post,
• takes a batch off the calendar or removes a teammate, if you have given it those tools.

Everything else happens without asking, because nothing leaves QuQi: audits, AI answer checks, keyword research, drafts, pictures, videos, and batches put on the calendar.

Out of the box

A piece of work you ask to see first, “let me see it before it goes out”, waits for your OK even when auto-approve is on.

Say it for the whole chat, “don’t post anything until I approve”, and everything in that chat that would go out or change your website waits in a box for your yes: posts, articles, page fixes and changes to the calendar or settings, whoever on the crew does them. The panel beside the chat says so, and “go ahead on your own” lifts it. While a step of the plan waits in a box, the plan shows it waiting for your OK; your yes finishes it.

The approval box

Waiting work appears as a box in the chat, under whoever made it. Its top line says what it is, such as Article · for your yes, and Waiting on you until you answer.

Below that is the work in brief: its picture, its title, where it goes, and one line of facts, such as its length or when it goes out. Edit opens the rest:

• A post shows on each channel the way that platform shows it, with its picture and when it goes out. You can Edit text, Change picture (from your library or an upload), make a New picture, or Ask the teammate to change it in words.
• An article shows its cover, title, description, opening and length. Read and edit it opens the full article; Ask the teammate to change it sends your note to its chat.
• Page fixes show each page with the new wording proposed for each field, to pick from or leave as it is.
• Anything else opens where you can check it.

Then Approve or Reject. Approve does the thing: it publishes, puts the post on the clock for its time, or applies the fix, and the box shows what came of it. Reject does nothing and leaves the work where it is. While a change you asked for is still landing, Approve waits for it.

Once answered, the box says Approved or Rejected, who answered, and the outcome — “Published.” or “Scheduled for Thu 8 Oct, 09:00.” If the approval went through but the publishing did not, it says Approved, but it did not go through, with the reason. Each box is answered once.

Who can answer

Anyone who could make the change themselves: editors, admins and the owner. A viewer sees the box but cannot answer it.

Where to find what is waiting

• Waiting for your OK at the top of the chat sidebar, with a count. It takes you to the newest one.
• The chat row, which reads Waiting for your OK instead of the last message.
• The teammate’s own page, where its waiting work is listed first.
• The calendar, where a batch that made something waiting reads Waiting for you.
• An email for an article or a post — see Notifications.

Waiting work does not expire. It stays in the chat until you answer it.

Changing your mind

Auto-approve takes effect from the next thing the teammate does. Turning it on does not approve what is already waiting; answer those boxes yourself. Turning it off does not unpublish anything.