Glossary

This glossary defines every important term you will encounter in GOD CRM. Each entry includes a plai

This glossary defines every important term you will encounter in GOD CRM. Each entry includes a plain-English definition and a real-world analogy to help you remember it.

The terms are listed in alphabetical order. If you are reading the Start Here guide from beginning to end, you do not need to read this page top to bottom. Use it as a reference whenever you see a word you do not recognize.

A

Access Level -- One of the 6 permission tiers in GOD CRM: owner_owner (100), owner (80), admin (60), editor (40), viewer (20), and denied (0). The owner_owner level is automatic and permanent (assigned to the creator). Denied access always takes highest priority. Analogy: security clearance levels in a government building. Level 5 gets you into every room, Level 1 lets you into the lobby, and Level 0 means the door is locked for you.

ADR (Architecture Decision Record) -- A document that records a design decision, including the problem, the options considered, and the chosen solution. ADRs are numbered (ADR-001, ADR-002, etc.) and live in the project's documentation. Analogy: meeting minutes that explain why a rule was made, so people who were not in the room can understand the reasoning later.

Agent -- An autonomous AI worker that lives inside GOD CRM. Agents can answer questions, process data, generate content, and perform tasks on your behalf. They are configured per Project and can be shared between users. Analogy: a team member who works 24/7 and never takes a coffee break.

API (Application Programming Interface) -- The set of rules and endpoints that allow different parts of the system to talk to each other. The frontend sends HTTP requests to the backend API, which reads and writes data in the database. Analogy: a waiter in a restaurant. You (the frontend) tell the waiter what you want, the waiter brings your order to the kitchen (the backend), and the kitchen sends back your food (the data).

API v3 -- The current version of the GOD CRM API. Every response follows a standard format: { success: true, data: {...}, timestamp: "..." }. The v3 prefix appears in route paths like /api/v3/spaces. Analogy: a standardized shipping label. No matter what is in the box, the label always has the same fields in the same places, so the mail carrier knows exactly where to look.

Atom -- A reusable content block that can be shared between documents. When you update an Atom in one place, every document that uses it gets the update automatically. Analogy: a Lego brick you can snap into different builds. Change the brick and every build that uses it changes too.

Automation -- A rule that triggers one or more actions when a specific event happens. For example, "when a row's status changes to Done, send an email." Analogy: a domino chain -- push the first one and the rest follow automatically.

B

Barrel Export -- An index.ts file that re-exports everything from a directory, so other files can import from the folder path instead of individual files. For example, import { Button } from '@/components' instead of import { Button } from '@/components/Button/Button'. Analogy: a receptionist at the front desk. Instead of walking through the building to find each person, you ask the receptionist and they connect you.

Barrel File -- Same as Barrel Export. The two terms are interchangeable. Analogy: same as above -- the receptionist at the front desk.

C

Cell -- A single value at the intersection of a row and a column in a table. If your table has a row for "John" and a column for "Email," the cell is the box that holds "john@example.com." Analogy: one square on a spreadsheet.

Column -- A field definition in a table. Each column has a name (like "Email" or "Due Date"), a type (like Text, Number, or Date), and optional settings (like whether it is required). Columns define what kind of data a table can hold. Analogy: a label at the top of a spreadsheet column that tells you what goes underneath it.

Column Type -- The kind of data a column holds. GOD CRM supports 22 column types including text, number, date, select, multi-select, file, link, formula, lookup, relation, checkbox, rating, email, phone, URL, currency, percent, duration, people, created-time, modified-time, and auto-number. Analogy: the shape of a puzzle piece. A date column only accepts dates, just like a square hole only accepts a square peg.

Connection -- The database adapter abstraction layer in GOD CRM. The Connection module detects which database is available (PostgreSQL or SQLite) and provides a unified interface so the rest of the code does not need to know which database it is talking to. Analogy: a universal power adapter. Whether you plug into a US or European outlet, the adapter gives your device the same power.

CRUD -- Create, Read, Update, Delete. The four basic operations you can perform on any data record. Every table in GOD CRM supports full CRUD through the API and the user interface. Analogy: the four things you can do with a notebook entry -- write it, read it, change it, or erase it.

D

Dashboard -- A customizable page of widgets inside a Project. You arrange widgets on a dashboard to build a personal overview of your data. Dashboards are the Space homepage. Analogy: your phone's home screen, where you choose which widgets and shortcuts to display.

Data Source -- An external database connected to GOD CRM. Data Sources let you read and write data from databases that live outside of GOD CRM, such as MySQL, PostgreSQL, or other systems. Analogy: a USB drive plugged into your computer -- the data lives somewhere else, but you can access it from here.

