Approvals and autonomy

ThemeSpot drafts. You publish. Anything a visitor could see waits for your approval, every time.

What ThemeSpot does on its own

Drafts aren’t visible to the public, so ThemeSpot makes these straight away:

• Editing a page or blog post draft: copy, images, links and SEO fields
• Adding, removing, moving and restyling sections
• Creating new page and post drafts
• Adding rows to HubDB tables (the table still needs publishing before visitors see them)

Afterwards it tells you what changed and gives you a preview link.

What always waits for you

• Publishing a page or post
• Creating or changing a redirect
• Creating or changing a form
• Adding a blog author or tag
• Uploading a file
• Shrinking an image in the file manager, which changes every page that uses it
• Rebuilding a page draft from its template, which discards the current draft
• Deploying theme changes

How approval works

When a change needs you, ThemeSpot pauses and shows an approval card. The card is the preview: it shows exactly what will change. Accept it and the change goes ahead. Decline it and nothing happens, and ThemeSpot asks what you’d like instead.

Publishing several drafts at once takes one approval for the whole set, not one per page. For more than 10 items, the approval names the count so the scale is clear.

Can I switch approvals off?

No. By design, there’s no setting that lets ThemeSpot make live changes without asking.

Publishing yourself

You can also publish any draft ThemeSpot made straight from HubSpot’s page editor, as you normally would.

For agencies

Each client portal has its own approvals and its own history. Your team asks, and the client’s named approver decides.

Undoing a change

Every change is logged with its previous values. Ask ThemeSpot to put something back and it shows you what it will restore before it does.