Projects and the Commun space
How projects, visibility levels, and the shared Commun space organize team knowledge.
Mios structures organizational memory into workspaces. There are two primary types of workspaces: dedicated projects and the shared Commun space.
Projects
A project is a focused workspace for an engineering squad, a product repository, or a client initiative. It holds all resources associated with that scope:
- Connected code repositories and issue trackers.
- Dedicated chat channels and document folders.
- Extracted architectural and product decisions.
- A project-specific review queue ("Needs you").
Each project maintains an independent knowledge graph. Decisions made in one project do not pollute or alter the rules of unrelated projects.
Open vs private projects
When creating or configuring a project, managers choose its visibility level:
Open projects
Any member of your organization can view and join an open project. When new teammates sign up using the organization invitation code, they are automatically placed into the default open project. Open projects are ideal for core products, shared libraries, and internal tooling.
Private projects
Private projects are restricted to explicit members. They do not appear in the open project browser. To access a private project, a teammate must either receive an invitation from a project admin or enter the private project's specific join code. Private projects are typically used for client contracts, sensitive infrastructure, or security reviews.
The Commun shared space
Every organization includes a special workspace named Commun.
The Commun space acts as a cross-project view for teammates. Here are its core characteristics:
- Stores no sources directly: You cannot connect a repository or upload documents directly into the Commun. All sources belong to projects.
- Cross-project search and chat: When asking questions in the Commun, Mios searches across all projects you have permission to view. This makes it easy to find decisions across multiple squads.
- Restricted from coding agents: Coding agents are strictly prohibited from connecting to the Commun space. The backend blocks agent requests to the Commun with an error. Coding agents must always be scoped to a specific project to avoid cross-project confusion.
You can switch between your projects and the Commun space at any time using the workspace selector in https://app.mios-ai.com.