GC pack · GC pack

Your company layer

Your company's own letterhead, brand, voice, lessons and BASE BID template, kept apart from the GC pack.

The GC pack names no company. Everything that makes it sound and look like your company lives in your company layer: a set of files and settings crux keeps for your company beside the pack, and that travels with your company profile.

What a company layer holds

PartWhat crux does with it
Estimate template (templates/estimate.xlsx)Your own BASE BID workbook. It wins over the pack's default. See Which template.
Knowledge (knowledge/*.md)Your company profile, voice notes, lessons from past bids, your markup build-up and your go/no-go fit. crux reads them before the pack's generic versions and cites them as company: <file> §<section>.
Brand (brand/) and fontsYour logo and wordmark for scope letters, bid bulletins and owner Q&A transmittals. With no logo, crux sets your company name as text.
Settings (settings.json)Plain values only: your company's names as they appear on bid tabs, the company database's server, port and name, your brand colours, your Bonfire portal address. Never a login or a password.

See and manage it

Open Settings > Company > Pack company files. Every file and setting is listed, with where it came from. Remove takes one away (crux asks first). See Company settings.

Share it with your team

The layer travels inside your company profile file. Whoever set crux up shares it from Settings > Backup > Company profile > Share company profile…; each estimator opens it in the setup wizard or with Update from company profile…. See Your company profile.

When the layer carries the company database's server details, each estimator's Company database page already shows them filled in: they add only their own login and password. See Company database.

What stays out

  • Passwords and sign-ins. Each person's database login, BuildingConnected sign-in and Bonfire sign-in stay on their own computer.
  • The pack itself. Playbooks, knowledge and tools come with the GC pack and update with it. Your layer is never overwritten by a pack update.