What AI employees can and cannot do
Read an employee’s live capability map, understand its boundaries, and delegate only work the workspace can verify.
Recording coming soon
Use the complete written steps and transcript below in the meantime.
An AI employee is an asynchronous software worker. It can reason over authorized context, coordinate in text, and produce reviewable digital work. Its exact abilities depend on the workspace, the employee, and the accounts currently connected—not on what a model might know in general.
The three capability states
Open Tools → Capabilities, then select an employee.
- Can do now means Yodu found an active native action, tool grant, skill, company document, or teammate relationship for that employee.
- Available on request means the capability can be added, but is not currently usable. The owner must connect an account, grant access, provide a document, install a reviewed skill, or assign help.
- Cannot do independently is a hard boundary. For example, an AI employee cannot attend a live call as a person. It can prepare the agenda, draft questions, ask a human to attend, and turn the notes into tracked work.
Exact safe account labels appear in the map. Secret values never do. A disconnected or revoked account must not appear under Can do now.
Delegate an outcome, not an activity
Give the employee four things:
- the result to achieve
- the deadline
- the source material it may trust
- the evidence a reviewer will accept
Prefer work that remains inspectable: an email draft, research brief, document, image, spreadsheet, web page, updated CRM record, tracked reply, or source-backed metric observation. Sending, publishing, spending, deleting, and other consequential actions still follow workspace approval rules.
Safe verification
Refresh one employee’s capability map and inspect the source labels. Confirm that a current capability resolves to an active account or workspace record, and that no token, password, or private metadata is exposed.
If the employee says it completed work that the provider does not confirm, treat the claim as unverified and create a blocker.
Troubleshooting
- Missing connected tool: check both the workspace connection and the employee grant.
- Missing document: add or request the authoritative company document instead of pasting sensitive content into a chat.
- Wrong teammate: update the employee’s team relationship before assigning coordination work.
- Unclear limitation: ask for human input and describe the smallest action a person must perform.
Transcript
Open the capability map, select one employee, and read the page from left to right. “Can do now” is the only section that authorizes immediate delegation. “Available on request” is a catalog of resolvable gaps. “Cannot do independently” protects the company from invented actions. Choose one real outcome, verify the exact source, and assign the work with a deadline and acceptance evidence.
First workspace setup
A step-by-step checklist for configuring company context, model access, AI employees, tools, tasks, approvals, and recurring work.
Connect tools and request capabilities
Turn a blocked employee outcome into the smallest auditable access request, then verify it before work resumes.
