Glossary

A friendly dictionary for BridgeApp. Skim the area you care about, or use your browser’s find (Ctrl/Cmd+F) to jump straight to a word. Each term links to the page where it’s explained in full.

Your workspace & people

• Workspace — Your team’s private home in BridgeApp, holding all your chats, tasks, pages, data, and members. Workspaces are completely separate from one another. (Internally it’s sometimes called a company.) See Create your workspace.
• Member — A person who belongs to your workspace. See Members.
• Role — A named bundle of permissions you assign to people. BridgeApp includes built-in roles (like Admin and User) and lets admins create custom ones. See Roles & permissions.
• Permission — A specific thing a role is allowed to do (invite users, manage billing, and so on). Permissions are enforced by the server, so they’re a real security boundary — not just a hidden button. See Roles & permissions.
• Guest — An external collaborator given limited access to specific workspace chats, or a temporary visitor allowed into a single call. See Invites & guests.
• Participant — The general word for any actor in BridgeApp: a person, an agent, a service account, or a guest.
• Service account — A non-human identity (like a bot token) used by automations and external integrations, authenticated by a token instead of a login. See Service accounts.

Messaging & calls

• Chat — Any conversation space: a channel, a direct message, or a group chat. See Chats, channels & DMs.
• Channel — A conversation organized around a topic, team, or project. Channels can be public (anyone in the workspace can join) or private (invite-only).
• Direct message (DM) — A private one-on-one conversation. A group chat is a DM with several people.
• Message — A single post in a chat: text, formatting, attachments, or all three. See Writing messages.
• Thread — A focused sub-conversation that hangs off one message, keeping side discussions out of the main flow. See Threads & replies.
• Mention — Tagging someone with @ to get their attention (and notify them). Mentioning an agent summons it to respond. See Mentions.
• Reaction — A quick emoji response to a message, using standard or custom workspace emoji. See Reactions & emoji.
• Draft — An unsent message BridgeApp saves for you automatically, so a half-written note is never lost. See Drafts.
• Pinned message — A message kept at the top of a chat for easy reference. See Pinned messages.
• Read state — BridgeApp’s private record of how far you’ve read in each chat, powering unread badges. You can mark things unread to follow up later. See Read state & unread.
• Call — A voice or video conversation, one-on-one or in a group, started from any chat. See Voice & video calls.
• SFU — The efficient relay server that powers group calls, so each person sends their video once and it’s shared with everyone. (You never interact with it directly.)
• TURN — A fallback that helps calls connect even through strict firewalls or networks.
• Recording — An optional saved copy of a call you can play back afterward.
• Transcript — An automatic text version of what was said on a call, available after it ends.

Tasks & projects

• Task — A unit of work: a feature, bug, idea, or to-do, with a title, status, assignees, and more. See Tasks.
• Project — A home for related tasks, plus the team and settings around them. See Projects.
• Task type — A template (Bug, Feature, Support…) that decides which custom fields a task has and, optionally, which workflow it follows. See Task types.
• Status — The state a task is in right now (Open, In Progress, Done…). See Workflows & statuses.
• Workflow — The set of statuses a task can have and the moves allowed between them. See Workflows & statuses.
• System field — A built-in field every task has: assignee, due date, priority, parent, subtasks, attachments, relations, and type. See Custom fields.
• Custom field — A field you define yourself (text, number, dropdown…) that appears only on tasks of a given type. See Custom fields.
• Subtask — A task nested under a parent task, used to break work into smaller pieces. See Relations & subtasks.
• Relation (dependency) — A typed link between two tasks (Blocks, Is Blocked By, Duplicates, Related To, Epic). Relations are mirrored automatically, so you create them once. See Relations & subtasks.
• Epic — A large body of work made up of related tasks; subtasks inherit their parent’s epic. See Relations & subtasks.
• Assignee — A person — or an AI agent — responsible for a task. A task can have several.
• Placement — A task’s position within a view; when you drag to reorder, you’re changing its placement. See Views.
• Version — A counter on each task that quietly prevents two people’s simultaneous edits from overwriting each other (optimistic locking). See Versions & milestones.
• Milestone — A named waypoint in a project’s timeline, like “Q3 Launch.” See Versions & milestones.
• Component — A named part of a project (API, Frontend…) you can attach tasks to. See Projects.
• Board — A kanban view where columns are statuses and you drag cards between them. See Views.
• Backlog — A queue of not-yet-started tasks, handy for planning. See Views.
• Saved view — A filter-and-sort combination you save and reuse. See Filters & saved views.