Deploy -- The process of shipping code from the develop branch to main and then to the production server. In GOD CRM this includes building the frontend, copying files to the web server directory, and restarting the service. Analogy: packing boxes in a warehouse (building), loading them on a truck (pushing to main), and delivering them to the store (production server).

Document -- A rich text page with headings, sections, images, and formatted content. Documents live inside Projects and can contain Atoms (reusable blocks). Analogy: a Google Doc or a Word document that lives inside your project.

Documents Widget -- A wiki-like module for creating and managing pages with sections, atoms, import/export, and rich content editing. Documents support hierarchical structure with headings that define sections. Analogy: a notebook app like Notion, where each page can have sub-sections, reusable blocks, and linked content.

E

Error Boundary -- A React component that catches JavaScript errors during rendering and displays a fallback UI instead of crashing the entire page. Error Boundaries prevent one broken widget from taking down the whole dashboard. Analogy: a circuit breaker in your house. When one circuit overloads, the breaker trips and protects the rest of the house from losing power.

Express -- The backend web framework that GOD CRM runs on. Express handles HTTP requests, routing, middleware, and responses in the Node.js server. Analogy: the highway system that connects all the neighborhoods (routes) in a city. Every request travels the highway to reach its destination.

F

Filter -- A rule that shows only the rows matching certain conditions. For example, "show only rows where Status equals Active." Filters do not delete data; they just hide the rows that do not match. Analogy: a sieve that only lets certain grains through while keeping the rest in the bowl.

Formula -- A calculated column whose value is computed from other columns in the same row. For example, a "Total" column that multiplies "Price" by "Quantity." Analogy: a spreadsheet formula like =A1B1 that updates automatically when the inputs change.*

K

Kanban -- A Module (Layer 3) that displays rows as cards arranged in columns by a status or category field. You drag cards between columns to update their status. Analogy: sticky notes on a whiteboard, organized into columns like "To Do," "In Progress," and "Done."

L

Layer -- One of the four architectural levels in GOD CRM. Each layer builds on the one below it:

Analogy: the layers of a building -- foundation, structure, rooms, decorations.

Logger -- A structured logging utility that replaces console.log in both frontend and backend code. The Logger supports levels (debug, info, warn, error, silent) and is controlled by environment variables. Debug messages appear only in development; errors always appear. Analogy: a flight recorder (black box) on an airplane. It quietly records everything important so you can review it later if something goes wrong.

M

MindWorkflow -- The visual node pipeline builder inside the Labs module, similar to ComfyUI. You place nodes on an infinite canvas, connect them with edges, and build AI pipelines, media processing chains, or brainstorming boards. Not an automation tool -- it is a creative environment for visual pipeline design. Analogy: ComfyUI for CRM -- a visual canvas where you wire together AI models, media processors, and code blocks to build creative pipelines.

Module -- A full-page application that appears in the sidebar (Layer 3 in the architecture). Modules include Kanban, Calendar, Documents, Labs, and others. Clicking a Module in the sidebar opens it full-screen. Analogy: an app on your phone. You tap the icon, it opens, and you get the full experience.

O

Orchestrator -- A special agent that coordinates other agents. Instead of doing the work itself, the Orchestrator decides which agent should handle each part of a task and routes instructions to them. Analogy: a project manager who assigns tasks to team members and tracks their progress.

P

Parameterized Query -- A SQL query that uses placeholders ($1, $2 for PostgreSQL; ? for SQLite) instead of inserting values directly into the query string. This prevents SQL injection attacks where malicious input could damage the database. Analogy: a fill-in-the-blank form. The structure of the sentence is fixed; you just fill in the blanks. Nobody can rewrite the sentence itself.

Playwright -- An end-to-end testing framework used in GOD CRM to test the application in a real browser. Playwright simulates user actions like clicking buttons, filling forms, and navigating pages. Analogy: a robot that sits at a real computer, uses the mouse and keyboard just like a human, and checks that everything works correctly.

PostgreSQL -- The main relational database used by GOD CRM in development and production. PostgreSQL stores all Spaces, Projects, Tables, Rows, and system data. SQLite is available as an alternative for isolated testing. Analogy: a massive, well-organized filing cabinet with built-in security, indexing, and the ability to handle thousands of simultaneous readers and writers.

Preset -- A widget template that determines its appearance and behavior. GOD CRM includes 19 presets such as Number, Table, Calendar, Chart, Kanban, Timeline, Gallery, and others. When you create a widget, you pick a preset first. Analogy: a cookie cutter. The preset defines the shape; the data you connect is the dough.

