Skip to main content
On a busy site, you may want a second pair of eyes on every change before it goes into Your site, the version you publish. Two rules in Branch settings do that: one makes each change wait for someone else’s approval, the other makes AI tools you connect from outside Hiveku send their changes for review instead of changing your site directly. Only an owner or admin can switch these rules on or off. Everyone else sees whether they’re on.

​
Switch the rules on

1

Open Manage branches

In the builder, click the branch menu at the top of the chat (it shows Your site), then Manage branches.
2

Open Branch settings

Click the settings button at the top right, next to New branch.
The settings button, outlined, between the refresh button and New branch

Branch settings

3

Switch on the rules you want

Each switch takes effect straight away, and a message confirms it.
  • Require an approval: a change goes into Your site only after someone other than the person who made it approves the latest version, and while nobody is asking for changes.
  • Require reviews for outside AI tools: AI tools you connect from outside Hiveku send their changes for review. Hiveku’s own AI and people editing in the builder aren’t affected.
Branch settings: Require an approval, On, and Require reviews for outside AI tools, On, both outlined; and Build before merging, Off

Both rules on

​
What changes for your team

Work happens on a branch, as usual: see Try a Change on a Branch First. When someone clicks Ask for a review, the review shows Needs an approval until a teammate opens it and clicks Approve. Merge stays waiting until then. If a reviewer asks for changes, the review waits for those too, and a new version needs a new approval.

​
Good to know

  • Working alone? Leave Require an approval off. Nobody can approve their own changes, so with only one person on the account nothing could go in.
  • Catch broken changes too. Build before merging builds each review together with Your site and sends it back if the build fails. Once it’s on, you can also run the site’s type check, lint and tests before merging.
  • Publishing is separate. Changes in Your site still reach the live site only when you publish them.