Best Practices
Recommendations on what to configure at company level (standard data) vs. project level (project-specific data).
What is it?
Practical recommendations on where to place each configuration so you scale efficiently across many projects.
Configure at company level
Keep at the company level everything that should stay consistent and be reused across projects. The directory of companies, vendors, and contacts belongs here because it is shared by every project and avoids duplicate data. Roles and permission groups keep access consistent organization-wide, and fieldsets ensure custom data is captured the same way everywhere. Workflow templates standardize review and approval processes, and shared data standards like disciplines, packages, and areas keep everyone working from the same vocabulary.
Configure at project level
Configure at the project level whatever is specific to a single job. The project settings and team are unique to each job. Locations differ from project to project, since each one has its own buildings, floors, and zones. Permission overrides let you tailor access to a particular project, and workflow adjustments adapt a company template to the contract or type of that project.
General rule: configure at the company level everything reused across multiple projects; configure at the project level everything specific to that job.
Inheritance Rules
Rules that determine which data is inherited automatically, which is optional, and which is never inherited.
Project Hub
Operational project modules. This is where all the technical documentation lives: drawings, BIM models, submittals, RFIs, correspondence, and punch list. It is the core of the project team's daily work.