Project -- A collection of tables, dashboards, documents, and modules that live inside a Space. Projects are the main unit of organization for actual work in GOD CRM. Analogy: a classroom in a school building. Each classroom has its own desks, whiteboard, and supplies.

R

Raw Table -- The hidden database storage layer (Layer 1). Raw Tables hold the actual data but are not directly visible to users. Universal Tables, Modules, and Widgets all read from Raw Tables. Analogy: a filing cabinet drawer. The data is in there, but you need to open a view (a Universal Table or Widget) to see it.

Row -- A single record in a table. If your table tracks people, each row is one person. If it tracks tasks, each row is one task. Rows contain the actual data values stored in Cells. Analogy: one line on a spreadsheet.

S

Slug -- A URL-friendly identifier made of lowercase letters, numbers, and dashes. Slugs are used in web addresses to create readable links. For example, "ADR-068" becomes "adr-068" as a slug. Analogy: a short nickname for a web page that looks clean in the browser address bar.

Space -- The top-level isolated workspace in GOD CRM. Each Space has its own users, settings, and data. Data in one Space is invisible to another Space. Analogy: a separate school building in a district. Each building runs independently with its own staff and students.

System Variables -- Special placeholders like {current_user_name}, {current_space_id}, and {current_date} that are automatically replaced with real values when content is rendered. Used in widget configurations, document templates, and agent prompts. Analogy: auto-fill fields on a form. Instead of writing your name every time, the form already knows who you are and fills it in.

T

Table -- A structured collection of rows and columns that stores data. Tables are the foundation of GOD CRM. Every widget, module, and view reads from a table. Analogy: a spreadsheet with labeled columns and numbered rows.

TanStack Query -- A data fetching and caching library used in the GOD CRM frontend. TanStack Query handles loading data from the API, caching responses, automatic refetching, and synchronizing server state with the UI. Analogy: a personal assistant who fetches documents for you, remembers where they are filed, and automatically grabs the latest version when it changes.

TDD (Test-Driven Development) -- A software development method where you write automated tests before writing the actual code. The cycle is: write a failing test (Red), write code to make it pass (Green), then clean up the code (Refactor). Analogy: writing the exam questions before teaching the lesson, so you know exactly what the students need to learn.

U

Universal Table -- The visible table view interface (Layer 2). While the Raw Table stores data behind the scenes, the Universal Table is what you actually see and interact with. It supports sorting, filtering, column reordering, and inline editing. Analogy: a notebook opened on your desk. The information came from the filing cabinet (Raw Table), but you are reading and writing in the notebook.

V

Vite -- The frontend build tool used by GOD CRM. Vite compiles TypeScript and React code, bundles it for production, and provides a fast development server with hot module replacement (instant updates as you code). Analogy: an assembly line in a factory. Raw materials (source code) go in one end, and a finished, packaged product (the built app) comes out the other end.

Vitest -- The JavaScript testing framework used in GOD CRM for unit and integration tests. Vitest runs test files, checks assertions, and reports which tests pass or fail. It is built on Vite for fast execution. Analogy: a quality inspector on the assembly line who checks every product against a list of requirements before it ships.

W

Widget -- A compact card that sits on a Dashboard and displays a summary of data (Layer 4). Widgets come in 19 preset types, from charts to task lists to Kanban boards. Unlike Modules, widgets share dashboard space and show overviews rather than full applications. Analogy: a home screen widget on your phone -- a small card that shows useful information without opening the full app.

Z

Zod -- A schema validation library used in GOD CRM to check that incoming data matches the expected shape and types. If a request body is supposed to have a string "name" and a number "age," Zod rejects the request if those fields are missing or wrong. Analogy: a bouncer at a club door who checks your ID. If your data does not match the rules, it does not get in.

Zustand -- A lightweight frontend state management library used in GOD CRM. Zustand stores keep UI state (like which modal is open, which filters are active, or which Space is selected) in a simple, predictable way. Analogy: a shared whiteboard in an office. Anyone on the team can read it or update it, and everyone sees the same information.

Quick Reference Table

For fast lookup, here are all 40 terms in a compact table:

How to Use This Glossary

• While reading the Start Here guide: If you encounter a term you do not recognize, jump here, find the entry, and jump back.
• While using GOD CRM: Keep this page bookmarked. The interface uses these terms in menus, settings, and tooltips.
• While talking to your team: Use these definitions to make sure everyone means the same thing. "Module" and "Widget" sound similar, but they refer to very different things in GOD CRM.

If a term is missing from this list, it probably has not been introduced in the Start Here guide yet. Check the full documentation or ask an Agent for help.