Guides
Spaces & Projects
Organize teams, domains, and initiatives so HiveBase mirrors how your company actually works.
Spaces and Projects give your workspace structure — so context, tasks, and agents line up with how your company is actually organized. Both are lenses over the same Company Brain: Spaces scope it by team, Projects focus it on a goal. The work stays connected; the structure just makes it legible.
- 01Company workspaceOne shared org
- 02SpacesTeams + domains
- 03ProjectsGoal + timeline
- 04TasksThe actual work
- 01
Company workspace
One shared org
- 02
Spaces
Teams + domains
- 03
Projects
Goal + timeline
- 04
Tasks
The actual work
Spaces
A Space represents a team or a domain — Sales, Engineering, a key account, a region. Spaces shape what context is relevant and who sees what, so each team works from the slice of the Brain that matters to them without losing the shared whole. They're the durable structure of your company: they outlast any single initiative.
Scoped relevance
Each Space surfaces the part of the Brain its team cares about — sharper answers, less noise.
Clear ownership
Work, agents, and context have an obvious home, so nothing lives in limbo.
Projects
A Project is an initiative with a goal and a timeline — a launch, a migration, a quarter's objective. Projects group the tasks, decisions, and context behind a body of work so progress is visible and nothing falls through. Unlike a Space, a Project is meant to finish: it spins up around an outcome and winds down when that outcome lands.
One goal in view
The tasks, decisions, and context behind an initiative sit together — progress is legible.
A clear arc
Projects start, ship, and close. The decisions made along the way stay in the Brain.
Spaces vs Projects
Both organize the workspace, but they answer different questions. Spaces are who and where; Projects are what and by when.
| Spaces | Projects | |
|---|---|---|
| What it is | A team or domain | An initiative with a goal and timeline |
| When to use | Standing structure that outlasts any one effort | A bounded push toward a specific outcome |
| What it groups | The people, context, and work for a domain | The tasks, decisions, and context behind one body of work |
| Lifecycle | Durable — it persists | Finite — it ships and closes |
| Example | "Sales", "Engineering", "Acme account" | "Q3 launch", "Postgres migration", "SOC 2" |
A Project typically lives inside a Space — the Q3 launch belongs to Marketing, the Postgres migration to Engineering — but the same shared Brain backs both, so context written in one is available wherever it's relevant.
How they connect to the Brain
Structure doesn't fragment your context — it focuses it. Every Space and Project reads from the one Company Brain, so a decision recorded in a Project is instantly part of the company's memory, not trapped in a silo.
- Spaces scope the Brain by team — relevant context, less noise.
- Projects pull together the tasks, decisions, and context for one goal.
- Tasks roll up to Projects and Spaces, so progress is visible at every level.
- Everything still reads and writes the same shared Brain — no duplicated truth.
Structure is optional to start
You can get value from HiveBase before organizing anything. Add Spaces and Projects when you want sharper relevance and clearer ownership — not before you need them.
Related
Context & the Brain
The shared memory that every Space and Project reads from.
Tasks
The work that rolls up into Projects and Spaces.
Invite your team
Shared Brain first; structure when ownership needs walls.
Squads
Department loops that still share the same company memory.
Autonomous PM
Board hygiene that can sit above Projects when the board is the product.