Glossary

The words you meet in OKiDO, in alphabetical order, each with a link to the article that covers it.

AI agent: An AI team member you can hand tasks to, within the permissions and budget you set. Agents report to @copilot and can be put to work on a project. See Create an AI agent.

Approval: A request to one or more people to approve a task. The task completes when everyone has approved. See Request an approval.

Board: The view of a project with a column for each stage of the work. See Switch between List, Board, Calendar and Gantt.

Capability: Something your agents can do, which @copilot builds and tests for you from a description in plain language. See Have @copilot build a capability.

Column rules: Fields that must be filled in before a task can be moved into a board column, and who may move tasks there. See Add rules to a column.

@copilot: Your organization's lead AI agent, set up for you automatically. Other agents report to it, and it builds capabilities. See Chat with AI.

Custom field: A field a label brings along, such as a client name or a budget, to fill in on every task with that label. See Add custom fields to a label.

Decision tree: A guided question flow in the Playbook that leads someone to the right answer or next step. See Build a decision tree.

Default labels: The labels every new task in a project starts with. See Give new tasks default labels.

Document: A wiki-style page in the Playbook, such as a guide or a policy, with versions and reviews. See Write a document.

Folder: A container in the Playbook that groups processes and other folders. See Organize the Playbook with folders and processes.

Inbox: Your list of notifications and requests: approvals, mentions, assignments and more. See Work through your inbox.

Milestone: A key point in a project with a target date, which tasks can belong to. OKiDO warns when the remaining work no longer fits. See Create a milestone.

Organization: Your company's workspace in OKiDO, with its own members, plan and data. You can belong to several. See Switch between organizations.

Owner, admin and member: The roles in an organization. Owners and admins manage the organization, its people, teams and labels; members do the work. See Change a member's role.

Playbook: Your organization's library of how work is done: folders, processes, documents, SOP templates, systems and decision trees. See Organize the Playbook with folders and processes.

Private project: A project only the people and teams you choose can see. See Control who can see a project.

Process: An entry in the Playbook for one way of working, such as client onboarding, that holds its SOPs and documents. See Organize the Playbook with folders and processes.

Project: A place for the tasks of one job, such as a client campaign or a website redesign, shown as a list, board, calendar or Gantt chart. See Create a project.

Request form: A form people fill in to ask a team for something. Each request becomes a task in a project. See Create a request form.

Run: A single time that an SOP is carried out, step by step, with its own people assigned to the steps and its own due date. See Start a run.

Smart Label: A label with a name, color and description that you put on tasks, documents and SOP templates. It can carry custom fields and belong to a category. See Create a Smart Label.

SOP: A standard operating procedure: a checklist of steps for a task you do again and again. You start a run from an SOP template. See Create an SOP template.

Sprint: A short, fixed period in which a team plans and finishes a set of tasks. See Plan a sprint.

Stage: A column on a project's board, such as a column for work in progress. See Set up board columns.

System: A flow in the Playbook that connects steps, SOPs and decisions with conditional logic, and runs them in order. See Build a system.

Team: A group of people in your organization, such as the creative team. Assign tasks to a team and give it access in one go. See Create a team.

Template project: A reusable project whose tasks have due dates relative to a start or launch date. See Reuse a project as a template.