Configure shared catalogs

Builddar keeps a set of shared lists at the organization level. They're the defaults every new project starts from, so curating them once saves setup work on every project after.

Required role: Organization Admin.

The catalogs

Catalog	What it's for	Scope
Trades	Work packages (lots) — Plumbing, Electrical, Earthworks. Used on issues and companies.	Organization template, copied into each project
Zone types	Building, Floor, Room, Area… the levels your zone tree is built from.	Organization template, copied into each project
Issue title suggestions	Ready-made issue titles per trade, to speed up logging on site.	Organization template, copied with the trades
Disciplines	Architecture, Structure, MEP… used to classify drawings.	Organization-wide, shared live
Company types	General Contractor, Subcontractor, Client, Architect…	Organization-wide
Typology and orientation	T1/T2/T3 and North/South/East/West, for unit attributes.	Organization-wide

note

Template versus shared. Trades, zone types, and title suggestions are templates: each project gets its own copy, so a project can rename a trade or renumber its lots without affecting anyone else. Disciplines, company types, and the categorization lists are shared live — editing one changes it everywhere.

Your organization is seeded with sensible defaults when it's created, so you can start working immediately and refine these later.

Edit trades

1. Open your organization's settings and go to Trades.
2. Add a trade, rename one, or set its code (the lot number) and display order.
3. Save.

Result: new projects start from this list. Existing projects keep the copies they already have.

caution

Changing an organization trade does not change projects that already exist — they own their own copies. Edit the trade inside the project when you need to fix it there.

Edit zone types

1. Go to Zone types in organization settings.
2. Add or rename a type, and set its hierarchy level so the tree validates correctly (Building 0, Floor 1, Unit 2).
3. Mark the type that represents what you deliver as a unit to enable lifecycle tracking on new projects.
4. Save.

See Build the zone hierarchy for how types shape the tree.

Edit issue title suggestions

Suggestions are attached to a trade and offered when someone types an issue title.

1. Go to Issue title suggestions.
2. Add a title and pick the trade it belongs to.
3. Save.

Result: on site, choosing a trade offers your standard wording instead of everyone typing their own. Builddar tracks which suggestions get used most and surfaces those first.

Edit disciplines

Disciplines classify drawings.

1. Go to Disciplines.
2. Add, rename, reorder, or remove one.
3. Save.

Result: the change applies to every project immediately — disciplines are shared, not copied.

Edit company types

Company types classify the companies on a project.

1. Go to Company types.
2. Add or rename a type.
3. Mark a type as a stakeholder when it represents a client, project manager, architect, or inspector rather than a contractor holding a work package.
4. Save.

note

The stakeholder flag is what separates the two rosters printed on a meeting report — the contractors on one side, the project stakeholders on the other.

Edit typology and orientation lists

These feed the unit attributes on a zone:

• Typology — T1, T2, T3, and any values you add.
• Orientation — North, South, East, West, and so on.

Add your own values and set their display order so the pickers read the way your team expects.

Choose what a new project copies

When you create a project, Builddar shows which of these settings can be copied from the organization, filtered to what your plan enables. Copying gives the new project a working configuration on day one.

Next steps

• Create a project
• Set up a project