Concepts
Organization
Learn how organizations, projects, and resources are structured in Monospace
Overview
An Organization is the top-level tenant in Monospace. Everything lives within a project, which belongs to an organization.
Organization
└── Projects
├── Access Control
│ ├── Members (Users with assigned Roles)
│ ├── Service Accounts (Non-human authentication with Roles)
│ └── Roles & Policies (Permission definitions)
├── Data Sources (Databases)
│ └── Collections (Tables, models, data structures)
│ ├── Fields (Columns, attributes)
│ └── Relations (Foreign keys, relationships)
└── Spaces
└── Pages (Custom data views and forms)
Glossary
| Term | Description |
|---|---|
| Organization | The top-level container representing your company or team. Provides centralized control over security policies and member management across projects. |
| Project | A workspace within an organization that contains data from one or many data sources. Each project has its own members, permissions, data sources, and spaces. |
| Data Source | An external database connected to a project. Data sources are federated at the query level — no replication or data movement is required. |
| Space | A space within a project that groups related pages together. For example, a "Products" space for the catalog team or an "Orders" space for fulfillment. Spaces help keep content organized and findable. |
| Page | An interface within a space where users view and interact with data. Pages can display collection data as tables, forms, or custom layouts. |
| Member | A user granted access to an organization or project. Members are assigned roles that control data access and entitlements. |
| Service Account | Non-human credentials for API access and integrations. Service Accounts are assigned roles and project scope just like members. |