Getting started / Overview

Overview

AgenticWebTeam gives your organisation its own AI web assistant — connected to your CMS, your code repository and your hosting, operated by your team in plain language, and governed by roles, approvals and a full audit log.

What you get

  • A private workspace at app.agenticwebteam.com where your team chats with the assistant. Conversations are saved and resumable, and every action the assistant takes is shown step by step.
  • Content editing through your CMS's official API — Sanity, Contentful, Webflow, WordPress, Drupal, Shopify, WooCommerce, BigCommerce and Adobe Commerce are supported. No migration; your CMS stays the source of truth. Self-hosted platforms have minimum versions (WordPress 5.6+, Drupal 8.7+, WooCommerce 3.5+, Magento 2) — see Connect your CMS.
  • Code changes via your repository on GitHub, GitLab or Bitbucket — styling, components and schema, committed to the branch you choose, with staging-first workflows.
  • Built-in skills — web research, stock photography, image generation and PDF documents — included on every workspace and metered by credits. No extra API keys to manage.
  • Governance — fine-grained roles (down to environment, path, page type and action), an approval workflow for publishing, and an audit trail of who changed what, where.

How it works

You connect your systems once, during a guided onboarding. From then on, your team asks for changes in plain language — the assistant reads the current state, makes the change through the official APIs, verifies the result and reports back. Drafts stay unpublished until someone with publish permission puts them live.

you › Update the FAQ page — clarify how monthly billing works, and add a question about VAT.

Behind the scenes every write is permission-checked against the requesting user's role, targeted at the environment they chose (production or staging), and logged.

Safety model

  • Credentials are never in chat. Tokens are entered in masked fields during setup, tested live against the provider before they're accepted, and stored encrypted (AES-256).
  • Live changes require publish permission. Users without it work in drafts and route changes through an approval request.
  • Nothing is silent. Every create, update, publish and delete lands in the audit log with the user, target and environment.
  • Deletes are confirmed. The assistant describes exactly what would be removed and waits for an explicit yes.

Where next

Quickstart →