Case Study · Technology, Professional services

Let Claude update your website through Kroy Publish, with approval before anything goes live.

Claude prepares a change set for the affected public pages. A person approves it, Kroy publishes the projection and the site rebuilds.

Example implementation A designed Kroy workflow showing how this can be set up. It is not a customer result.

The workflow

Watch this workflow run through Kroy.

  1. The request.

    “Kroy Publish”

  2. Who is asking.

    Kroy identifies the person in marketing and Claude acting for them, within the delegation they gave it.

  3. Only what the task needs.

    Kroy retrieves public content entities (services, integrations, articles) and draft Artifacts from Cloudflare and GitHub.

  4. Excluded by design.

    Internal and client content and Hosting and repository credentials never reach Claude. That boundary is Kroy’s, not an instruction to the AI.

  5. The proposed action.

    Permitted: create draft change set and request publication.

  6. What Kroy refuses.

    Refused: publish without approval and edit content outside the public Channel.

  7. A person decides.

    A person approves each change set before publication.

  8. State changes. Everything is recorded.

    The work is updated in Kroy, and every request — allowed or refused — is written to the audit trail.

Claude
Marketing
Kroy
Cloudflare
GitHub
✓ Create draft change set
✕ Publish without approval
! Approval
AUDIT · STATE

Retrieved

  • ✓Public content entities (services, inte…
  • ✓Draft Artifacts

Excluded

  • ✕Internal and client content
  • ✕Hosting and repository credentials
Claude
Marketing
Kroy
Cloudflare
GitHub
✓ Create draft change set
✕ Publish without approval
! Approval
AUDIT · STATE

Retrieved

  • ✓Public content entities (services, inte…
  • ✓Draft Artifacts

Excluded

  • ✕Internal and client content
  • ✕Hosting and repository credentials

What the AI can and cannot do

Data accessed

  • ✓ Public content entities (services, integrations, articles)
  • ✓ Draft Artifacts

Data excluded

  • ✕ Internal and client content
  • ✕ Hosting and repository credentials

Actions permitted

  • ✓ Create draft change set
  • ✓ Request publication

Actions refused

  • ✕ Publish without approval
  • ✕ Edit content outside the public Channel

Human approval required

  • A person approves each change set before publication

Business situation

A company keeps its website’s services, integration pages and articles in Kroy. It has just shipped a new capability, and several pages need updating.

Why existing tools alone are insufficient

An AI can write the copy, but giving it CMS or repository credentials lets it publish anything, anywhere, at any time. Copying and pasting AI output into a CMS by hand loses the link between the change and why it was made.

Systems involved

  • KroyDB — public content entities.
  • Kroy Publish — the public Channel.
  • A static website hosted on Cloudflare, built from the public projection.
  • A deployment hook that rebuilds the site.

Kroy architecture

Public content lives in Kroy as structured entities. The website fetches the public projection at build time. Claude acts through the Publish Blog Article and Deploy Website Skills. Publication requires approval.

Workflow

  1. A user asks Claude: “Update our Xero integration page to reflect the new capability.”
  2. Claude identifies the affected public entities.
  3. Claude creates a change set as a Draft Artifact.
  4. A person reviews and approves it.
  5. Claude requests publication. Kroy checks the user’s authority, the agent’s authority, content status, publication policy and approval.
  6. Kroy updates the public projection and calls the deployment hook.
  7. The website rebuilds and the pages update.

Agent permissions

Claude can read public content and create drafts. It can request, but not force, publication.

Human permissions

Only people with the Publisher role can approve a change set.

State changes

  • The entities move to a new published version.
  • The Artifact is marked Approved and linked to the release.

Audit outcome

Kroy records the draft, the approval, the publication and the deployment call.

Security considerations

  • Hosting and repository credentials stay with Kroy’s deployment Skill.
  • Only the public Channel is writable in this workflow.

Setup requirements

  • Public content modelled as Kroy entities.
  • A website that reads the public projection at build time.
  • A deployment hook configured as a Kroy Connector action.

Try this with your own systems.

Explore Kroy Publish