Approvals

Nothing goes live without a person approving it inside cnvrtlocal. That's true even if you gave an AI app every permission.

What needs approval

• Publishing a site
• Connecting a custom domain
• Adding a page to a site that's already live
• Editing, adding, moving, hiding or removing a section, or changing a section's image, on a site that's already live
• Scheduling blog posts to publish

How it works

1. You ask your AI app to publish, for example.
2. The AI creates a request and gives you a link.
3. Open the link, or go to Approvals in the top bar of cnvrtlocal. A count shows how many requests are waiting.
4. Check the request and approve it.
5. cnvrtlocal does the real action as you, the person who approved.

If you don't approve, nothing happens.

Editing a live site

When your AI changes a section on a live site, it creates an approval request and gives you the approval id and a link. This covers editing text or list items, adding, moving, hiding or removing a section, and setting a section's image. The Approvals list in cnvrtlocal shows a before and after preview, so you can see exactly what would change.

For adding, moving, hiding and removing sections, the preview shows the page's section outline before and after, with the new, moved or removed section marked. For an image, it shows the old and new image side by side.

When you approve, cnvrtlocal plans the change again against the site as it is then. If that part of the page was edited since the request was made, the request fails and nothing is overwritten. Examples: a section you asked to remove was edited, the section a new one was to sit next to is gone, or an image spot now shows a different image. Otherwise the change is saved and your site is republished.

If your AI asks again for the same thing (the same fields of the same section, or the same image spot), the new request replaces the earlier open one. Requests for different sections wait side by side.

On a draft site, these changes are saved straight away and don't need approval. Uploading or generating an image changes no page, so it doesn't need approval on a draft or a live site. An image named in a waiting request is kept safe from clean-up until you decide.

A new section that still contains sample text is refused on a live site until the real text is filled in.

Scheduling blog posts

When your AI schedules blog posts, it creates one approval request for the whole batch and gives you the approval id and a link. The Approvals list shows each post's title with its publish date and time, in your browser's timezone. Nothing is scheduled yet.

When you approve, cnvrtlocal checks each post again. Posts that still qualify are scheduled and publish by themselves at their time (cnvrtlocal checks every 5 minutes). Posts that no longer qualify are skipped. Ask your AI for get_approval_status to see which were skipped and why.

If you reject the request, nothing changes. To pull a scheduled post back, your AI can call unschedule_blog_post. That needs no approval.

On a draft site you can still schedule and approve, but the posts only appear publicly once the site is live.

Good to know

• Requests expire after 7 days. Ask again if one runs out.
• After approving a domain, you see the DNS records to add.
• Guests can't approve. You need a real account.
• You can check status any time. Ask your AI for list_approvals, or look at the Approvals page.