Glossary

The terms you'll meet across Boost.space, in one place.

Action — What an automation does when it fires: a notification, an email, a webhook, or your own code. See Actions and triggers.

Admin — A system role with full access: manage all levels, users, and settings; create fields and modules; configure automations.

Agent Chat — The agent chat built into the app (the Agent button in the sidebar): ask questions, work with records, and build automations in plain language. See Agent Chat.

AI agent — An external AI assistant (Claude, ChatGPT, Cursor, and others) connected to your data over MCP. It can read and write your records within the connecting user's permissions.

AI credits — The allowance that powers Boost.space's AI features and the Agent Chat. See AI credits.

AI field — A field whose value is generated or enriched by AI. See AI fields.

AI mapping — Automatically analyzes incoming data during import and maps it to the right fields, recognizing the structure and suggesting new fields when needed.

API token — A secure code that authenticates a user with the REST API and integrations. It can never have more rights than the user it belongs to. See API tokens and MCP tokens.

API token prioritization — Priorities set on API tokens that decide which source wins during data consolidation.

Automation — Keeping data current automatically: native actions and triggers, your own code automations in a secure sandbox, and scenarios on your connected Make.com account.

Basic fields — The system fields present on every record: ID, Space, Status, Labels, Created time, Created by user, and Remote ID. Everything else is a field you define. See Fields.

Boost.space system — The platform that centralizes and synchronizes your company data from internal and external sources. Also called your system instance. See System instance.

Category — A group of people, used the same places a team is: space access, menu visibility, segment visibility. Every new user joins Everyone by default.

Code automation — An automation step that runs your Python in a secure, isolated sandbox — written by you, your LLM, or the Agent Chat. See Code automations.

Connection — Authenticated access to an external app, used by Make.com scenarios to read and write that app's data.

Custom branding — Personalize the system's appearance: logos, login-screen backgrounds, favicons, and colors. See Company design settings.

Data consolidation — Merging data from multiple sources into one record, using the key field to match and API token prioritization to decide which source wins. See API token prioritization + data consolidation.

Field — A typed attribute on a record (text, number, date, a relational link, a computed value). Fields were formerly called custom fields. See Fields.

Field group — A named collection of fields. Every field belongs to at least one group, and a field can be shared across several groups. See Field groups.

Formula field — A field that computes its value from other fields. See Formula fields.

Key field — The field that identifies records in a space for merging. Essential for data consolidation — e.g. setting email as the key means incoming data with the same email updates the existing record instead of creating a duplicate. See Key fields.

Label — A tag added to records to categorize and organize them. See Record labels.

Licence — Enables access to certain features and plan tiers. See Plans, tiers and usage limits.

Linked record — A field that links a record to one or more records in another module — the basis for relationships and lookups. See Linked records.

Lookup — A read-only field that pulls a value from a linked record, so related data appears without being duplicated.

Manager — A space role that can manage members and other managers, manage records, and change space settings such as statuses and labels. See Space roles.

MCP (Model Context Protocol) — The open standard that lets an AI agent read, write, and query your data in natural language. See Connect via MCP.

Member — A space role that can view and manage records using existing statuses and labels, but cannot manage members or change space settings. See Space roles.

Menu editor — Customize the system's navigation: menus, folders, shortcuts, and embedded content, tailored per user. See Menu editor.

Module — A type of data in your system — a table in your database. Modules hold spaces and records; you create the modules your business needs, each with its own structure.

Multicurrency database — Modules that work with currencies can store exchange rates and recalculate prices automatically.

Multilingual database — Store your data in multiple languages.

Owner — A space role with full control: manage members, managers, and owners; manage records; edit space settings; and delete the space. See Space roles.

Record — A single data entry in a module — a row in the table (a company, a deal, a ticket). See Records.

Remote ID — The identifier a record carries from the external system it came from, used to match and update the right record on re-sync (upsert). See Remote IDs.

Rollup — A field that aggregates a value across linked records — a sum, count, minimum or maximum — and keeps it current. See Rollup fields.

Sandbox environment — A copy of your system instance for risk-free testing. Regenerate it any time to match your main instance. See Sandbox environment.

Scenario — A visual automation (a trigger plus steps that move and transform data) that runs on your connected Make.com account against your Boost.space data. See Views.

SDK — A typed client for the REST API, so you write Boost.space calls in your own language instead of assembling HTTP by hand. See SDK.

Segment — A saved filter over a module that shows only the matching records. Used both as a standing queue of work to do and as a throwaway view for a one-off job; records leave a segment on their own once they stop matching. See Segmenter.

Space — A container within a module that groups records (e.g. EU pipeline and US pipeline inside a Deals module). Access is restricted to users who created it or were granted access. See Spaces.

Status — An indicator assigned to a record to represent its state or progress — system-defined (e.g. Active, Done) or custom. See Record statuses.

System instance — A distinct environment for a team or organization: all its users, modules, spaces, records, and configuration. Every customer gets their own, on their own domain. See System instance.

System key — A unique identifier for your Boost.space system, used for secure connections across integrations. See System name and system key.

System roles — The two roles: Admin (full permissions) and User (acts within permissions granted by an admin). See System roles.

System settings — The admin-only settings (fields, actions and triggers, design, and more). See System settings.

Team — A named group of people. A team can be granted a space role, so everyone in it inherits that access — the maintainable way to run permissions, because you change the team rather than every space. Managed in Settings → Teams; which spaces a team reaches is set from each space. See Inviting users and setting up teams.

Trigger — What starts an automation: a record being created, updated or deleted, or a schedule. See Actions and triggers.

User — Uses the system within the rights an admin assigns, usually inherited through team membership. See System roles.

Vector database — Turns the text in a space's records into embeddings so agents and search can match records by meaning rather than exact words. See Vector database.

Webhook — A way for an app to send real-time data to a URL in response to an event. As an automation action, Boost.space calls a URL you choose when a record changes, and the payload can carry dynamic values from that record.