Glossary

The words the workspace uses

What each term means here, in the help, the guides and the workspace itself.

TermsCopy link to this section

Bot
The name the workspace uses for one AI coworker, in its menus and settings. A Bot and a coworker are the same thing.
Coworker
An AI that works beside your team. You give it instructions, a model, and the skills and connectors it may use, then write to it the way you would to a colleague. It asks when something is unclear, and waits for an approval before consequential actions.
Computer
A coworker's private browser, with its own files and a shell. You can watch its screen live, take the mouse and keyboard, and hand it back. You type passwords yourself through a private form, and password fields are hidden from everything the coworker reads back.
Routine
An instruction and a schedule. At each due time the coworker carries out the instruction, and every run is kept in the routine's history. A routine runs at most once every 15 minutes. See Routines and responsibilities.
Responsibility
A lasting goal for one coworker, with an instruction, the criteria for success and the events it cares about. It runs when one of those events arrives rather than on a clock, and stays active until it is paused or completed.
Skill
Written know-how for a kind of task, such as how your team writes a report. A coworker uses only the skills granted to it, and skills can be imported and exported as packs.
Approval
A consequential action that waits on the Approvals page for a person to decide. You choose how much each coworker may do without asking; sending, paying and deleting always ask. An approval nobody answers goes to a backup approver and is refused after 24 hours by default.
Boundary
A rule an administrator writes that every browser, file, shell and connector action is checked against before it happens. Deny rules win over allow rules, a missing policy permits nothing, and a broken rule refuses. Every change is versioned and can be restored.
Snapshot
A saved copy you can go back to. The workspace's database is backed up as snapshots automatically, and an administrator can restore a kept one from the operations page; see Backup and restore. A Bot's computer keeps its own snapshots of its files, saved and restored from its Files section. Either kind saves the current state first, so a restore can be undone.

Where to go nextCopy link to this section

The help center walks through each part of the workspace, and the FAQ answers what teams ask before they start.

Last updated