Pages & knowledge

• Page (doc) — A rich, collaborative document. Pages nest into a tree to form your knowledge base. See Pages overview.
• Block — A single piece of content in a page: a heading, list, table, code block, quote, image, and so on. You insert blocks with the ”/” menu. See The editor.
• Collaborative editing (CRDT) — The technology that lets everyone edit a page at once with no conflicts — like Google Docs, where two people can type at the same time and nothing collides. See Real-time collaboration.
• Page tree — The nested hierarchy of pages shown in the sidebar. See Organizing your knowledge.
• Breadcrumb — The path shown above a page (Parent › Child › This page) so you always know where you are.

Databases

• Database — A structured, strongly-typed table for the data that runs your business (leads, inventory, a backlog). See Databases overview.
• Attribute (field/column) — A typed column in a database, such as Text, Number, or Date. See Field types.
• Entry (record/row) — A single row of data in a database. See Tables & records.
• Field type — The kind of data a field holds: Text, Integer, Float, Boolean, Date, DateTime, Money, Enum, or Attachment. See Field types.
• Filter — A rule that narrows a database (or task list) to the rows you want to see. See Views & filters.
• View — A saved way of looking at your data; database views are an evolving area. See Views & filters.

Automation

• Automation — A rule that runs a flow when something happens or on a schedule. It’s a trigger plus a flow. See Automations.
• Trigger — The “when” of an automation: an event (Task Created, Comment Added…) or a schedule (daily, weekly, every N minutes). See Triggers.
• Launch — A durable record of one run of an automation, showing what happened and whether it succeeded — great for debugging. See Automations.
• Flow — A visual, step-by-step recipe you build on a canvas; the “what” an automation runs. See Flows.
• Node (block) — One step in a flow, like “Send Message” or “Create Task.” See Nodes, edges & pins.
• Edge — A connection between nodes that decides what runs next. See Nodes, edges & pins.
• Pin — A named input or output on a node that carries data between steps (mostly hidden from you). See Nodes, edges & pins.
• Pure node — An advanced kind of node that runs only when a later step needs its result.
• Context reference (template) — The {{ ctx.<node>.<field> }} syntax that pulls a value from an earlier step into a later one. See Nodes, edges & pins.

AI

• Bridge (copilot) — BridgeApp’s always-available AI assistant. Mention @Bridge in any conversation to get help. See Copilot.
• Agent — A custom AI teammate you build for a specific role, with its own prompt, knowledge, tools, and rules. See Agents.
• Tool (tool call) — An action an agent can take, whether a built-in BridgeApp action or an external system. A “tool call” is the agent asking to use one. See Tools & knowledge.
• Tool approval — The check that lets some actions run automatically while sensitive ones ask for your okay first. See Tools & knowledge.
• MCP (Model Context Protocol) — A standard “plug” for connecting outside tools and systems to an agent. See Tools & knowledge.
• Knowledge — Documents, pages, or database entries you connect to an agent so it understands your context. See Tools & knowledge.
• Skill — A reusable bundle of capability and instructions an agent can use, like “summarize meetings.” See Skills & rules.
• Rule — A conditional instruction that shapes an agent’s behavior in certain situations. See Skills & rules.
• Agentic step — One unit of an agent’s work — a model call or a tool run — shown so you can follow what it’s doing. See Agents at work.
• Compaction — BridgeApp automatically summarizing a long conversation so the AI stays focused; it happens behind the scenes.

Billing

• Plan — Your subscription tier: Free, Pro, or Enterprise. See Plans.
• Subscription — Your active plan plus its payment details. See Managing billing.
• Credits — Usage-based balance spent on AI features, billed alongside your plan. See Credits.

CRM

• Customer — A person or organization you do business with, tracked in the CRM. See Customers & contacts.
• Interaction — A logged communication or engagement with a customer (a call, email, or meeting). See Interactions.
• Campaign — An email marketing initiative sent to a list of contacts. See Campaigns.

Security & deployment

• Data residency — Control over where your data physically lives, which matters for many regulated industries. See Deployment & data residency.
• On-premises (on-prem) — Running BridgeApp on your own servers for full control. See Deployment & data residency.
• BYOK (Bring Your Own Keys) — Using your own encryption keys so you hold the ultimate control over your data. Available on Enterprise. See Privacy & encryption.

Related

• FAQ
• Core concepts
• What is BridgeApp?