Channels

One organisation. Different audiences.

  1. One Kroy node.

    Everything your organisation holds, governed in one place.

  2. Employees get their Channel.

    Approved policies, procedures, internal knowledge and employee Skills.

  3. Clients get theirs.

    Each client sees their own reports, requests and deadlines — and can respond.

  4. Partners and the public, too.

    Partners receive what the relationship needs. The public Channel carries services, articles and public Skills.

Kroy
Employees
Clients
Partners
Public

Employee projection

  • Policies
  • Procedures
  • !Client data

ABC projection

  • Reports
  • Requests
  • Internal notes

Public projection

  • Services
  • Articles
  • Clients
Kroy
Employees
Clients
Partners
Public

Employee projection

  • Policies
  • Procedures
  • !Client data

ABC projection

  • Reports
  • Requests
  • Internal notes

Public projection

  • Services
  • Articles
  • Clients
Routes branching from Kroy to employees, clients, partners and the public. One Kroy node.. Employees get their Channel.. Clients get theirs.. Partners and the public, too..

What a Channel combines

  • Audience — who receives it.
  • Projection — which portion of the data they may see.
  • Artifacts — which produced work is shared.
  • Events — which changes they are told about.
  • Skills — which actions they may request.

Example: a client Channel

ABC Client Channel
AudienceABC Limited
DataABC client projection
ArtifactsApproved accounts and reports
Eventsrequest.created · artifact.approved · deadline.changed
Skillsdocuments.upload · request.respond
AI accessAllowed
PublicNo

Types of Channel

Internal, Client, Partner, Supplier, Public, AI-only and Custom. An employee Channel might expose approved policies and procedures; a public Channel might expose services, locations, articles and public Skills.

Subscribe to what matters

Authorised people, systems and agents can subscribe to a Channel’s events. Don’t keep asking what changed. Subscribe to what matters.

Case Studies using Channels

Technology · Professional services

Letting AI update your website — with a person approving

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

ClaudeCloudflareGitHub

Professional services · Financial services

Preparing a board pack with AI, and sharing it with the board

Claude assembles a draft board pack from Xero, Salesforce and KroyDB. The finance director approves it, and it appears in the board Channel. Directors can query the approved pack with their own AI, but not the ledger behind it.

ClaudeChatGPTXeroSalesforce

Accountancy

A client uses their own Claude with the information you share

The client’s own Claude answers questions about outstanding records from the shared projection. A request for the firm’s internal notes is refused by Kroy.

Claude

Legal

A client document room with an expiry date

The buyer’s advisers can read, and ask their own AI about, the documents in the room until the expiry date. Anything outside the room, and any request after expiry, is refused.

ClaudeChatGPTSharePoint

Accountancy

Preparing a management accounts pack with Claude and Xero

Claude assembles the month’s figures and draft commentary as an Artifact. The manager approves it, and only then does it appear in the client’s workspace.

ClaudeXeroSharePoint

Technology

A private ERP Connector with a customer-facing order status Skill

A developer builds a private Kroy Connector for the ERP and a Check Order Status Skill. Staff AI and a customer’s own AI can both invoke it; each customer sees only their own orders.

Microsoft CopilotClaudeChatGPTPrivate ERP connector