Multi-Tenancy Overview
Menatic AI supports multi-tenancy through a three-level hierarchy: Organizations → Departments → Projects.
Hierarchy
Section titled “Hierarchy”Organization (e.g. "Acme Corp")└── Department (e.g. "Engineering") └── Project (e.g. "data-pipelines") ├── Kubernetes Namespace: apps-data-pipelines ├── ResourceQuota ├── Project API Token └── Allowed MCP ServersOrganization
Section titled “Organization”The top-level container. An organization groups all departments and projects belonging to a company or a large team.
Department
Section titled “Department”A subdivision of an organization. Departments map to business units, teams, or cost centers.
Project
Section titled “Project”The operational unit. Each project gets:
- A dedicated Kubernetes namespace (
apps-<project-slug>) with aResourceQuota - A project API token for programmatic access from notebooks and external services
- A list of allowed MCP servers that project members can call
- Shared usage tracking for billing and chargeback
Resource Quotas
Section titled “Resource Quotas”Each project has configurable resource quotas enforced by Kubernetes:
| Resource | Default |
|---|---|
| CPU | 4 cores |
| Memory | 8Gi |
| Storage | 50Gi |
| GPU | 0 |
Quotas prevent a single project from consuming all cluster resources.
Memberships
Section titled “Memberships”Users are assigned roles at each level of the hierarchy:
| Level | Role | Effect |
|---|---|---|
| Organization | admin | Manage all departments and projects in the org |
| Organization | member | Read access to org resources |
| Department | admin | Manage all projects in the department |
| Department | member | Read access to department resources |
| Project | admin | Full access to project resources |
| Project | member | Access to project notebooks, jobs, and MCP servers |
Managing Tenancy
Section titled “Managing Tenancy”Navigate to Settings → Tenancy to manage organizations, departments, and projects.