KaziKazi

How can a small team share an AI agent without giving it access to everything?

Scope the agent's access by project, so the agent working on one client's job can only reach what that job needs. In Kazi a project holds members with the roles owner, admin and member, and the project's agent has its own access list, read or write per app. Each person also keeps their own Kazi.

Ken Wiltshire, founder of Kazi · Checked against the product on 2026-11-14

Why company-wide access is the wrong default

If one agent can reach every app the company has, every person who talks to it effectively can too. Your new hire asking for a client summary shouldn't be one prompt away from payroll.

How Kazi organizes team work

  • A project has an owner, a state and a deadline, and members with roles.
  • Chats, files, playbooks and subagents are shared into a project with view or edit access.
  • The project's agent has its own access list. A connection marked read-only for that agent stays read-only, whatever the person asking can do elsewhere.
  • Every person keeps their own assistant, on the web and on their phone.

One owner or a team of twenty, it's the same product. There's no team plan to upgrade to.