Glossary

Reference

Glossary

Plain definitions of the words Volobox uses, from Workbench and approval cards to personal access tokens, webhooks and preview manifests.

Short definitions of the terms used across Volobox and this documentation. Each term is the name the product itself uses, so the same word means the same thing on the website, in these docs and inside Volobox. The API, MCP and file-format terms are under Developers.

Workspace

  • Workbench tab: a browser-style tab at the top of Volobox. Each screen you open, such as a project, a docs page or a chat, opens in one, so several can stay open at once.
  • Side panel: the panels on the left and right of the Workbench, holding Agenda, Notes, Inbox, Agent Chats, Chats, Team, Coding and Calls. They stay open while you switch tabs.
  • Spotlight: the search and jump bar (Ctrl+K or Cmd+K). It finds pages, people, work items, docs, files, meetings and chat messages, and shows only what you are allowed to open.
  • Home: your personal page after sign-in, with today's plan, what needs you, your work in progress and what your agents are doing.
  • Inbox: one queue of everything that waits for an action from you, including assignments, invitations and approval cards.
  • Agenda: the side panel with your days ahead: meetings, your own agenda items, calendar events and reminders.
  • Quick Notes: private scratch tabs for short personal text, saved as you type.
  • Screen sharing mode: a switch that hides personal and sensitive content, such as private chats, customer details and AI costs, while others can see your screen.
  • Your status: where you are right now (Focus, Lunch, Break, Commuting or Away), shown to colleagues for a time you choose.
  • Do Not Disturb: silences sounds and push notifications for a period, while messages still arrive quietly.
  • Alert: a condition that holds now and needs someone's attention, such as an insight crossing a threshold. It resolves itself when the condition clears.

Work

  • Project: the container for a team's work: tasks, requests, members, the project chat and, where coding is on, linked repositories.
  • Task: a piece of deliverable work in a project, with a state, an assignee (a person or an agent) and its own discussion.
  • Request: an intake item for new work, a bug or an idea. Tasks handle requests, and a request closes when its work is done.
  • Story: how a piece of work travelled, from a ticket or request to tasks, workflow runs, coding sessions, pull requests and reviews. It is built from recorded activity, not written by AI.
  • Insight: a saved question over the workspace's data that draws its own chart, without an AI model on each refresh.
  • Dashboard: a grid of insights, either personal (and shareable read only) or belonging to a project.
  • App: a small application built inside Volobox, with its own data, roles, rules and screens.
  • Builder: where an app is built: you describe the app to a coding agent and watch a live preview beside the chat, then publish.

Collaboration

  • Work thread: a chat tied to a task, request, project or other piece of work.
  • Reply thread: the replies to one chat message, kept out of the main chat. A team agent you mention answers there.
  • Volobox Call: Volobox's own voice, video and screen sharing. A call can start from any chat, with no meeting behind it.
  • Meeting: people coming together on a subject, usually planned on the calendar. A meeting may be held on Volobox Call, on another provider or in person.
  • Call notes: a call's summary, decisions, action items and open questions, made from what was said. Calls are transcribed, not recorded: no audio is kept.
  • Docs: wiki spaces with pages, sheets and folders: your own personal space, and shared spaces for teams.
  • Connected files: your Google Drive, OneDrive and SharePoint files shown in Volobox, read only. Volobox never stores their contents and never changes them.
  • Shared mailbox: one team email address, such as sales@, answered together in Mail, with one owner for each thread.

Agents and governance

  • Agent: an AI team member with skills and permissions. It can answer questions, take tasks and propose changes.
  • Personal assistant: a private agent every person gets automatically, working only within that person's own permissions.
  • Team agent: a shared agent created by administrators, with its own handle that people mention in chat and assign work to.
  • Ask mode / Agent mode: in Ask mode an agent only reads and answers; in Agent mode it proposes changes for you to approve. Plan mode sits between: the agent writes a plan, and nothing changes until you run it.
  • Approval card: the card an agent shows before a change. It names what will happen, and nothing runs until a person approves it.
  • Standing rule: a rule you own that lets matching agent actions run without a card. It can expire and carry a budget, and it never covers a reply to a customer.
  • Authorization mode: how far a shared agent may act: within the asking person's permissions, by escalating to its manager, or within its own memberships under hard safety limits.
  • Skill: a bundle of tools and instructions that lets an agent work in one area, such as projects, meetings or support. Skills can be imported and exported as SKILL.md files or zip bundles, and an imported skill grants no permissions by itself.
  • Library pack: a bundle of ready-made agents, skills and commands that an administrator chooses to install.
  • Library pack registry: an HTTPS address that serves an index.json and zip bundles of packs. An administrator adds it to the Library, and its packs can then be installed there.
  • Channel agent: a workflow that watches one chat and acts on new messages without being mentioned.
  • Learned note: a convention or decision approved for one project or one shared agent, read by agents working there.
  • Audit log: the organization-wide history of agent actions, work changes, configuration and security events, filterable and exportable by administrators.

Coding and automation

  • Coding session: a room where a coding agent and the team work on a branch inside a sandbox, with the chat, diffs, terminal and preview in view.
  • Sandbox: an isolated computer where agent tools, a coding session or a branch preview run: in the cloud, or on a person's own machine.
  • Branch preview: a running copy of an app built from a Git branch, so people can try a change before it merges.
  • Preview manifest: the file in a repository, volobox.app.yaml, that tells Volobox how to run its app for a branch preview. A repository with more than one app adds volobox.workspace.yaml.
  • Verify step: a build, test or lint command listed under verify in the preview manifest. An agent's change must pass it before Volobox opens the pull request for agent work on a task.
  • AI review: an agent's reading of a pull request, with findings on the diff. It is advice: it never approves, requests changes or blocks a merge.
  • Workflow: a process agents run, written as a playbook or as code, started by hand, on a schedule or by an event.
  • Playbook: a workflow written in plain Markdown that an agent reads and carries out, asking questions when it needs to.
  • Code body: a workflow written as JavaScript that Volobox runs on the server, for a process that must take the same path every time. The model is a step it calls on purpose. A playbook can be converted to a code body once, never back.

Developers

  • Action group: a named set of public API actions, such as support or calendar. A token, a sign-in or an integration app reaches only the groups it was given.
  • Personal access token: a token a person creates in their own settings, with the action groups it may use and when it expires, so a script or agent can act as them. Volobox calls it a personal token. It is shown once, and revoking it ends it at once.
  • Integration app: an OAuth application an administrator registers so something outside Volobox can call the API or the MCP server. People sign in through it, or it runs as a service with a client secret. It is not an app built in the Builder.
  • MCP server: a server that offers tools to AI agents over the Model Context Protocol. Volobox hosts one that external agents connect to, and administrators can connect external MCP servers for Volobox's own agents.
  • Webhook: an address outside Volobox that receives a signed HTTPS POST when an event it chose happens. It carries ids and labels, not message bodies.
  • Event: something that happened in the workspace, such as a task closed or a pull request merged. Events can start workflows, and webhooks send the ones that may leave the workspace.

Support and clients

  • Support desk: the unit of support. It owns its tickets, the people who answer them and the clients it serves.
  • Ticket: one customer conversation about one problem, with a reference such as SUP-14 the customer can quote.
  • Internal note: a message for your own team on a ticket, client channel or mail thread. It is never sent to the customer.
  • Client: a company outside your own that you work with. Everyone you invite from outside belongs to one.
  • Portal: the separate area where customers and external collaborators sign in. It is the only part of Volobox their accounts reach.