Glossary
Short definitions of the terms used in Stevin and in this manual, from Activity and approval to workspace.
Terms#
| Term | Meaning |
|---|---|
| Activity | The console page that lists tasks, their status and results, and the approvals waiting for you. See Tasks and activity |
| Admin | A role for people who configure the workspace: integrations, MCP servers, team skills, models, usage. See People and roles |
| Allowance | The credits a plan includes per billing period |
| Approval | A pause in which Stevin describes an action and waits for a person to approve or reject it. See Approvals |
| Automation | A trigger plus an instruction: Stevin runs the instruction on a schedule or when an event happens. See Automations |
| Background task | Work Stevin does without you waiting in the conversation; you are notified when it is done |
| Channel | A place where you talk to Stevin: Slack, Feishu or Lark, WhatsApp, the console, Live, the phone. See Channels |
| Chat identity | The link between your console account and you in the chat tool |
| Code execution | Stevin writing and running a short program to compute over data it has. See Code execution |
| Console | The web interface of your workspace |
| Credits | The unit usage is metered in. See Usage and plans |
| Customize | The console page with the Integrations, Skills and MCP tabs; also the section of this manual on configuring the workspace. See Customize |
| Directory | The list of people in your organization, synced from your chat tool |
| Integration | A connection to a chat tool, GitHub or a built-in capability. See Integrations |
| Library | The console page with transcripts, summaries and generated files. See Library |
| Live | A real-time voice conversation with Stevin in the browser. See Live voice |
| MCP | Model Context Protocol, an open standard for making a service usable by AI |
| MCP server | One outside service added through MCP, offering a set of tools. See MCP servers |
| Member | The role for people who use Stevin day to day |
| Owner | The role responsible for the workspace; the only one that can change roles and permissions by default |
| Permission | One thing a role may or may not do. See Permissions |
| Plan | Free, Pro or Max; decides the monthly credit allowance |
| Role | Owner, Admin, Member or Viewer |
| Scope | For data permissions, whose data a role reaches: no one, their own, or everyone |
| Skill | Instructions written for Stevin on how to do a kind of job. See Skills |
| Task | One piece of work Stevin does in the background |
| Tool | One action an integration or MCP server offers, such as "create an issue" |
| Tool review | An admin deciding, tool by tool, which tools of an MCP server Stevin may call |
| Trigger | What starts an automation: a schedule, a record change, a GitHub event or a webhook |
| Viewer | The role for people who only need to keep informed; cannot talk to Stevin by default |
| Webhook | An address another system calls to start an automation |
| Workspace | Your team's own Stevin: its people, connections, skills, settings and data |