Unit hubs
Every business unit gets a hub: a page named after the unit itself - "Water Hub" - holding the material that unit has adopted.
If units are the scope things get shared with, the hub is the place they end up.
A unit hub with its five sections
Getting there
From your account menu. If you belong to more than one unit, the menu shows your first alphabetically; the others are a click away from there. If you belong to no units, there's no hub entry - there'd be nothing on it.
What's on it
Five sections:
| Section | What's in it |
|---|---|
| Checklists | The unit's shared checklists |
| Revit Workflows | Saved routines for the Revit add-in |
| Workflows | Workflows the unit has adopted |
| Resources | A general file store for the unit |
| Codes | The unit's code books, as a plain list |
Everything here is on the hub because someone tagged it to the unit and a lead approved it. That's the point: a hub is a curated shelf, not a dump of everything anyone in the unit has ever made. See How access works.
Resources
Resources is the section with no equivalent anywhere else: a place for the unit's own files - the CAD standard, the client's title-block template, the reference document everyone on that market needs at hand.
Anyone in the unit can upload. What happens next depends on who you are:
- A lead's upload goes straight onto the hub, approved.
- A member's upload lands as a pending request and shows an Awaiting review chip until a lead accepts it. It doesn't quietly join the shelf, and it doesn't vanish either.
The reviewer is the unit's lead, or an org owner where the unit has no lead yet - so the confirmation never names an approver who doesn't exist.
For unit leads
The hub is also your workbench. Three things live in the manage view:
Your unit's queue. Pending requests to share something with this unit, each opening an evidence panel with the item, the same accept / decline controls whatever kind it is, and the conversation thread underneath. A decline needs a note; see How access works.
Organization requests. A separate, org-wide queue. Because the org-door review pool is org owners plus any unit lead, leading one unit puts these in front of you too. The same queue appears on the Dashboard.
Members. Add any active person in your organization to the unit, and remove plain members. You can't remove another lead - granting and revoking the lead role stays with the org owner, on the Dashboard.
Two limits worth knowing: your own shares into your unit still go through the queue (that's deliberate - it's what teaches leads the queue exists), and you can't browse members' private drafts, only what has actually been offered to you.
Asking to join a unit
If your work has moved and you should be in a unit you're not in, you can request to join it. It goes to the same reviewers as a share request.
An org owner adding you to the unit directly settles any pending request you had - you won't end up with a stale request hanging around after you've already been added.
Where else units show up
The hub isn't the only place units matter. Once your organization uses them, they narrow things across the platform:
- The code library - a published book can be tagged to specific units, so the Texas amendments file under the Texas team's shelf instead of cluttering the Ontario library. Tags on a published book organize; they don't restrict who can read it.
- Workflows - shared workflows group by unit.
- The Dashboard - stats break down by unit, so an owner can compare offices or disciplines. A project belonging to two units is counted in both.
- Projects - a project carries its units, which is what makes that breakdown work.
Units gate, disciplines label
Two things on the platform look like filters, and only one of them is.
Units are an access boundary. Something shared with a unit is visible to that unit's members and to org owners - nobody else. Other people don't see a locked version of it; it simply doesn't appear in their lists, and a hub you're not a member of won't open at all.
Disciplines are a label. Your discipline is self-selected, it preselects a chip here and there, and you can always clear it to see every discipline's material. A discipline chip narrows what you're looking at; it never hides anything from you.
Either way, what you see is trustworthy: anything a hub or list shows you, you're allowed to see. Confidential material is kept out of your lists by the platform itself, never by a filter you could clear.
A retired unit
If a unit is removed from your organization's list, its hub still opens and says so. You can't share anything new into it, but what's already there stays visible and its grants stay revocable. See How access works.
Business units are switched on per organization. With no units configured, the hub entry and the unit controls simply don't appear. If you want them, talk to us.