AI Teammates
AI teammates are rolling out gradually. If you don't see them in your workspace yet, they're on the way — and every job a teammate can do can be built today as an Automation or run on demand with Ask Copera AI.
An AI teammate is a named agent that runs on its own schedule, under its own identity, doing a standing job for your workspace. Where Ask Copera AI works alongside you in a conversation and Automations fire on a trigger, a teammate is a persistent worker with a role — it shows up, does its job, and reports back, even when no one asked.
Think of the AI Playbook as the list of jobs you could hire a teammate for: a daily executive briefing, a stale-lead nudger, an onboarding buddy, a content manager. Each one can be an always-on teammate.
How teammates fit alongside the rest of Copera AI
| Works when | Best for | |
|---|---|---|
| Ask Copera AI | You're in a conversation | On-demand answers and actions you drive |
| Automations | A trigger fires | Deterministic, event-driven workflows |
| AI teammates | On their own schedule | Standing, recurring jobs that need judgment |
Many teams use all three: an automation handles the mechanical trigger-to-action steps, and a teammate owns the recurring, reason-about-it work — reading the week's activity, deciding what matters, and reporting it.
What a teammate can do
A teammate acts under its own identity, and you decide how much it can do:
- Read (on by default): workspace members, channels and direct messages, documents, and meeting notes.
- Write (opt-in, per teammate): create and update rows, create and update documents, build boards, tables, and columns, create channels, send direct messages, and post to channels.
What a teammate can't do
The boundaries are deliberate and are what make a standing agent safe to run:
- No deleting. A teammate never deletes your data.
- No sending outside your workspace. It can't email or message beyond Copera — outbound-to-the-world stays with automations and their connectors, where you can gate it behind approval.
- Never beyond its permissions. A teammate only sees and does what it's been granted, nothing more.
From recipe to teammate
Every recipe in the AI Playbook shows two things you can do today — build it as an automation, or ask Copera AI to do it — plus a note on running it as a standing teammate once the feature reaches your workspace. That's the path: prove the job as an automation, then hand it to a teammate to own.
Frequently Asked Questions
What is an AI teammate?
A named agent that runs on its own schedule, under its own identity, doing a standing job for your workspace — reading your data and doing recurring work between the times you talk to it. It's rolling out in early access.
How is it different from an automation?
An automation is a fixed flow that runs on a trigger. A teammate is a persistent worker with a role that reasons across your data and does a broader recurring job. They complement each other.
What can a teammate do, and what can't it?
It can read members, channels, docs, and meeting notes, and — when granted — create/update rows and docs, build boards/tables/columns, create channels, send DMs, and post to channels. It can't delete data or send anything outside your workspace, and it only acts within its permissions.
Related
- What You Can Build with Copera AI — the jobs you could hire a teammate for
- Ask Copera AI — the assistant that acts inside your conversation
- Automations — event-driven flows any teammate job can start as
- What Copera AI Can Do — the full capability reference
- Connectors — how outbound actions to other apps work