For agencies and owners who look after several sites: Clients gathers each client with all of their sites, what needs you on each one, their Brief & rules, and the people who can reach them. From a client you can start a new site for them, make one change across all of their sites at once, and give a teammate access to every one of their sites with a single grant.
Open Clients →Clients sits in the sidebar under Projects, with a count of how many clients you can see. Each client is a card: their initials, name, and website (or email), a blue "Needs you" count when something on their sites is waiting on you (it opens that client's Needs you list), and up to four of their sites with a small picture of the live homepage, the site's name, where it stands (Live, Live with the own domain not connected, Site is down, or Draft), and a blue number if that one site needs you. Clicking a site opens it; clicking the client's name or Open opens the client page. A client with two or more sites also shows "One change, all sites".
Three cards across the top are filters, not just numbers: "clients need you" narrows the list to clients with something waiting, "live sites" narrows to clients with at least one live site, and "sites in all" opens Projects. Below them, search matches the client's name, website, email, and the names and addresses of their sites. The Show menu filters to Needs you, Has a live site, Has a draft, or No sites yet, each with its count, and Sort puts clients that need you first (the default), A to Z, or most sites first. Whenever a filter or search is on, a bar says "Showing: …" with the number of matches and a "Show all" button that clears everything. Filters live in the address, so a filtered list can be bookmarked or shared with a teammate who has the same access.
Sites that aren't linked to any client are counted under the list with a link to Projects. Choose a client in a project's details to group it here.
Once you have two or more clients, a "Working on" menu appears under Clients in the sidebar. Pick a client and Home and Projects show only that client: their projects, and only the things that need you on their sites. A bar at the top says "Showing: <client> only" with Open client and "Show all clients". Choose "All clients" in the menu, or press Show all clients, to go back to everything. Picking a client from any other page takes you to Projects for that client.
The top shows the client's name, website, email, how many sites they have and how many are live, and what you can do for this client (you own it, you can edit their sites, or you're a reviewer). Two buttons: "One change, all N sites" (when they have two or more) and "New site for <client>", which opens the project planner with this client already picked. Reviewers don't see either button.
Needs you lists everything waiting on this client's sites, the same rows as Home (new requests, changes to make, client messages, builds that stopped, fixes waiting for the client, open questions), each with a button straight to the right place. Sites shows every site as a tile with its picture, where it stands (Live, Live with the own domain not connected, Site is down, or Draft), and its status line; "Open in Projects" shows the same sites on the Projects page.
Brief & rules is a summary of the client's Client File: each section that has entries (business facts, brand, rules, content guidelines, approved styles, decisions, notes, learned facts), how many entries it has, and the latest one. The AI reads all of it on every change to every one of this client's sites. "Open and edit Brief & rules" opens it in the Assistant on their first site.
People with access lists the client's owner, anyone with access to every one of the client's sites ("Every <client> site, including new ones"), and anyone added to individual sites (with the site names), each with a tag: Owner, Can edit, or Reviewer.
The client's owner (and aiKit admins) also see "Give someone every <client> site": type the email of their aiKit account, pick "Can edit and publish" or "Reviewer: view, comment, approve", and press Give access. That one grant covers every site the client has now and any site added later. Giving the same person a different role later replaces the old one, and Remove access takes it away from all of the client's sites at once (access someone was given on a single site stays until it's removed on that site). Nobody else can grant or remove access. The person needs their own aiKit account first; no email is sent, so tell them yourself.
A reviewer can open every site, read the requests, feedback, versions, Brief & rules and site plan, leave pins and replies (labeled Reviewer), and approve a finished fix or send it back. They can never start an AI edit, build, restore, change settings or Brief & rules, add people, or publish, and the site's client access code is never shown to them. aiKit checks this on its servers for every action, not just by hiding buttons.
Client link tokens, under People with access, is how much AI the client's own link can use each month. Their link is the access code behind Edit on the live site and the client chat: every change or answer they ask for there uses your account's tokens and also counts here. It shows what's left of the month's amount, a bar, and when it renews (the same day your own tokens renew).
Every client starts at 2,000 tokens a month. The client's owner (and aiKit admins) can type a new amount and press Save; 0 turns off AI changes from their link. A typical change uses 10 to 50 tokens. When it's used up, the client's chat says so and offers Ask the owner for more, which sends you a request. Your own team's edits, chats and builds never count here: they use your account's tokens only.
On a live site, every change the AI makes — a chat request, a pin or Quick edit fix, a Redesign, a restore, a multi-site run, or files sent from a connected tool — is saved as a draft. The site's files and a new version are saved, but the public site does not change. A purple bar appears on every tab of the project page: "N changes waiting · not on your live site yet", with Review and publish. The Assistant's chat says "Saved as a draft" under its reply with the same link.
The review screen (/home/projects/<project>/review) shows the live page next to the draft. "Side by side" puts both real pages next to each other, each scrollable; "Slider" lays a full-page picture of the draft over a picture of the live page so you can drag a handle across to see what moved (the arrow keys move it too). Computer, Tablet, and Phone switch the screen size, and Page switches between the pages that changed. Forms are switched off in the draft, so nothing you try there is sent to the business.
"What changed" lists every changed, new, or removed file in plain words ("Home page", "Site styles", "Image (img/hero.jpg)"); a changed page has a Compare link that switches the view to it. "Changes in this draft" lists each request that went into it, who asked, and when.
Automatic checks run before Publish turns on: the home page is still there; pictures, styles, and scripts the pages use exist; links between pages work; scripts are valid; forms on changed pages still send to the same place with the same required fields; no page lost most of its words (a warning only); and a real browser opens the changed pages of the draft and of the live site and reports any new error or file that didn't load. Only problems the draft added count: a link that was already broken on the live site is mentioned, never held against the draft. A failed check keeps Publish off. Press "Check every page" to open up to 12 pages of the site in the browser, not only the changed ones (useful for a chat widget on pages you did not change). The owner can tick "I looked at the failed checks and want to publish anyway"; builders can't.
Publish (people with edit rights: owners and builders) puts the draft on the live site, marks that version "Live now", and records who published and when on the version and in What shipped. Ask for changes adds another AI change to the same draft. Discard throws the draft away: the files go back to exactly what the live site shows, nothing is deployed, and the discarded versions stay in Versions. Show your client has Send proof: your client gets full-page pictures of the draft's pages on a computer and a phone to mark up, a private link to click through the draft, and Approve or Request changes (see the Customer Proofs guide, "Website proofs"). Their changes land in Feedback with the page and the spot; an approval never publishes. A preview link made before website proofs existed is shown there with Turn it off; it also stops working when you publish or discard. Reviewers can open the review screen and see everything but never publish.
Settings has "How changes go live": "Wait for Publish (recommended)", the default for every live site, or "Publish automatically", the old behavior where each change goes live as soon as the AI finishes. Only the owner can change it. Either way every publish is a version you can put back in one click from Versions. Sites that aren't live yet have nothing to protect, so their changes save straight to the files until Go live.
"One change, many sites" (from Clients, or "One change, all sites" on a client) opens a page listing your sites grouped by client. Each client has an "All of <client>" box that ticks every one of their sites in one click; you can also tick sites one by one, across clients. Started from a client, their sites are already ticked and listed first. Sites where you're a reviewer are shown as View only and can't be picked. A bar at the bottom counts the sites picked (one AI edit per site) and has Clear and "Describe the change".
"Describe the change" opens a dialog: write the change once and press Start. aiKit runs it on its own server, one site at a time, so closing the tab doesn't stop it, and you land on the run's page (/home/clients/run/<run>), which has a stable link and refreshes itself every few seconds while the run works. "Stop after this site" lets the current site finish and skips the rest. Your recent runs are listed at the top of the picking page, with how many are ready to publish or need a look.
On the run page every site is a card. A site whose change worked shows a small before and after (the live home page and the draft, side by side), what the AI said it did, and which files changed, with Publish, Review (the site's full review screen), Keep as a draft, and Discard. A site that didn't go through says why (out of tokens, nothing changed, another change was running on it, or the server restarted mid-change) with "Run it again" and a link into its editor. Four tiles at the top count All sites, Ready to publish, Published, and Need a look; each one filters the cards (the filter is in the address, so it can be shared) with a "Showing — Show all" bar to undo it.
"Publish all ready" publishes every site that is waiting, one after another, after the same automatic checks the review screen runs. A site whose checks fail, or where you no longer have edit rights, is held back and its card says why. Nothing on any site goes live without a Publish press, unless that site's owner turned on "Publish automatically".
Have a quicker, specific question instead? Check the FAQ.