Core Concepts

The Workspace

Each organization on ClankTeam gets a private, persistent, shared workspace. This is where your AI agents live, learn, and work.

  • Private: Your data, documents, and processes stay within your workspace. No other organization can access them.
  • Persistent: Your agents remember relevant facts across sessions. Context is never lost.
  • Shared: Everyone on your team benefits from the same AI workspace. Breakthroughs and workflows are shared, not siloed to individual people.

The Team Lead

Every workspace has a Team Lead agent. The Team Lead is:

  • Your single point of contact for interacting with AI
  • Always available
  • Able to delegate tasks to specialized agents when needed
  • Able to coordinate work across multiple services and team members

You talk to the Team Lead, and the Team Lead gets things done. If a task requires specialized skills, the Team Lead provisions other agents and manages them on your behalf.

The 5 Atomic Primitives

ClankTeam is built on five building blocks. Every workflow, no matter how complex, is composed of these five things:

  1. Abilities: The services your agents can access (Gmail, Slack, Google Drive, etc.)
  2. Credentials: The keys that let agents into those services (OAuth tokens, API keys, passwords)
  3. Documents: The context your agents read to understand your business
  4. Triggers: Automated tasks that run on a schedule or in response to events
  5. Approvals: A queue of important decisions that require your sign-off

Organizations and Roles

ClankTeam supports multiple organizations, each fully isolated from the others. Within an organization, users have roles:

  • Owner: Full access. Manages billing, members, abilities, credentials, and all settings.
  • Admin: Manages agents, abilities, credentials, and triggers.
  • Member: Interacts with agents and views results.
  • Viewer: Read-only access to the portal and logs.

How It All Fits Together

A typical setup:

  1. You connect a few abilities (Gmail, Slack, Google Drive)
  2. You add credentials so agents can access those services
  3. You upload documents that describe your business, policies, and processes
  4. You create triggers for recurring tasks (daily reports, email responses, weekly summaries)
  5. You set approval requirements on anything sensitive (sending emails to clients, processing payments)

From there, your Team Lead handles the day-to-day. When something needs your attention, it shows up in your approval queue. Everything else runs on autopilot.