Spaces and Projects

In this chapter you will learn how GOD CRM organizes everything into two layers: **Spaces** and **Pr

In this chapter you will learn how GOD CRM organizes everything into two layers: Spaces and Projects. If you understand these two ideas, the rest of the system will make sense.

The School Building Analogy

Think of a real school district. The district runs several school buildings. Each building has its own principal, its own teachers, its own students, and its own classrooms. A student in School A cannot walk into a classroom in School B without permission.

GOD CRM works the same way:

  • A Space is like a school building. It is a completely isolated workspace with its own users, settings, and data.
  • A Project is like a classroom inside that building. It holds the actual work: tables, dashboards, and modules.

What Is a Space?

A Space is the top-level container in GOD CRM. When you create a Space, you get a private area that is fully separated from every other Space in the system.

Key facts about Spaces:

  • Isolation. Data in one Space is invisible to another Space. If you run two businesses, you can put each one in its own Space and they will never mix.
  • Members. Each Space has its own list of users. You invite people into a Space, and they can only see what is inside that Space.
  • Settings. Each Space can have its own integrations, AI agent configurations, and preferences.

When to create a new Space

  • You are starting a separate business or team that should not share data with your existing work.
  • You want a sandbox environment to experiment without affecting real data.
  • You are managing work for a client and need to keep their data private.

What Is a Project?

A Project lives inside a Space. It groups together everything related to one area of work: tables, dashboards, widgets, documents, and modules.

Key facts about Projects:

  • Organization. A Project is how you keep related things together. Instead of dumping all your tables into one big list, you put "Sales" tables in a "Sales" project and "Marketing" tables in a "Marketing" project.
  • Dashboards. Each Project can have its own dashboard with widgets that show summaries, charts, and key numbers from the tables inside that Project.
  • Modules. Projects can include specialized modules like Documents, Workflows, or AI Agents that operate on the data within that Project.

The Hierarchy

Here is the full hierarchy from top to bottom:

Space (the school building)
  |
  +-- Project A (a classroom)
  |     |
  |     +-- Tables
  |     +-- Dashboards
  |     +-- Documents
  |     +-- Widgets
  |     +-- Modules (Workflows, Agents, etc.)
  |
  +-- Project B (another classroom)
  |     |
  |     +-- Tables
  |     +-- Dashboards
  |     +-- Documents
  |     +-- Widgets
  |     +-- Modules
  |
  +-- Project C ...

Everything in GOD CRM lives somewhere inside this tree. If you know which Space and which Project you are in, you always know where your data is.

A Real-World Example

Imagine you run a small company called Acme Corp. You create one Space called "Acme Corp" and set up three Projects inside it:

Space: Acme Corp
  |
  +-- Project: Sales
  |     +-- Table: Leads
  |     +-- Table: Deals
  |     +-- Dashboard: Sales Pipeline
  |
  +-- Project: Marketing
  |     +-- Table: Campaigns
  |     +-- Table: Content Calendar
  |     +-- Dashboard: Campaign Performance
  |
  +-- Project: Support
        +-- Table: Tickets
        +-- Table: FAQ Articles
        +-- Dashboard: Support Metrics

Each Project has its own tables and dashboards. The Sales team works in the Sales project. The Marketing team works in the Marketing project. They are all inside the same Space, so they share the same member list and settings, but their work is organized into separate containers.

Now imagine you also do freelance consulting on the side. You would create a second Space called "Freelance" so that your personal client data never appears alongside Acme Corp data:

Space: Acme Corp          Space: Freelance
  +-- Sales                 +-- Client Projects
  +-- Marketing             +-- Invoicing
  +-- Support

Two Spaces, completely separate, both managed from one GOD CRM account.

Users and Permissions

Six Access Levels

GOD CRM uses 6 access levels that can be applied at every level of the hierarchy -- from an entire Space down to an individual column:

Access Level Value What it means
Owner_Owner 100 Creator of entity. Automatic and permanent -- cannot be transferred or removed
Owner 80 Full control: can delete the Space, manage everything
Admin 60 Administrative access: manage members, settings, tables
Editor 40 Read and write: create, edit, and delete rows
Viewer 20 Read-only: can see data but cannot change anything
Denied 0 Explicitly blocked: cannot see or access the resource. Denied always wins

The person who creates a Space gets the Owner_Owner level automatically. Three default roles (admin, editor, viewer) are created automatically in every Space. You can also create unlimited custom roles that combine these access levels at any granularity. Role aliases: writer (Editor), reader (Viewer), blocked (Denied).

How Permissions Work

  1. You invite a user to a Space and assign them a role (or access level).
  2. Permissions cascade through 4 levels: Space -> Project -> Table -> Column.
  3. The column is the atomic unit -- you can give one user "editor" access to one column and "viewer" access to another in the same table.
  4. Owner_Owner and Owner have full access unless explicitly denied at a lower level.
  5. Denied access always wins -- overrides all other permissions.
  6. A user cannot grant a level equal to or higher than their own.
  7. System Data projects auto-downgrade roles (admin->editor, editor->viewer, viewer->denied).

Example

Space: Acme Corp
  |
  +-- Owner_Owner: Alice (creator, permanent, full control)
  +-- Admin: Bob (manages Sales and Support projects)
  +-- Editor: Carol (edits data in Marketing tables)
  +-- Viewer: Dave (views Marketing reports, read-only)
  +-- Carol has "denied" on the Salary column (cannot see it)

Alice is the Owner_Owner (creator) -- permanent full control, can never be removed. Bob can manage tables, invite members, and edit data across all projects. Carol can add and edit rows in Marketing tables, but she cannot see the Salary column because it is explicitly denied. Dave can open the Marketing dashboard and read the data, but he cannot change a single cell.

Why This Structure?

You might wonder why GOD CRM does not just give you one big list of tables. The Space-and-Project structure exists for three reasons:

1. Separation

Different businesses, clients, or teams should not see each other's data. Spaces provide hard boundaries. Data does not leak between Spaces.

2. Organization

Even within one business, you have different departments or areas of work. Projects keep things tidy. You do not have to scroll through a hundred tables to find the one you need.

3. Scalability

As your work grows, you add new Projects. Each Project is self-contained, so adding a new one does not make the existing ones harder to use.

ASCII Diagram: The Full Picture

+-------------------------------------------------------+
| GOD CRM Account                                       |
|                                                       |
|  +-------------------------+  +--------------------+  |
|  | Space: Acme Corp        |  | Space: Freelance   |  |
|  |                         |  |                    |  |
|  |  +------ Sales ------+  |  |  +-- Clients ---+  |  |
|  |  | Leads table       |  |  |  | Projects tbl |  |  |
|  |  | Deals table       |  |  |  | Invoices tbl |  |  |
|  |  | Pipeline dashboard|  |  |  | Dashboard    |  |  |
|  |  +-------------------+  |  |  +--------------+  |  |
|  |                         |  |                    |  |
|  |  +--- Marketing -----+  |  +--------------------+  |
|  |  | Campaigns table   |  |                          |
|  |  | Content table     |  |                          |
|  |  | Campaign dashboard|  |                          |
|  |  +-------------------+  |                          |
|  |                         |                          |
|  +-------------------------+                          |
+-------------------------------------------------------+

Quick Summary

Concept Analogy Purpose
Space School building Isolates data, users, and settings
Project Classroom Groups related tables, dashboards, modules

What's Next?

You now know how GOD CRM organizes work into Spaces and Projects. But what actually goes inside a Project? The answer is tables -- the core way GOD CRM stores every piece of data.

Next: Tables and Data -- learn how data is stored, what column types are available, and how views let you look at the same data in different ways.