Core concepts

BridgeApp has a handful of core ideas. Once they click, the whole product makes sense, because every feature is built from the same small set of concepts. This page is the map; the rest of the docs are the territory.

Workspaces

A workspace is your team’s private home in BridgeApp. It holds your members, chats, tasks, documents, databases, automations, and agents — and it’s completely separate from every other workspace. People in another workspace can’t see anything in yours.

Note

Inside BridgeApp’s settings you’ll usually see this called your workspace. In some technical material it’s referred to as a company — same thing. It’s the boundary that keeps each team’s data private.

You can belong to more than one workspace (say, your own company and a client’s), and switch between them freely. Each one has its own members, billing, and data.

Learn more in Create your workspace.

People and participants

Everything in BridgeApp is done by a participant — and a participant isn’t always a human. There are a few kinds:

• Members — the people on your team, each with a role that controls what they can do.
• Guests — external people invited to a specific chat, without full access to your workspace.
• Agents — custom AI teammates you build. An agent can chat, be assigned tasks, and take actions, much like a person.
• Service accounts — non-human identities (think “bot tokens”) used by integrations and automations to act on their own.

This is a quietly powerful idea: because an agent or a service account is a participant too, you can assign a task to an AI exactly the way you’d assign it to a colleague.

See Roles & permissions and Agents.

The building blocks

Your day-to-day work happens in a few building blocks. Each is useful alone, but the magic is how they connect.

Building block	What it’s for	Start here
Chats	Real-time conversation: channels, DMs, threads, calls	Messaging
Tasks & projects	Planning and tracking work	Tasks
Pages	Collaborative documents and knowledge	Pages
Databases	Structured, typed tables of data	Databases
Flows & automations	Letting BridgeApp do repetitive work	Automation
Agents	AI teammates that act in your workspace	AI in BridgeApp

How it all connects

The building blocks aren’t islands. They’re designed to reference each other, so context follows your work instead of getting stranded in a single tool:

• A task can be assigned to a person or an agent. Same mechanism, whether the assignee is human or AI.
• A task can link to a page. Keep the spec, plan, or notes right next to the work they describe.
• A database can feed an automation. When a new record appears, a flow can react — create a task, send a message, call an external service.
• An automation can run a flow on a trigger. “When a high-priority task is created, notify the team and log it” — without anyone lifting a finger.
• The Bridge copilot can see across all of it. Because your messages, tasks, docs, and data live together, the AI’s answers are grounded in your real workspace.

Tip

A good way to internalize this: pick one real workflow your team does today — onboarding a client, shipping a feature, closing the books — and notice how it touches chats, tasks, pages, and data. In BridgeApp, those stop being separate tools and become one connected flow.

A note on roles

Within a workspace, what each person can do is governed by their role — a named bundle of permissions. BridgeApp ships with sensible roles like Admin and User, and admins can create custom roles to fit how your team works. Roles are the answer to “who’s allowed to do what” — see Roles & permissions.

Next steps

• Create your workspace — set up your team’s home.
• A tour of BridgeApp — see where each building block lives.
• Quickstart — put these ideas into practice.