Zones overview
A zone is a place on your project — a building, a floor, an apartment, a room. Zones form a tree: a building contains floors, a floor contains apartments, an apartment contains rooms. Everything else in Builddar hangs off this tree.
Why zones matter
- Every issue is located in a zone. It's how you answer "where is this defect?".
- Drawings are attached to zones, so a floor plan belongs to the floor it shows.
- Reports can be filtered and grouped by zone.
- Zone access controls what a guest can see — a subcontractor can be limited to the building they work on.
Zone types
Every zone has a zone type — Building, Floor, Room, Area, and so on. Your organization ships with a default set of types, and each project gets its own copy that a manager can rename, add to, or remove.
A zone type carries two settings that shape the tree:
- Hierarchy level — the depth this type normally sits at (Building 0, Floor 1, Unit 2). It orders the type picker, defaults the child type when you add a zone, and blocks impossible structures: a Floor can't contain a Building. A type with no level set is unclassified and is never blocked.
- Unit — marks a type as the thing you actually deliver or sell (an apartment, a shop, a parking space). Zones of a unit type carry a lifecycle state; zones above them report a rollup.
Zone types are project-scoped. Editing a type inside a project changes it for that project only — your organization's defaults stay untouched, and new projects keep getting a clean copy. See Configure shared catalogs.
Zone identifiers
Beyond its name, a zone can carry two references:
- Reference — generated by Builddar from the zone's path when it's created (for example
Bâtiment A > Étage 1 > A-101becomesBATA-E1-A101). It's unique in the project, read-only, and never regenerated — not on rename, not on move. This is what a units import matches on so a re-upload updates instead of duplicating. - External code — your own identifier, the lot reference your spreadsheet or CRM already uses. Free text, editable, unique within the project when set.
Who can do what
| Action | Manager | Collaborator | Guest |
|---|---|---|---|
| View zones | ✅ | ✅ | ✅ (only zones they have access to) |
| Create a zone | ✅ | ✅ | — |
| Rename / move a zone | ✅ | ✅ | — |
| Delete a zone | ✅ | — | — |
| Share a zone / manage access | ✅ | — | — |
| Record a unit lifecycle state | ✅ | ✅ | — |