Can we invite our manager or a contractor into a Hub thread?

One of the more useful things about a thread-based discussion tool is that access can be scoped to exactly the conversation someone needs to be part of, rather than all-or-nothing.

Why scoped invites matter

Under a lot of informal systems, involving a contractor in a discussion means either forwarding emails piecemeal (and losing context) or adding them to a group chat where they can see everything the committee discusses, including unrelated and sometimes sensitive matters. Neither is ideal.

How it works

A committee member can invite a specific person — a strata manager, building manager, or contractor being consulted on a job — into a single Hub thread. That person sees only that thread, not the rest of Committee Hub or the portal generally, unless they're separately given a broader seat with wider access.

Typical situations to use this for

• Getting a contractor's input on scope before finalising a quote request
• Looping a building manager into a specific maintenance decision without giving them standing access to every committee conversation
• Consulting the strata manager on a legal or procedural question relevant to one matter

What this doesn't replace

This is different from giving someone a full seat in the portal — managers and building managers who need ongoing access get their own seat type with page-level permissions set by the committee. Thread invites are for one-off or matter-specific involvement, while seats are for standing roles.

Keeping control

Because each invite is scoped to a single thread, removing someone's access when the matter is resolved is straightforward, and it doesn't affect anything else they might separately have access to in the portal.