This glossary defines Vibework's main customer-facing concepts in plain language. Use the stable section links when sharing a specific definition, or download this article as a PDF for training and reference.

Vibework

The business AI platform that brings chat, company knowledge, agents, integrations, tasks, and repeatable workflows together under organization access and governance controls.

Vibey

Vibework's conversational assistant—the place a user asks for work, supplies context, reviews results, and uses approved agents and tools.

Organization

A customer's isolated Vibework environment containing its people, access rules, content, connections, agents, projects, and workflows.

User

A person with an identity and membership in a Vibework organization.

Role

A named set of responsibilities used to grant a class of access, such as organization administrator.

Permission

A specific allowed action, such as reading files, managing users, or publishing an agent. Roles can grant permissions.

Team

A reusable group of people used to assign work or share supported resources.

Platform administrator

Authorized Vibework staff who manage platform-wide configuration. This is different from an administrator inside one customer organization.

Organization administrator

A customer-side administrator who manages allowed settings, people, teams, connections, agents, and governance for their own organization.

Chat / conversation

A sequence of messages and results between a user and Vibey or a selected agent.

Message

One user request, assistant response, status update, or tool or result event inside a conversation.

AI model

The underlying language or reasoning model used for a response or step. Administrators control which models are available.

Prompt

Instructions and context given to an AI model for one request or behavior.

Saved prompt

Reusable prompt text stored in Vibework so approved users can apply the same instruction again.

Agent

An AI worker with a defined purpose, instructions, approved model, knowledge, and tools. An agent can make bounded decisions while working toward a result.

Organization agent

An agent configured for and shared within one customer organization.

Tool

An approved operation an agent can call, such as searching a knowledge base, reading a connected system, or creating a result.

Integration

A catalog definition that tells Vibework how an external application or service can be connected and what operations it offers.

Connection

An organization's configured, authorized instance of an integration. A connection holds or references credentials and access settings; users do not receive the credential itself.

Function

A reusable business operation with defined inputs, outputs, access rules, and implementation that an agent or workflow can invoke.

Catalog

A browsable inventory of approved capabilities or reusable resources, such as services, integrations, functions, or other platform-managed items.

My Files

The user's managed file area for content they upload or save in Vibework. Access still follows organization and sharing rules.

Knowledge Base

A curated set of documents and instructions that Vibework indexes so an approved assistant or agent can retrieve relevant company context.

Project

A durable place to organize related work, context, files, knowledge, an agent, and tasks around an outcome.

Task

A trackable unit of work with status, ownership or assignment, and related context.

Workflow

A reusable, ordered process that collects inputs and runs defined steps to produce a repeatable result.

Workflow step

One unit of work inside a workflow, such as collecting a file, asking an agent, running an operation, waiting for review, or presenting output.

Step type

The step's behavior and configuration contract—for example input, AI processing, code or function execution, review, or completion. Exact available types depend on the workflow builder.

Workflow run

One execution of a workflow with its own inputs, step status, outputs, timestamps, and history. The workflow is the reusable definition; a run is one occurrence.

Input

Data supplied to a chat, agent, function, workflow, or step before it runs.

Output

Data or files produced by an agent, function, workflow, or step. An output can become a later step's input.

Variable / data mapping

A named reference that passes a value from an earlier input or output into a later workflow step.

Generated file / deliverable

A document, spreadsheet, PDF, image, or other file created as a result of work in Vibework and made available to preview, save, or download.

Human in the loop

A deliberate pause where a person supplies information, reviews work, or decides whether execution may continue.

Approval

A recorded human decision that allows, rejects, or returns a proposed action or workflow step.

Governance

The access rules, policies, approvals, monitoring, and records that control how AI and automation may use data and take actions.

Guardrail

A specific rule or check that limits, blocks, flags, or requires review of an action.

Sharing / access rule

A record of who may read, use, edit, or administer a resource, such as a person, team, or the organization.

Dataset

A structured, reusable collection of records that approved agents, functions, workflows, or dashboards can use. Availability may be limited to specific organizations or administrators.

Dashboard

A saved visual view of metrics, results, or structured data.

Usage

Measured consumption of platform capabilities, including model or service activity, used for visibility, budgets, and billing where applicable.