SiteAdmin
Change your own website by asking for it.
Type what you want in plain English, attach a poster if you have one, and SiteAdmin makes the change. Every change goes through a full set of automatic checks before it goes live, and a record is kept.
See how a change goes live
A volunteer asks
Here's the poster for the Christmas Fair. Can you put it on the noticeboard until the day?
SiteAdmin reads the poster
Spots the date and time, and asks whether it should go on the calendar too
Every check runs
466 passed, and only the parts of the site this volunteer may change were touched
It's live, and recorded
A message comes back in the chat with a link to the public list of changes to your site
Example request. The steps and checks are the ones SiteAdmin really runs.
In short.
- You ask for a change in plain English, and attach a poster or photo if you have one.
- Every change is checked automatically before it goes live, and a record is kept.
- Each person can change only their own part of the site.
- If something breaks, we are told straight away, and a person approves every fix.
What it's like to use.
No page builder to learn and no password to forget.
Ask in your own words
"Change Sunday's service to 10.30", "add Jane as our new treasurer", "the Friday session is cancelled this week".
Attach a poster, photo or PDF
SiteAdmin looks at it and asks sensible questions. Hidden location details are removed from photos before anything is saved.
Only your part of the site
A calendar volunteer can change the calendar and nothing else. The computer checks that limit on every change. It doesn't rely on people remembering.
Told when it's done
A reply comes back in the chat once it's live, linking to the public list of changes to your site.
Show sign-in and team details
Sign in with an email link or a passkey
Enter your email and click the link we send, which works once and expires after 15 minutes. Or use a passkey: your fingerprint, face or screen lock, with no email to wait for. A passkey is optional, and the email link always works.
Your team, your rules
You decide who can change what, person by person. Tell us when a volunteer joins or leaves and we update it the same day.
Every change, every time
Four checks before any change goes live.
Every change is made as a separate draft, so nothing touches your live site until it has been checked. We keep a record of exactly what changed. A change goes live automatically only if it passes all four checks. If one fails, the change waits for a person to look at it, and we say why.
Is this person allowed?
SiteAdmin checks what this person is allowed to do every time, from our own list of your team. Nothing typed in the chat can change that. One person might only be able to update the calendar, another might be able to add events, and another might be trusted to change anything on the site.
The site's own checks
The full set of automatic checks that a web developer would run. They cover accessibility, security, content, and the software the site relies on.
Only the right parts of the site
Every page or file the change touches is checked against what this person is allowed to change.
Changes to how the site is built
Everyday changes, such as events, notices and wording, go live once they pass the earlier checks. Changes to how the site itself is built or published always come to us to review first, whatever a person's permission level.
Safeguards that work in the background.
Show the three safeguards
Daily limits
There is a limit on how much each person, and the whole site, can use in a day, so a mistake can't run up a bill.
Off-topic requests are turned down
If someone asks for something that isn't a website change, SiteAdmin politely says so and tells us. It does nothing with the request.
Problems are reported to us
If something breaks, we get an email with a first guess at the cause, often before you notice.
A person is in charge
When something breaks, we want to know first.
If something goes wrong, SiteAdmin tells us before you have to. An automated helper works out what broke and drafts a fix. A person then checks it before anything changes on your site.
Caught as it happens
Every error is noted the moment it happens. Whoever was using SiteAdmin still gets a friendly reply, not a broken screen.
We're told straight away
We're emailed straight away, with a first guess at the cause (clearly marked as a guess). If the same fault repeats, we get one grouped message, not a flood.
The problem is proved
An automated helper writes a check that fails because of the fault. That shows the problem is real before anyone tries to fix it.
A fix a person approves
The helper's fix has to pass that check and all the others. It can't publish its own work: a person approves every change.
A real example from September 2026.
A code review found a fault. If two changes finished at exactly the same moment, SiteAdmin's daily count could miss one. It was recorded as a problem. The automated helper then wrote a check that proved the fault and proposed a fix. We reviewed it and released it. The check stays in place so the fault can't quietly return.
And a daily report, whatever happens.
Every day a summary arrives covering errors, requests we turned down and how much SiteAdmin was used, even on quiet days. If an alert email ever went missing, the daily report would still show the problem.
Already in use.
SiteAdmin runs today on Kington Parishes, Kington Foodbank, orangebob.uk and Mr Wright's Rules. It comes with MediaWright hosting.
Prefer to just email us? That works too. SiteAdmin is there for when you'd rather not wait, not a replacement for talking to a person.
Ready to ask?
Tell us about your site and your team, and we'll show you how SiteAdmin would work for you.