Enterprise Feature — This functionality is only available in the
Enterprise version of Packmind.
What are Spaces?
Spaces let you organize your playbook into distinct areas that reflect how your team works. A Space can represent a topic, a team, a programming language, a functional scope, or a technical scope — for example, “Backend”, “React Frontend”, “Security”, or “Data Pipeline”. Instead of managing all artifacts in a single flat list, Spaces give structure to your standards, commands, and skills so each group sees what is relevant to them.The Global Space
Every organization comes with a built-in Global space. It has special rules:- It cannot be deleted
- Every members of the organization belong to this space
Space Types
Spaces have two visibility levels:| Type | Visibility | Joining |
|---|---|---|
| Open | Visible to everyone in the organization | Anyone can browse and join via the sidebar |
| Private | Hidden from non-members | Must be added by a space administrator |
Space names must be unique within an organization.
Creating a Space
Any organization member — whether admin or regular member — can create a space. Click Browse in the sidebar to see all available spaces, then click New to create one. Provide a name and choose a visibility level (open or private).Roles Within a Space
Each space has its own set of roles, separate from organization roles:| Action | Space Admin | Space Member | Organization Admin |
|---|---|---|---|
| Add/remove members | Yes | No | No |
| Change member roles | Yes | No | No |
| Delete the space | Yes | No | Yes |
Space roles are independent from organization roles. A user can be an
administrator in one space and a regular member in another.
Leaving a Space
Any member can leave a space on their own at any time — except the Global space, which cannot be left.Deleting a Space
Only space administrators and organization administrators can delete a space.Spaces and the CLI
Package slug prefixing
When your organization uses multiple spaces, package slugs are prefixed with the space slug using@space/package notation:
Access warnings during install
If yourpackmind.json references packages from spaces you do not currently have access to, the install command displays a warning. However, this does not affect your existing configuration — files from those packages are not removed, they simply will not be updated.
To resolve access issues:
- Open spaces — join the space via the sidebar in the Packmind app
- Private spaces — ask a space administrator or a colleague to add you
Related Documentation
- Packages Management — group artifacts into packages within a space
- Distribute Artifacts — distribute packages from spaces to your repositories
- Manage Users — organization-level roles and permissions
- CLI Documentation — CLI commands including install with space-prefixed packages