ParaHub

ParaHub is a single workspace for every parameter job in a Revit project. Revit ships the primitives — shared parameters, project parameters, family parameters — but very little tooling to govern, audit or propagate them at the scale a real design firm works at. Instead of moving between the Project Parameters dialog, the Shared Parameters editor, and each family one at a time, ParaHub puts five tabs — Parameters, Categories, Transfer, Families, and Shared Editor — behind one modeless window that stays open while you keep working in the model. Nothing reaches your model until you say so. The Parameters tab lists every parameter in the document, including the built-ins Revit's binding map never reports, and stages your creates, edits, duplicates and deletes as pending rows. Apply commits the whole batch as one Revit undo step, with each row in its own transaction so one failure never takes the others down. Excel and shared parameter file imports run through a review dialog first, where every incoming row is classified as new, identical, conflicting or ambiguous before anything is staged. Category assignment works the same way, with a per-row picker, presets that persist across projects, and drag-and-drop to copy a category set from one parameter to another. The Transfer and Families tabs extend that batch-apply engine to family documents: copy an existing family's parameters into any number of loaded families, or compose a new set and write it into all of them at once. Parameters are written into each family's own definition and the family is reloaded into the project, so they never land in the project's parameter list, and a shared parameter is matched by GUID rather than by name so it stays one definition everywhere it lands. The Shared Editor tab manages the shared parameter file itself — rename, delete, move between groups, regenerate GUIDs, and merge several files into one — operations Revit's own API cannot perform, handled by editing the shared parameter file directly, one line at a time. Throughout, ParaHub never resolves an ambiguity silently. Parameters are identified by built-in id, shared GUID or definition id rather than by display name; GUIDs are never fabricated; and where a conflict could redefine an identity used elsewhere, it is reported for a decision rather than settled for you. Full installation and per-tab instructions are in the Documentation tab.