CupixWorks 5.0 — this article is still being finished. Screenshots marked to be replaced show the right screens and will be retaken before launch. Taken in a support session, so the top of the screen shows a bar you will not see. Taken on an internal test system, so the address and team name are not the ones you will see.
Four catalogues, defined once
Team Settings › Standards holds four lists that the rest of the product draws on: Project Types and their subtypes, BIM templates and categories with work phases, Work Area Types, and Note Tags.
Each is defined here and consumed elsewhere. IA5-SET-AC-26 puts it plainly for project types: this page is the single authority. Everywhere a project type is chosen — the New Project dialog, a project's properties — reads this list.
Why you cannot pick the thing you need
This is the question the cascade answers, and it is the reason this article exists rather than a note in each of four other articles. If a type, a category or a work area type is not offered where you expect it, it was never defined a level up.
The order is always the same: defined at team level → chosen per project → used in the work.
A default is a starting point. A constraint is not.
The distinction matters more than it sounds. IA5-SET-AC-12 draws it explicitly.
Defaults seed. Units and language give a new member a starting point, and that member can choose otherwise on their own Preferences page. Changing a team default does not reach back and change anyone.
Constraints enforce. Project Types is the worked example, because it produces a refusal rather than a suggestion: a project cannot be given a type nobody defined here, and the Standards row for each type shows how many projects already hold it, so the reach of the list is on the page.
Length, Area and Volume are set independently, and an unset one reads (Not set) rather than silently taking a value.
Adding a type, a subtype, a BIM category
Add Type, top right of Project Types, opens a one-field dialog — the type's name — and Add puts it at the foot of the list with 0 subtypes and 0 Projects. Expand a type and the last row is an inline field: type a subtype name and press Enter. Each type row also shows how many projects hold it, which is the reach of the list on the page.
BIM Categories works the same way one level down: Add Template creates a template, and a template expanded ends in an Add item… field for a category. Templates are listed with their category and subcategory counts and the number of projects using each.
Renaming, and deleting
Renaming a type does not disturb the projects using it — they follow the record, not the string.
Deleting is where the caution belongs. Deleting a work area type tells you how many work areas use it inside the confirmation, because a count after the fact is not a decision anyone got to make.
Deleting a project type that is in use is allowed, and the projects survive it. Their Project Type becomes Not set. The confirmation dialog tells you how many projects that will happen to before you agree to it.
Editing this page is Team Admin, Super Admin included — and the same is true of Templates and Asset Categories. A Project Admin cannot edit team standards.